Check-Host.cc

Try 1.1.1.1 AS13335 check-host.cc /country/de /tld/cc
Domain

zz.bdstatic.com

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

DNS Check HTTP Check Run Full Scan .com TLD

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

DNS Records

A
0.0.0.0, 112.82.180.48, 157.255.63.48, 218.94.231.48, 36.250.226.48, 58.221.32.48
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

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

Hosts whose HTML body references this domain. Strong signal for origin/mirror/embed discovery.

118.196.78.170:443 href · ×5
47.98.213.217:80 href · ×4
106.54.195.164:443 href · ×4
173.213.124.117:443 href · ×4
59.36.171.239:443 href · ×4
173.213.124.135:443 href · ×4
1.14.248.80:443 href · ×4
173.213.124.251:443 href · ×4
103.45.249.96:443 href · ×4
58.63.255.28:80 href · ×4
8.222.180.12:443 href · ×4
173.213.124.18:443 href · ×4
173.213.124.162:443 href · ×4
173.213.124.177:443 href · ×4
173.213.124.107:443 href · ×4
173.213.124.179:443 href · ×4
173.213.124.42:443 href · ×4
173.213.124.150:443 href · ×4
173.213.124.242:443 href · ×4
173.213.124.96:443 href · ×4
173.213.124.36:443 href · ×4
173.213.124.137:443 href · ×4
205.164.27.35:443 href · ×3
8.166.143.228:80 href · ×3
43.240.238.178:443 href · ×3
107.149.106.105:80 href · ×3
23.231.69.114:443 href · ×3
49.51.166.248:80 href · ×3
202.140.140.48:443 href · ×3
23.231.221.129:443 href · ×3
45.125.109.85:443 href · ×3
173.232.165.123:443 href · ×3
38.38.85.233:443 href · ×3
173.232.165.63:443 href · ×3
160.124.22.118:443 href · ×3
101.200.160.81:443 href · ×3
206.119.28.35:443 href · ×3
39.105.49.122:443 href · ×3
129.204.225.177:80 href · ×3
43.226.77.106:80 href · ×3
38.12.45.116:443 href · ×2
47.92.2.36:80 href · ×2
116.62.84.71:443 href · ×2
185.61.208.20:443 href · ×2
43.138.241.164:443 href · ×2
140.188.174.81:443 href · ×2
50.3.0.236:443 href · ×2
168.76.50.76:443 href · ×2
23.231.221.173:443 href · ×2
192.238.144.112:443 href · ×2

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 157.255.63.48 2026-05-25 21:56:50.553 2026-06-17 09:04:18.958
A 218.94.231.48 2026-05-28 16:03:40.742 2026-05-29 00:17:40.753
A 112.82.180.48 2026-06-17 09:13:58.274 2026-06-24 00:12:22.073
A 0.0.0.0 2026-06-18 16:39:36.706 2026-06-18 16:39:36.706
A 58.221.32.48 2026-06-22 18:07:35.073 2026-06-23 02:40:41.453
A 36.250.226.48 2026-07-15 19:40:12.781 2026-07-23 02:32:00.869