HOW.IS
?

How is wordpress.com?

Looks fine risk 0/100

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

Why

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

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

How wordpress.com looks right now
The home page, rendered by how.is in a sandboxed browser. Nothing on it is clickable here.
Site
200
32 ms
HTTPS
38 d
left on a Let's Encrypt certificate
Age
27 years
registered 2000-03-03
Blocklists
0
listings across 5 lists

Everything we looked at

DNS records5 record types
A192.0.78.17
192.0.78.9
MX10 mx-dfw.automattic.com
10 mx-ams.automattic.com
NSns2.wordpress.com
ns3.wordpress.com
ns1.wordpress.com
ns4.wordpress.com
TXTyahoo-verification-key=GqtxTvPQ+tFgwrCg9xNl6srlPSpDkTIj6q9YzADxxdE=
openai-domain-verification=dv-AKnzAsfVXHG2wucO1Bcx2JC7
v=spf1 include:_spf.automattic.com include:servers.mcsv.net include:_spf-wwd.automattic.com include:mail.zendesk.com include:sendgrid.net include:145630858.spf04.hubspotemail.net include:amazonses.com -all
google-site-verification=CW2JYOoHSXW8x6QyQO_a0edu0gNOKsLIHcO49QquLdU
CAA{'type': 'CAA', 'iodef': 'mailto:caa@automattic.com', 'critical': 0}
{'type': 'CAA', 'issue': 'letsencrypt.org;validationmethods=dns-01;accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/36334489', 'critical': 0}
{'type': 'CAA', 'critical': 0, 'issuewild': 'letsencrypt.org;validationmethods=dns-01;accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/36334489'}
RegistrationMarkMonitor Inc.
registrarMarkMonitor Inc.
registered2000-03-03
expires2033-03-03
last changed2023-08-28
ownerREDACTED FOR PRIVACY
nameserversns1.wordpress.com
ns2.wordpress.com
ns3.wordpress.com
ns4.wordpress.com
statusclient delete prohibited
client transfer prohibited
client update prohibited
server delete prohibited
server transfer prohibited
server update prohibited
registered 2000-03-03expires 2033-03-03
HTTPS certificate38 days left
validyes
issuerLet's Encrypt
covers*.wordpress.com, wordpress.com
protocolTLSv1.3
issued 2026-09-04expires 2026-12-03
DNSSECinsecure

Domain is not signed with DNSSEC

. → com → wordpress.com
Email authenticationexcellent
SPFpass v=spf1 include:_spf.automattic.com include:servers.mcsv.net include:_spf-wwd.automattic.com include:mail.zendesk.com include:sendgrid.net include:145630858.spf04.hubspotemail.net include:amazonses.com -all
DMARCpass policy reject
DKIMfound: k1

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

Security scoregrade B · 165/205
Basic Security
10/40missing: DNSSEC Enabled, Nameserver Diversity
Record Security
45/45missing: DKIM Presence
Advanced Security
15/25missing: SOA Record Configuration, IPv6 Support
Domain Reputation
50/50
Threat Detection
45/45missing: Domain Age Check
Blocklists0 listings · 8 lookups
SURBL MultidomainURIBL MultidomainSpamCop192.0.78.9Barracuda192.0.78.9UCEPROTECT Level 1192.0.78.9SpamCop192.0.78.17Barracuda192.0.78.17UCEPROTECT Level 1192.0.78.17

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

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

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