Registered 24 years ago, on no blocklists we checked, valid HTTPS, the site answered 200 in 1399 ms.
Rule-based: domain age, blocklists, TLS. A heuristic, not a guarantee.

| A | 206.17.31.208 |
|---|---|
| MX | 0 kansas-gov.mail.protection.outlook.com |
| NS | ks11.state.ks.us ks01.state.ks.us |
| TXT | _2oow7rme8cvrfell2g53r9npfcpdfhe 7o427ne1ns90sqvj4uimr37i9o MS=ms95468730 v=spf1 include:spf.protection.outlook.com -all |
| registrar | get.gov |
|---|---|
| registered | 2002-09-11 |
| expires | 2027-08-06 |
| last changed | 2026-08-14 |
| owner | State of Kansas, DISC |
| country | United States |
| nameservers | ks01.state.ks.us ks11.state.ks.us |
| status | server transfer prohibited |
| valid | yes |
|---|---|
| issuer | DigiCert Inc |
| covers | www.kansas.gov, kansas.gov |
| protocol | TLSv1.2 |
Domain is not signed with DNSSEC
| SPF | pass v=spf1 include:spf.protection.outlook.com -all |
|---|---|
| DMARC | none |
| DKIM | none of 1 common selectors |
Whether mail claiming to be from this domain can be checked as genuine.
Green: clean. Red: listed. Grey: the list did not answer.
Agents get this as data. Bought through the API, the checks behind this page cost $0.070: profile $0.025 + trust $0.020 + screenshot $0.020 + site status $0.005.
MCP: add https://how.is/mcp to Claude, Codex or Cursor
(one-line install) and ask for domain_trust on kansas.gov.
Reference: /llms.txt.
IPv6. Does kansas.gov work over IPv6? See the live check on aaaa.bot — website, mail and nameservers, graded A–F.
Watch kansas.gov. DNS read at the source every 5 minutes; certificate, blocklists and expiry every 6 hours. You get an email only when something changes.
Watch — $1 / 30 days