Check-Host.cc

Domain

clustrmaps.com

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

Run a live full scan of clustrmaps.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
A/AAAA targets
Subdomains
CT + scan + body
Record Types
seen in DNS
Observed Certs
in our scans

DNS Records

A
104.20.22.84, 172.66.172.34, 5.39.10.93
AAAA
2001:41d0:203:dee4:5:39:10:93, 2606:4700:10::6814:1654, 2606:4700:10::ac42:ac22
MX
1 aspmx.l.google.com, 10 alt3.aspmx.l.google.com, 10 alt4.aspmx.l.google.com, 10 mail.imena.com.ua, 5 alt1.aspmx.l.google.com, 5 alt2.aspmx.l.google.com
NS
aurora.ns.cloudflare.com, decker.ns.cloudflare.com, nsa2.srv53.com, nsa2.srv53.org, nsa3.srv53.net, nsb2.srv53.net, nsb3.srv53.org, nsb4.srv53.com
TXT
google-site-verification=3ttraLldeCl1cCVw2m5yb85ALVFhQASqTyAQg1v7vkg, google-site-verification=F6bipmFPWalr9LrQdLadw4GqH9Sl8eLpykIlzl4NJM8, google-site-verification=Zh3WqHmQESOik0dQdChNsPEgSMf99535_58Po-6qEjw, v=spf1 include:_spf.google.com mx ip4:184.170.148.29/32 ip4:66.172.56.11/32 ip4:185.142.32.104/27 a:secure.serverhub.co ~all
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

Every subdomain we know about — harvested from CT-log SANs, scan-observed certs and HTML body references — paired with its current A/AAAA target.

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

Domain timeline pending

Passive-DNS history accumulates as our forward-DNS crawler observes A/AAAA/MX/NS/TXT records over time.