Registered 26 years ago, on no blocklists we checked, no valid HTTPS certificate, the site did not answer (SSLCertVerificationError).
Rule-based: domain age, blocklists, TLS. A heuristic, not a guarantee.
| A | 166.117.127.137 166.117.221.242 |
|---|---|
| MX | 10 state-nm-us.mail.protection.outlook.com |
| NS | ns3-37.azure-dns.org ns2-37.azure-dns.net ns1-37.azure-dns.com ns4-37.azure-dns.info |
| TXT | jocol4b2dtpf6bq16edeq9s7t8 MS=ms50975780 |
| registrar | get.gov |
|---|---|
| registered | 2000-07-21 |
| expires | 2027-09-08 |
| last changed | 2026-08-14 |
| owner | Dept. of Information Technology |
| country | United States |
| nameservers | ns1-37.azure-dns.com ns2-37.azure-dns.net ns3-37.azure-dns.org ns4-37.azure-dns.info |
| status | server transfer prohibited |
| valid | no |
|---|---|
| issuer | Amazon |
| covers | www.nm.gov, nm.gov, nmgov.onconcourse.com |
| protocol | TLSv1.3 |
Domain is not signed with DNSSEC
| SPF | none |
|---|---|
| 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 newmexico.gov.
Reference: /llms.txt.
IPv6. Does newmexico.gov work over IPv6? See the live check on aaaa.bot — website, mail and nameservers, graded A–F.
Watch newmexico.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