How is about.com?

Looks fine risk 0/100

Registered 28 years ago, on no blocklists we checked, valid HTTPS, the site answered 200 in 163 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

163 ms · ends at www.people.inc

HTTPS

70 d

left on a Let's Encrypt certificate

Age

28 years

registered 1999-03-12

Blocklists

listings across 5 lists

Everything we looked at

DNS records5 record types

A	172.66.1.220 162.159.141.224
AAAA	2a06:98c1:58::1d8 2606:4700:7::1d8
MX	50 aspmx3.googlemail.com 30 alt2.aspmx.l.google.com 20 alt1.aspmx.l.google.com 10 aspmx.l.google.com 40 aspmx2.googlemail.com
NS	blue.foundationdns.com blue.foundationdns.org blue.foundationdns.net
TXT	_globalsign-domain-verification=ojigih5w0ef57wjvnpzdo5a4culsziquhumcdqksj2 globalsign-domain-verification=w4_cm6jggwq8dxcwhkis6ltg0lzij1oizfjnoapv_d atlassian-domain-verification=uutqhyge655rxaicqp-iayc/q7ggtojzidouyp0rb7n8oudp4q8wfsgllr1iajvr facebook-domain-verification=rf8ocdhxrznl039sodxk5mul9of8l7 slack-domain-verification=op2dusosy3seuyxvj1tjafq1nwifizeevpkitpnr google-site-verification=nabvdaatpqecskkkchqujsdsjagdkyi4dg5-vj-bcrw v=spf1 ip4 64.125.213.247 ip4 216.223.13.247 ip4 34.194.76.185 ip4 35.164.185.216 ip4 34.194.69.219 include _spf.salesforce.com include _spf.google.com include spf.protection.outlook.com include amazonses.com ~all airtable-verification=7f23bd05102c5a2c073b0d0689ecaf71 adobe-idp-site-verification=4d443bb146b2a60fc0c0216c899a6ef9baa971cc3c36ac4b3020b4719b5c2e82 openai-domain-verification=dv-7ma37immfvwqj1fwgsn676a6

RegistrationMarkMonitor Inc.

registrar	MarkMonitor Inc.
registered	1999-03-12
expires	2027-03-12
last changed	2026-02-08
owner	REDACTED FOR PRIVACY
nameservers	blue.foundationdns.com blue.foundationdns.net blue.foundationdns.org
status	client delete prohibited client transfer prohibited client update prohibited

registered 1999-03-12expires 2027-03-12

HTTPS certificate70 days left

valid	yes
issuer	Let's Encrypt
covers	*.about.com, about.com
protocol	TLSv1.3

issued 2026-10-12expires 2027-01-10

DNSSECinsecure

Domain is not signed with DNSSEC

. → com → about.com

Email authenticationfair

SPF	pass `v=spf1 ip4 64.125.213.247 ip4 216.223.13.247 ip4 34.194.76.185 ip4 35.164.185.216 ip4 34.194.69.219 include _spf.salesforce.com include _spf.google.com include spf.protection.outlook.com include amazonses.com ~all`
DMARC	warning policy none
DKIM	none of 1 common selectors

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

Security scoregrade B · 163/205

Basic Security

20/40missing: DNSSEC Enabled

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 MultidomainSpamCop172.66.1.220Barracuda172.66.1.220UCEPROTECT Level 1172.66.1.220SpamCop162.159.141.224Barracuda162.159.141.224UCEPROTECT Level 1162.159.141.224

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=about.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=about.com"

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

IPv6. Does about.com work over IPv6? See the live check on aaaa.bot — website, mail and nameservers, graded A–F.

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