Check-Host.cc

Domain

www.example.com

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

Run a live full scan of www.example.com

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
4
A/AAAA targets
Subdomains
CT + scan + body
Record Types
2
seen in DNS
Observed Certs
6
in our scans

DNS Records

A
AAAA
MX
NS
TXT
CNAME
CAA

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

Subject: www.example.com
Issuer: www.example.com
SANs: www.example.com
Subject: www.example.com
Issuer: www.example.com
SANs: www.example.com
Subject: www.example.com
Issuer: www.example.com
SANs: www.example.com
Subject: www.example.com
Issuer: www.example.com
SANs: www.example.com
Subject: www.example.com
Issuer: www.example.com
SANs: www.example.com
Subject: www.example.com
Issuer: www.example.com
SANs: www.example.com
Subject: example.com
Issuer: example.com
SANs: example.com, www.example.com
Subject: www.example.com
Issuer: www.example.com
SANs: www.example.com
Subject: www.example.com
Issuer: www.example.com
SANs: www.example.com
Subject: www.example.com
Issuer: www.example.com
SANs: www.example.com
Subject: www.example.com
Issuer: www.example.com
SANs: www.example.com
Subject: example.com
Issuer: example.com
SANs: 127.0.0.1, example.com, www.example.com
Subject: www.example.com
Issuer: www.example.com
SANs: www.example.com
Subject: www.example.com
Issuer: www.example.com
SANs: www.example.com
Subject: www.example.com
Issuer: www.example.com
SANs: www.example.com
Subject: www.example.com
Issuer: www.example.com
SANs: www.example.com
Subject: www.example.com
Issuer: www.example.com
SANs: www.example.com
Subject: www.example.com
Issuer: www.example.com
SANs: www.example.com
Subject: example.com
Issuer: example.com
SANs: 127.0.0.1, example.com, www.example.com
Subject: www.example.com
Issuer: www.example.com
SANs: www.example.com
Subject: www.example.com
Issuer: www.example.com
SANs: www.example.com
Subject: www.example.com
Issuer: www.example.com
SANs: www.example.com
Subject: www.example.com
Issuer: VPN CA
SANs: www.example.com
Subject: www.example.com
Issuer: www.example.com
SANs: www.example.com
Subject: www.example.com
Issuer: www.example.com
SANs: www.example.com
Subject: www.example.com
Issuer: www.example.com
SANs: www.example.com
Subject: example.com
Issuer: example.com
SANs: 127.0.0.1, example.com, www.example.com
Subject: www.example.com
Issuer: www.example.com
SANs: www.example.com
Subject: www.example.com
Issuer: www.example.com
SANs: www.example.com
Subject: www.example.com
Issuer: www.example.com
SANs: www.example.com

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.

CT-Log Evidence

Certificates from public Certificate Transparency logs whose subject or SAN names this domain — including historic certs we never observed live.

8affadae5b2cc6e3… google · argon2026h2
Subject: example.com
Issuer: Sectigo Public Server Authentication CA OV R36
SANs: example.com, example.edu, example.net, example.org, www.example.com, www.example.edu, www.example.net, www.example.org
Valid: 2025-12-02 00:00:00 → 2026-12-02 23:59:59
a42a79d123e9de1d… cloudflare · nimbus2026
Subject: example.com
Issuer: Sectigo Public Server Authentication CA OV R36
SANs: example.com, example.edu, example.net, example.org, www.example.com, www.example.edu, www.example.net, www.example.org
Valid: 2025-12-02 00:00:00 → 2026-12-02 23:59:59
a42a79d123e9de1d… google · xenon2026h2
Subject: example.com
Issuer: Sectigo Public Server Authentication CA OV R36
SANs: example.com, example.edu, example.net, example.org, www.example.com, www.example.edu, www.example.net, www.example.org
Valid: 2025-12-02 00:00:00 → 2026-12-02 23:59:59
04d54ae0d1b89c04… google · argon2026h2
Subject: example.com
Issuer: Sectigo Public Server Authentication CA OV R36
SANs: example.com, example.edu, example.net, example.org, www.example.com, www.example.edu, www.example.net, www.example.org
Valid: 2025-11-21 00:00:00 → 2026-11-21 23:59:59
d909797016952e2e… google · argon2026h2
Subject: example.com
Issuer: Sectigo Public Server Authentication CA OV R36
SANs: example.com, example.edu, example.net, example.org, www.example.com, www.example.edu, www.example.net, www.example.org
Valid: 2025-11-21 00:00:00 → 2026-11-21 23:59:59

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 172.66.147.243 2026-05-25 21:30:03.372 2026-07-31 23:15:37.363
AAAA 2606:4700:10::6814:179a 2026-05-25 21:30:03.372 2026-07-31 23:15:37.363
A 104.20.23.154 2026-05-25 21:30:03.372 2026-07-31 23:15:37.363
AAAA 2606:4700:10::ac42:93f3 2026-05-25 21:30:03.372 2026-07-31 23:15:37.363