How is engadget.com?

Looks fine risk 0/100

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

88 ms · ends at www.engadget.com

HTTPS

163 d

left on a Amazon certificate

Age

23 years

registered 2004-01-23

Blocklists

listings across 5 lists

Everything we looked at

DNS records4 record types

A	13.226.209.41 13.226.209.76 13.226.209.123 13.226.209.71
MX	5 alt2.aspmx.l.google.com 5 alt1.aspmx.l.google.com 1 aspmx.l.google.com 10 aspmx3.googlemail.com 10 aspmx2.googlemail.com
NS	ns-1449.awsdns-53.org ns-598.awsdns-10.net ns-305.awsdns-38.com ns-1799.awsdns-32.co.uk
TXT	v=spf1 include:_spf.google.com ~all facebook-domain-verification=ji23xe0rk7xahs4smgxgv2b833jbr7 google-site-verification=z8P2Zv9ueAtK5r0B2VTHvQhS1bUWkyU0ppiD2av3pUU

RegistrationGoDaddy.com, LLC

registrar	GoDaddy.com, LLC
registered	2004-01-23
expires	2028-01-23
last changed	2026-05-06
nameservers	ns-1449.awsdns-53.org ns-1799.awsdns-32.co.uk ns-305.awsdns-38.com ns-598.awsdns-10.net
status	client delete prohibited client renew prohibited client transfer prohibited client update prohibited

registered 2004-01-23expires 2028-01-23

HTTPS certificate163 days left

valid	yes
issuer	Amazon
covers	engadget.com, *.engadget.com
protocol	TLSv1.3

issued 2026-09-28expires 2027-04-13

DNSSECinsecure

Domain is not signed with DNSSEC

. → com → engadget.com

Email authenticationexcellent

SPF	pass `v=spf1 include:_spf.google.com ~all`
DMARC	pass policy reject
DKIM	found: google

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: IPv6 Support

Domain Reputation

50/50

Threat Detection

45/45missing: Domain Age Check

Blocklists0 listings · 14 lookups

SURBL MultidomainURIBL MultidomainSpamCop13.226.209.123Barracuda13.226.209.123UCEPROTECT Level 113.226.209.123SpamCop13.226.209.41Barracuda13.226.209.41UCEPROTECT Level 113.226.209.41SpamCop13.226.209.76Barracuda13.226.209.76UCEPROTECT Level 113.226.209.76SpamCop13.226.209.71Barracuda13.226.209.71UCEPROTECT Level 113.226.209.71

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

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

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

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