How is huffingtonpost.com?
Looks fine
risk 0/100
Registered 22 years ago, on no blocklists we checked, valid HTTPS, the site answered 200 in 127 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
127 ms · ends at www.huffpost.com
HTTPS
162 d
left on a Amazon certificate
Age
22 years
registered 2005-03-10
Blocklists
0
listings across 5 lists
Everything we looked at
DNS records5 record types
| A | 3.167.88.21 3.167.88.30 3.167.88.92 3.167.88.85 |
|---|---|
| MX | 10 alt3.aspmx.l.google.com 5 alt2.aspmx.l.google.com 5 alt1.aspmx.l.google.com 1 aspmx.l.google.com 10 alt4.aspmx.l.google.com |
| NS | ns-559.awsdns-05.net ns-287.awsdns-35.com ns-1205.awsdns-22.org ns-2006.awsdns-58.co.uk |
| TXT | spf2.0/pra include:_spf.createsend.com include:aspmx.sailthru.com include:_spf.google.com include:amazonses.com ip4:74.205.21.242 ip4:149.174.0.0/16 ip4:64.236.0.0/16 ip4:204.29.186.0/23 ~all dropbox-domain-verification=uncn7ru3lk5v facebook-domain-verification=g0p5wv14z89jccwlf5dsz1kprzffff docusign=803bb1d1-ca00-4828-9d0d-958294911d50 sjvw8kcp29jmrzqy6w30vj9xxcw0l2lt v=spf1 mx include:_spf.createsend.com include:aspmx.sailthru.com include:_spf.google.com include:amazonses.com ip4:74.205.21.242 ip4:149.174.0.0/16 ip4:64.236.0.0/16 ip4:204.29.186.0/23 ip4:148.163.135.35/32 ip4:148.163.139.55/32 ~all google-site-verification=2gqirxtTfQnbuBxqItMEYhPDLHI3aETO2cuv4TZ5gI4 _amazonses.huffingtonpost.com:Ymj5A72/0+8fWyJoUb4+sbAmempNyKaefa5cPtM7+fo= |
| CAA | {'type': 'CAA', 'issue': 'letsencrypt.org', 'critical': 0} {'type': 'CAA', 'issue': 'digicert.com', 'critical': 0} {'type': 'CAA', 'iodef': 'mailto:security@verizonmedia.com', 'critical': 0} {'type': 'CAA', 'issue': 'amazon.com', 'critical': 0} {'type': 'CAA', 'issue': 'globalsign.com', 'critical': 0} |
RegistrationMarkMonitor Inc.
| registrar | MarkMonitor Inc. |
|---|---|
| registered | 2005-03-10 |
| expires | 2028-03-10 |
| last changed | 2026-02-06 |
| owner | REDACTED FOR PRIVACY |
| nameservers | ns-1205.awsdns-22.org ns-2006.awsdns-58.co.uk ns-287.awsdns-35.com ns-559.awsdns-05.net |
| status | active client update prohibited client transfer prohibited client delete prohibited |
registered 2005-03-10expires 2028-03-10
HTTPS certificate162 days left
| valid | yes |
|---|---|
| issuer | Amazon |
| covers | blogger.huffingtonpost.com, politics.huffingtonpost.com, interactives.huffingtonpost.com, editorial.huffingtonpost.com, accounts.huffingtonpost.com, secure.huffingtonpost.com, bestschoolday.huffingtonpost.com, tips.huffingtonpost.com, cgnk.huffingtonpost.com, finance.huffingtonpost.com, rise.huffingtonpost.com, status.huffingtonpost.com |
| protocol | TLSv1.3 |
issued 2026-09-24expires 2027-04-09
DNSSECinsecure
Domain is not signed with DNSSEC
. → com → huffingtonpost.com
Email authenticationexcellent
| SPF | pass v=spf1 mx include:_spf.createsend.com include:aspmx.sailthru.com include:_spf.google.com include:amazonses.com ip4:74.205.21.242 ip4:149.174.0.0/16 ip4:64.236.0.0/16 ip4:204.29.186.0/23 ip4:148.163.135.35/32 ip4:148.163.139.55/32 ~all |
|---|---|
| DMARC | pass policy quarantine |
| DKIM | found: google |
Whether mail claiming to be from this domain can be checked as genuine.
Security scoregrade A · 175/205
Basic Security20/40missing: DNSSEC Enabled
Record Security45/45missing: DKIM Presence
Advanced Security15/25missing: SOA Record Configuration, IPv6 Support
Domain Reputation50/50
Threat Detection45/45missing: Domain Age Check
Blocklists0 listings · 14 lookups
SURBL MultidomainURIBL MultidomainSpamCop3.167.88.92Barracuda3.167.88.92UCEPROTECT Level 13.167.88.92SpamCop3.167.88.30Barracuda3.167.88.30UCEPROTECT Level 13.167.88.30SpamCop3.167.88.21Barracuda3.167.88.21UCEPROTECT Level 13.167.88.21SpamCop3.167.88.85Barracuda3.167.88.85UCEPROTECT Level 13.167.88.85
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=huffingtonpost.com" \
-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=huffingtonpost.com"
MCP: add https://how.is/mcp to Claude, Codex or Cursor
(one-line install) and ask for domain_trust on huffingtonpost.com.
Reference: /llms.txt.
Watch huffingtonpost.com. 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