HOW.IS
?

How is merriam-webster.com?

Looks fine risk 0/100

Registered 28 years ago, on no blocklists we checked, valid HTTPS, the site answered 403 in 64 ms.

Why

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

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

How merriam-webster.com looks right now
The home page, rendered by how.is in a sandboxed browser. Nothing on it is clickable here.
Site
403
64 ms
HTTPS
64 d
left on a Amazon certificate
Age
28 years
registered 1999-02-08
Blocklists
0
listings across 5 lists

Everything we looked at

DNS records5 record types
A3.162.112.97
3.162.112.64
3.162.112.58
3.162.112.129
AAAA2600:9000:244d:e800:c:3d32:e340:93a1
2600:9000:244d:f600:c:3d32:e340:93a1
2600:9000:244d:2e00:c:3d32:e340:93a1
2600:9000:244d:fc00:c:3d32:e340:93a1
2600:9000:244d:f200:c:3d32:e340:93a1
2600:9000:244d:c400:c:3d32:e340:93a1
2600:9000:244d:9200:c:3d32:e340:93a1
2600:9000:244d:d600:c:3d32:e340:93a1
MX1 smtp.google.com
NSns-323.awsdns-40.com
ns-1084.awsdns-07.org
ns-1998.awsdns-57.co.uk
ns-636.awsdns-15.net
TXTv=spf1 include:_spf.google.com include:sendgrid.net ~all
google-site-verification=yhZNYrftQlDsh_3oIQsAxUkrnWJCsa3pgxqnlBS3aIw
google-site-verification=S4yVMtexKSScdrR1yYa25BvuqJmWnB6MudoXTyEEFU0
google-site-verification=QFIo-DJEb2h-NnAkKfbngucTyIPtJLkdhiK9nI-icWo
google-site-verification=0P7lGsk2k9lYPZzfPtMQ65anErIqEaDKEB5s5SA-wjA
RegistrationCSC Corporate Domains, Inc.
registrarCSC Corporate Domains, Inc.
registered1999-02-08
expires2027-02-08
last changed2026-02-04
ownerEncyclopaedia Britannica, Inc.
nameserversns-1084.awsdns-07.org
ns-1998.awsdns-57.co.uk
ns-323.awsdns-40.com
ns-636.awsdns-15.net
statusclient transfer prohibited
registered 1999-02-08expires 2027-02-08
HTTPS certificate64 days left
validyes
issuerAmazon
covers*.merriam-webster.com, cdn-mw.com, *.m-w.com, *.theusage.com, theusage.com, *.word.com, *.cdn-mw.com, m-w.com, merriam-webster.com
protocolTLSv1.3
issued 2026-06-16expires 2026-12-30
DNSSECinsecure

Domain is not signed with DNSSEC

. → com → merriam-webster.com
Email authenticationexcellent
SPFpass v=spf1 include:_spf.google.com include:sendgrid.net ~all
DMARCpass policy reject
DKIMfound: google, s1, s2

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

Security scoregrade B · 165/205
Basic Security
20/40missing: DNSSEC Enabled
Record Security
30/45missing: CAA Records, DKIM Presence
Advanced Security
20/25missing: Mail Server Configuration
Domain Reputation
50/50
Threat Detection
45/45missing: Domain Age Check
Blocklists0 listings · 14 lookups
SURBL MultidomainURIBL MultidomainSpamCop3.162.112.129Barracuda3.162.112.129UCEPROTECT Level 13.162.112.129SpamCop3.162.112.58Barracuda3.162.112.58UCEPROTECT Level 13.162.112.58SpamCop3.162.112.97Barracuda3.162.112.97UCEPROTECT Level 13.162.112.97SpamCop3.162.112.64Barracuda3.162.112.64UCEPROTECT Level 13.162.112.64

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

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

Watch merriam-webster.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