Check-Host.cc

Domain

developer.umeng.com

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

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

DNS Records

A
59.82.29.162, 59.82.29.248, 59.82.29.249, 59.82.31.92, 59.82.60.44
AAAA
2408:4001:f00::14d, 2408:4001:f00::169, 2408:4001:f00::2a8
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.

211.149.170.89:443 href · ×2
47.99.91.98:8080 href · ×2
112.74.195.21:443 href · ×1
1.13.92.114:80 href · ×1
112.74.195.21: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 2408:4001:f00::14d 2026-05-27 07:21:42.379 2026-07-26 19:32:25.567
A 59.82.29.162 2026-05-27 07:21:42.379 2026-05-27 07:21:42.379
A 59.82.29.249 2026-06-15 00:07:36.295 2026-06-15 00:07:36.295
A 59.82.60.44 2026-06-20 14:13:48.766 2026-06-20 14:13:48.766
AAAA 2408:4001:f00::169 2026-06-20 14:13:48.766 2026-06-20 14:13:48.766
AAAA 2408:4001:f00::2a8 2026-07-23 15:46:15.105 2026-07-23 15:46:15.105
A 59.82.29.248 2026-07-23 15:46:15.105 2026-07-23 15:46:15.105
A 59.82.31.92 2026-07-26 19:32:25.567 2026-07-26 19:32:25.567