Check-Host.cc

Domain

blog.google

Aggregated from public BGP, CT logs, our scan layer, honeypots and global probes.

Run a live full scan of blog.google

On-demand: ports, banners, TLS, tech-stack, subdomains and origin/IP-leak detection. Results are shared publicly for everyone to link to.

Deep-scan now
Hosting IPs
A/AAAA targets
Subdomains
CT + scan + body
Record Types
seen in DNS
Observed Certs
in our scans

DNS Records

A
216.239.32.21, 216.239.34.21, 216.239.36.21, 216.239.38.21
AAAA
2001:4860:4802:32::15, 2001:4860:4802:34::15, 2001:4860:4802:36::15, 2001:4860:4802:38::15
MX
0 smtp.google.com
NS
ns1.zdns.google, ns2.zdns.google, ns3.zdns.google, ns4.zdns.google
TXT
facebook-domain-verification=1dpptdn7bpg26p5d1mkvttadjncmm8, v=spf1 include:_spf.google.com ?all
CNAME
CAA
0 issue "pki.goog"

WHOIS / Registration

Registration data planned

Registrar, creation/expiry dates and domain status via RDAP. Rolling out gradually — bulk WHOIS is rate-limited, so we resolve on a prioritized cadence.

Subdomains

Subdomain enumeration pending

Every subdomain ever issued a TLS cert under this apex — extracted from Certificate Transparency logs, our own scan observations and body references.

Tech Stack

Tech detection pending

Wappalyzer-rules detect CMS, frameworks, analytics, JS libs and server-side languages on this domain.

TLS Certificates

Certificate observations pending

TLS certs naming this domain in subject or SANs will appear here as our scan-layer catches them.

IPs Citing This Domain

No citing IPs found yet

As the world-sweep progresses, hosts referencing this domain in their HTML will surface here.

Origin / IP-Leak

USP

When a hostname is served behind a CDN (e.g. Cloudflare), the origin server can sometimes be identified by matching its TLS cert against the protected hostname. Findings shown here are heuristic candidates, not guarantees.

No origin-IP leaks detected (yet)

Either this domain doesn't sit behind a CDN, or we haven't seen a TLS cert from a non-CDN IP matching this hostname. Run a fullscan to refresh the cert→IP cross-reference.

Threat Intelligence

Domain threat-intel pending

Matches in URLhaus, OpenPhish, PhishTank, malware feeds, and Spamhaus DBL.

History

Passive DNS — every value this name ever resolved to and when we first / last observed it. Updates every cycle of our forward-DNS crawler.

Type Value First seen Last seen
A 216.239.32.21 2026-05-26 02:34:00.508 2026-07-26 13:46:30.523
TXT v=spf1 include:_spf.google.com ?all 2026-05-26 02:34:00.508 2026-07-26 13:46:30.523
AAAA 2001:4860:4802:38::15 2026-05-26 02:34:00.508 2026-07-26 13:46:30.523
NS ns4.zdns.google 2026-05-26 02:34:00.508 2026-07-26 13:46:30.523
AAAA 2001:4860:4802:32::15 2026-05-26 02:34:00.508 2026-07-26 13:46:30.523
TXT facebook-domain-verification=1dpptdn7bpg26p5d1mkvttadjncmm8 2026-05-26 02:34:00.508 2026-07-26 13:46:30.523
AAAA 2001:4860:4802:34::15 2026-05-26 02:34:00.508 2026-07-26 13:46:30.523
MX 0 smtp.google.com 2026-05-26 02:34:00.508 2026-07-26 13:46:30.523
NS ns2.zdns.google 2026-05-26 02:34:00.508 2026-07-26 13:46:30.523
NS ns3.zdns.google 2026-05-26 02:34:00.508 2026-07-26 13:46:30.523
A 216.239.36.21 2026-05-26 02:34:00.508 2026-07-26 13:46:30.523
NS ns1.zdns.google 2026-05-26 02:34:00.508 2026-07-26 13:46:30.523
CAA 0 issue "pki.goog" 2026-05-26 02:34:00.508 2026-07-26 13:46:30.523
A 216.239.38.21 2026-05-26 02:34:00.508 2026-07-26 13:46:30.523
AAAA 2001:4860:4802:36::15 2026-05-26 02:34:00.508 2026-07-26 13:46:30.523
A 216.239.34.21 2026-05-26 02:34:00.508 2026-07-26 13:46:30.523