How is whitehouse.gov?

Looks fine risk 0/100

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

Why

02050100

finecarefulhigh risk

·Nothing in the checks added risk.

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

The home page, rendered by how.is in a sandboxed browser. Nothing on it is clickable here.

Site

200

68 ms · ends at www.whitehouse.gov

HTTPS

67 d

left on a Let's Encrypt certificate

Age

29 years

registered 1997-10-02

Blocklists

listings across 5 lists

Everything we looked at

DNS records4 record types

A	192.0.66.51
AAAA	2a04:fa87:fffd::c000:4233
NS	wally.ns.cloudflare.com ernest.ns.cloudflare.com
TXT	v=spf1 include:spf.mail.dmz.pitc.gov include:spf.protection.outlook.com include:spf.mandrillapp.com ip4:214.3.115.10/32 ip4:214.3.115.12/32 ip4:214.3.115.14/32 ip4:214.3.115.225/32 ip4:214.3.140.16/32 ip4:214.3.140.22/32 ip4:214.3.140.255/32 ~all _ag15rep8dkdk6c65mcqgkcmtszqxbqt MS=ms61205702 _annzjem33a9incgz74j6bqwu65dmzac google-site-verification=TfE8QdIcAwpNcoG9l9AxMIzz69S5PPd8peS-Pj1qtXk

Registrationget.gov

registrar	get.gov
registered	1997-10-02
expires	2027-09-17
last changed	2026-08-14
owner	Executive Office of the President
country	United States
nameservers	ernest.ns.cloudflare.com wally.ns.cloudflare.com
status	server transfer prohibited

registered 1997-10-02expires 2027-09-17

HTTPS certificate67 days left

valid	yes
issuer	Let's Encrypt
covers	whitehouse.gov, www.whitehouse.gov
protocol	TLSv1.3

issued 2026-10-05expires 2027-01-03

DNSSECsecure

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

. → gov → whitehouse.gov

Email authenticationgood

SPF	pass `v=spf1 include:spf.mail.dmz.pitc.gov include:spf.protection.outlook.com include:spf.mandrillapp.com ip4:214.3.115.10/32 ip4:214.3.115.12/32 ip4:214.3.115.14/32 ip4:214.3.115.225/32 ip4:214.3.140.16/32 ip4:214.3.140.22/32 ip4:214.3.140.255/32 ~all`
DMARC	pass policy reject
DKIM	found: selector1

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

Security scoregrade B · 150/205

Basic Security

10/40missing: DNSSEC Enabled, Nameserver Diversity

Record Security

30/45missing: CAA Records, DKIM Presence

Advanced Security

15/25missing: Mail Server Configuration

Domain Reputation

50/50

Threat Detection

45/45missing: Domain Age Check

Blocklists0 listings · 5 lookups

SURBL MultidomainURIBL MultidomainSpamCop192.0.66.51Barracuda192.0.66.51UCEPROTECT Level 1192.0.66.51

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=whitehouse.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=whitehouse.gov"

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

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