HOW.IS
?

How is loc.gov?

Looks fine risk 0/100

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

Why

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

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

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

Everything we looked at

DNS records5 record types
A104.18.64.82
104.17.6.58
AAAA2606:4700::6812:4052
2606:4700::6811:63a
MX10 mxa-00026101.gslb.gpphosted.com
10 mxb-00026101.gslb.gpphosted.com
NSalice.ns.cloudflare.com
kevin.ns.cloudflare.com
TXT62QSYa/kfNXdxXnLjT9/ZOyvqed/KSL3dFy+b7K7EFS08xeEY8vGX0IT9BCOCvkgLa16BcrmaQhTgKeOMK6njA==
ZA=NzrYbQCQ4geLYL//TYHmJA==
webexdomainverification.NQCL=b1bef083-e011-4dcf-b1f7-42204b82128e
atlassian-domain-verification=nWInaz9qwixZxg4Ef5K7jmsSKDAlta15azD9kOFROWwn8xjciPtK3MK4SUFB1R1/
538fe1481176c669d55eb1a37227bd0a3ccfb28d6a2838429e59f504dc3070d3
yTrNm8yrlLjz94UZ1A2UUPz7Gv5UfCIypoGH1HmXjNs=
google-site-verification=D5cqNFQ7z5rT2z4OXeYRmxrMc80omDUqEGtsNFY9N_g
google-site-verification=o0tsBc2NuJSImRS3MromAcC8lwoaWNp5LFZlmJXB0-0
e9af54f5-6e02-4c11-84a3-ab9d25e7b454
adobe-idp-site-verification=02f02861-90f5-4cf5-9922-c67c80a7bf26
google-site-verification=60lAEjrt1Mhjzxp92lROrlGsYFR9alVBZVncUMaus7Q
v=spf1 include:spf1.loc.gov include:spf2.loc.gov include:spf-00026101.gpphosted.com mx -all
MS=ms90737861
openai-domain-verification=dv-30BwSHGyfCP4Av8FZs9IAyOJ
Registrationget.gov
registrarget.gov
registered1997-10-02
expires2027-07-07
last changed2026-08-14
ownerLibrary of Congress
countryUnited States
nameserversalice.ns.cloudflare.com
kevin.ns.cloudflare.com
statusserver transfer prohibited
registered 1997-10-02expires 2027-07-07
HTTPS certificate85 days left
validyes
issuerGoogle Trust Services
coversloc.gov, *.loc.gov, *.le.loc.gov
protocolTLSv1.3
issued 2026-10-22expires 2027-01-20
DNSSECsecure

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

. → gov → loc.gov
Email authenticationfair
SPFpass v=spf1 include:spf1.loc.gov include:spf2.loc.gov include:spf-00026101.gpphosted.com mx -all
DMARCwarning policy none
DKIMnone of 1 common selectors

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

Security scoregrade B · 153/205
Basic Security
10/40missing: DNSSEC Enabled, Nameserver Diversity
Record Security
23/45missing: CAA Records, DMARC Record, DKIM Presence
Advanced Security
25/25
Domain Reputation
50/50
Threat Detection
45/45missing: Domain Age Check
Blocklists0 listings · 8 lookups
SURBL MultidomainURIBL MultidomainSpamCop104.18.64.82Barracuda104.18.64.82UCEPROTECT Level 1104.18.64.82SpamCop104.17.6.58Barracuda104.17.6.58UCEPROTECT Level 1104.17.6.58

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

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

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