Check-Host.cc

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

api.map.baidu.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 api.map.baidu.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
5
A/AAAA targets
Subdomains
—
CT + scan + body
Record Types
1
seen in DNS
Observed Certs
—
in our scans

DNS Records

A
180.101.49.70, 180.101.50.17, 180.76.11.161, 180.76.11.208, 180.76.11.230
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.

47.244.174.75:443 href · ×63
39.105.164.113:80 href · ×22
39.105.164.113:443 href · ×22
123.56.130.138:443 href · ×16
114.116.22.231:80 href · ×15
129.204.247.133:443 href · ×15
47.104.73.59:443 href · ×14
180.167.224.96:8081 href · ×14
139.9.228.247:81 href · ×14
175.178.241.90:443 href · ×12
120.76.136.56:80 href · ×12
111.34.19.234:8888 href · ×10
8.134.57.65:443 href · ×10
140.210.207.28:443 href · ×10
47.92.134.10:443 href · ×10
180.167.213.204:8443 href · ×9
101.37.23.129:80 href · ×9
121.37.240.33:443 href · ×9
101.200.37.209:443 href · ×9
47.98.147.108:80 href · ×9
1.95.12.170:80 href · ×8
47.115.209.228:80 href · ×8
36.134.87.224:443 href · ×8
120.78.127.48:443 href · ×8
118.31.67.28:443 href · ×8
113.240.114.55:443 href · ×8
112.115.191.109:80 href · ×8
1.95.12.170:443 href · ×8
8.134.204.86:443 href · ×8
114.55.209.85:443 href · ×8
47.108.162.192:80 href · ×8
110.42.213.177:443 href · ×8
122.224.147.119:80 href · ×8
101.201.80.203:80 href · ×8
47.120.15.143:443 href · ×7
39.107.247.192:80 href · ×7
47.110.240.169:80 href · ×7
139.9.228.247:443 href · ×7
39.100.112.252:8443 href · ×7
117.175.146.59:80 href · ×7
218.90.225.169:8081 href · ×7
39.107.91.254:443 href · ×7
47.119.114.98:80 href · ×7
140.143.49.179:443 href · ×6
39.106.53.190:80 href · ×6
124.71.184.189:443 href · ×6
123.206.19.170:443 href · ×6
124.221.85.45:443 href · ×6
216.225.207.40:443 href · ×6
113.250.181.107:443 href · ×6

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 180.76.11.230 2026-05-25 21:56:50.553 2026-07-28 19:57:26.855
A 180.76.11.161 2026-05-25 21:56:50.553 2026-07-28 19:57:26.855
A 180.76.11.208 2026-05-25 21:56:50.553 2026-07-28 19:57:26.855
A 180.101.50.17 2026-07-28 10:09:41.387 2026-07-28 10:09:41.387
A 180.101.49.70 2026-07-28 10:09:41.387 2026-07-28 10:09:41.387