HOW.IS
?

How is gizmodo.com?

Looks fine risk 0/100

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

Why

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

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

How gizmodo.com looks right now
The home page, rendered by how.is in a sandboxed browser. Nothing on it is clickable here.
Site
200
55 ms
HTTPS
43 d
left on a Google Trust Services certificate
Age
24 years
registered 2002-07-01
Blocklists
0
listings across 5 lists

Everything we looked at

DNS records5 record types
A172.67.74.173
104.26.2.63
104.26.3.63
AAAA2606:4700:20::681a:23f
2606:4700:20::681a:33f
2606:4700:20::ac43:4aad
MX10 aspmx2.googlemail.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
1 aspmx.l.google.com
NSagustin.ns.cloudflare.com
monika.ns.cloudflare.com
TXTapple-domain-verification=qVsrwksLomfAp5ui
v=spf1 include:_spf.google.com include:_spf.scw-tem.cloud include:servers.mcsv.net -all
google-site-verification=ZHpYCDO8_L6gzqEMj34dxIVrm1qElsr_07cRdTMZ6vE
RegistrationOVH sas
registrarOVH sas
registered2002-07-01
expires2027-07-01
last changed2026-07-02
nameserversagustin.ns.cloudflare.com
monika.ns.cloudflare.com
statusclient delete prohibited
client transfer prohibited
registered 2002-07-01expires 2027-07-01
HTTPS certificate43 days left
validyes
issuerGoogle Trust Services
coversgizmodo.com, *.gizmodo.com, m.ca.gizmodo.com
protocolTLSv1.3
issued 2026-09-15expires 2026-12-14
DNSSECsecure

Domain is properly signed — chain validated by an independent validating resolver

. → com → gizmodo.com
Email authenticationexcellent
SPFpass v=spf1 include:_spf.google.com include:_spf.scw-tem.cloud include:servers.mcsv.net -all
DMARCpass policy quarantine
DKIMfound: google

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

Security scoregrade B · 160/205
Basic Security
10/40missing: DNSSEC Enabled, Nameserver Diversity
Record Security
30/45missing: CAA Records, DKIM Presence
Advanced Security
25/25
Domain Reputation
50/50
Threat Detection
45/45missing: Domain Age Check
Blocklists0 listings · 11 lookups
SURBL MultidomainURIBL MultidomainSpamCop172.67.74.173Barracuda172.67.74.173UCEPROTECT Level 1172.67.74.173SpamCop104.26.2.63Barracuda104.26.2.63UCEPROTECT Level 1104.26.2.63SpamCop104.26.3.63Barracuda104.26.3.63UCEPROTECT Level 1104.26.3.63

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

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

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

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