HOW.IS
?

How is nps.gov?

Looks fine risk 0/100

Registered 29 years ago, on no blocklists we checked, valid HTTPS, the site answered 200 in 76 ms.

Why

02050100
finecarefulhigh risk
  • ·Nothing in the checks added risk.

Rule-based: domain age, blocklists, TLS. A heuristic, not a guarantee.

How nps.gov looks right now
The home page, rendered by how.is in a sandboxed browser. Nothing on it is clickable here.
Site
200
76 ms · ends at www.nps.gov
HTTPS
127 d
left on a DigiCert Inc certificate
Age
29 years
registered 1997-10-02
Blocklists
0
listings across 5 lists

Everything we looked at

DNS records5 record types
A35.169.243.105
AAAA2600:9000:20aa:0:1:983:9400:93a1
MX10 nps-gov.mail.protection.outlook.com
NSlucy.ns.cloudflare.com
ivan.ns.cloudflare.com
TXTk3x1fbzs2816tkxpg3c76qky6c7s2x4v
atlassian-domain-verification=BDNWwhbMkb/KgzHy3HEdJBunaWjCLLc1pTa1UNQLj/zH/f2zkBaWuLxSzT8UjnZV
f6500lq5a2750627udutbjg0b1
adobe-sign-verification=ccc5d4bbde3e1c62a31238fd7983103730f30c32145a4ae2fe71264bbd3874ef
_qbssbwgpkm46pn8gif4416ijhafqg85
openai-domain-verification=dv-ebpiMpJUr0MylOGbu0HSOvUN
amazonses:72aXC5OVEkJqI109ds3EEaNByQb/SclYLq+pIp+JWz0=
v=spf1 ip4:96.127.113.23 include:_spf.nps.gov include:servers.mcsv.net -all
MS=ms12791101
adobe-idp-site-verification=0c06fad3-cf1c-4e40-8ec6-2507879c946e
BEAA-1797-3015-58D3-FA87-9BD8-3ADE-179B
adobe-sign-verification=90b66ed10fef33178bc085fa5524b39d8bfcfbcb0da9aa7a440a60610f8513b1
perplexity-ai-domain-verification-z4mg7t=QEnaU1uq5f4xOyCwehY9Rduc8
domain-verification=Fk5XTTt657ZDHZU5Tw24OpZeUHYkCmh-HoGheazSguE
334fjub5l60gouiv36ot0f4fr8
Registrationget.gov
registrarget.gov
registered1997-10-02
expires2027-08-29
last changed2026-08-14
ownerDepartment of the Interior
countryUnited States
nameserversivan.ns.cloudflare.com
lucy.ns.cloudflare.com
statusserver transfer prohibited
registered 1997-10-02expires 2027-08-29
HTTPS certificate127 days left
validyes
issuerDigiCert Inc
covers*.nps.gov, nps.gov
protocolTLSv1.2
issued 2026-08-21expires 2027-03-07
DNSSECsecure

Domain is properly signed — chain validated by an independent validating resolver

. → gov → nps.gov
Email authenticationexcellent
SPFpass v=spf1 ip4:96.127.113.23 include:_spf.nps.gov include:servers.mcsv.net -all
DMARCpass policy reject
DKIMfound: k1, s1, s2, mail

Whether mail claiming to be from this domain can be checked as genuine.

Security scoregrade B · 155/205
Basic Security
10/40missing: DNSSEC Enabled, Nameserver Diversity
Record Security
30/45missing: CAA Records, DKIM Presence
Advanced Security
20/25missing: Mail Server Configuration
Domain Reputation
50/50
Threat Detection
45/45missing: Domain Age Check
Blocklists0 listings · 5 lookups
SURBL MultidomainURIBL MultidomainSpamCop35.169.243.105Barracuda35.169.243.105UCEPROTECT Level 135.169.243.105

Green: clean. Red: listed. Grey: the list did not answer.

Ask it yourself

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.

curl "https://how.is/v1/domain/trust?domain=nps.gov" \ -H "Authorization: Bearer $HOWIS_KEY" # or pay per call in USDC (x402), no key: the 402 tells your agent the price curl -i "https://how.is/v1/domain/profile?domain=nps.gov"

MCP: add https://how.is/mcp to Claude, Codex or Cursor (one-line install) and ask for domain_trust on nps.gov. Reference: /llms.txt.

IPv6. IPv6 readiness grade for nps.gov Does nps.gov work over IPv6? See the live check on aaaa.bot — website, mail and nameservers, graded A–F.

Watch nps.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