HOW.IS
?

How is house.gov?

Looks fine risk 0/100

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

Why

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

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

How house.gov looks right now
The home page, rendered by how.is in a sandboxed browser. Nothing on it is clickable here.
Site
200
93 ms · ends at www.house.gov
HTTPS
69 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 records3 record types
A3.33.159.71
15.197.146.213
NSpdns109.ultradns.biz
pdns109.ultradns.net
oxygen.house.gov
oxygen2.house.gov
pdns109.ultradns.org
pdns109.ultradns.com
TXT29wmjnwx6vr4cjqdbpdbgf60w6yhq5qx
72dk1qrd40qj0p94d7wx21tpj0j9rqvl
05cdx4snf6v0gxb0gb2124yfrm7mtn8w
google-site-verification=mAav-03XKMcfymo5s4BIGk64cLuJiBzwpdlyTKVgyAY
webexdomainverification.3LT6D=cc5e7b80-cddb-4e1b-8aac-d234c0a57705
google-gws-recovery-domain-verification=43442272
v=spf1 -all
jh148yl90mjb447d3qtwltmkhq4rjfch
gs69p2t6tn69nrdpjx3j4p6znrv53sr1
jbyz8mxd14wlzr2vzrt23wlrqfh6ltmf
cisco-ci-domain-verification=7d4cfc14af7a55da81bc7f1eb7a8dc13109344083623b9c52a62a26cbab325cb
google-site-verification=U6531Rs-iaqgh32_VR_5l6QqA9xWV4ppAEQJki9YJkg
Registrationget.gov
registrarget.gov
registered1997-10-02
expires2027-08-01
last changed2026-08-14
ownerUnited States House of Representatives
countryUnited States
nameserversoxygen.house.gov
oxygen2.house.gov
pdns109.ultradns.biz
pdns109.ultradns.com
pdns109.ultradns.net
pdns109.ultradns.org
statusserver transfer prohibited
registered 1997-10-02expires 2027-08-01
HTTPS certificate69 days left
validyes
issuerDigiCert Inc
coverswww.house.gov, www.aocoig.gov, www.cecc.gov, www.coil.gov, www.csce.gov, www.democraticleader.gov, www.democraticwhip.gov, www.dems.gov, www.gop.gov, www.gopleader.gov, www.gopwhip.gov, www.housecommunications.gov
protocolTLSv1.3
issued 2026-06-25expires 2027-01-09
DNSSECsecure

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

. → gov → house.gov
Email authenticationfair
SPFpass v=spf1 -all
DMARCwarning policy none
DKIMfound: selector1

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

Security scoregrade B · 148/205
Basic Security
20/40missing: DNSSEC Enabled
Record Security
23/45missing: CAA Records, DMARC Record, DKIM Presence
Advanced Security
10/25missing: Mail Server Configuration, IPv6 Support
Domain Reputation
50/50
Threat Detection
45/45missing: Domain Age Check
Blocklists0 listings · 8 lookups
SURBL MultidomainURIBL MultidomainSpamCop3.33.159.71Barracuda3.33.159.71UCEPROTECT Level 13.33.159.71SpamCop15.197.146.213Barracuda15.197.146.213UCEPROTECT Level 115.197.146.213

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

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

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

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