Check-Host.cc

Domain

hk.yahoo.com

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

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

DNS Records

A
87.248.107.204, 87.248.107.206, 87.248.116.11, 87.248.116.12, 87.248.119.251, 87.248.119.252
AAAA
2a00:1288:80:807::1, 2a00:1288:80:807::2, 2a00:1288:84:800::1001, 2a00:1288:84:800::1002, 2a00:1288:88:800::4001, 2a00:1288:f035:1fa::2000, 2a00:1288:f035:1fa::4000
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.

124.220.222.26:443 href · ×2
1.36.131.99:8080 href · ×1
45.82.56.241:443 href · ×1
114.115.184.193:443 href · ×1
198.46.253.117:443 href · ×1
144.24.86.21:80 href · ×1
141.147.169.246:80 href · ×1
139.99.170.175:443 href · ×1
47.243.44.10:443 href · ×1
45.82.56.241:80 href · ×1
125.59.214.158:80 href · ×1
31.42.188.25:443 href · ×1
192.227.184.229:80 href · ×1
155.248.180.248:80 href · ×1
47.239.226.133:80 href · ×1

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
AAAA 2a00:1288:80:807::1 2026-05-27 00:36:20.779 2026-06-19 09:04:21.210
A 87.248.119.252 2026-05-27 00:36:20.779 2026-07-16 11:23:18.792
AAAA 2a00:1288:80:807::2 2026-05-27 00:36:20.779 2026-06-19 09:04:21.210
A 87.248.119.251 2026-05-27 00:36:20.779 2026-07-16 11:23:18.792
AAAA 2a00:1288:84:800::1002 2026-05-27 13:42:43.904 2026-07-26 08:37:17.900
A 87.248.116.11 2026-05-27 13:42:43.904 2026-07-26 08:37:17.900
AAAA 2a00:1288:84:800::1001 2026-05-27 13:42:43.904 2026-07-26 08:37:17.900
A 87.248.116.12 2026-05-27 13:42:43.904 2026-07-26 08:37:17.900
A 87.248.107.206 2026-05-27 18:03:08.079 2026-05-28 23:39:40.755
A 87.248.107.204 2026-05-27 18:03:08.079 2026-05-27 18:03:08.079
AAAA 2a00:1288:f035:1fa::4000 2026-05-28 23:39:40.755 2026-05-28 23:39:40.755
AAAA 2a00:1288:88:800::4001 2026-05-28 23:39:40.755 2026-05-28 23:39:40.755
AAAA 2a00:1288:f035:1fa::2000 2026-05-28 23:39:40.755 2026-05-28 23:39:40.755