Check-Host.cc

Domain

android.myapp.com

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

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

DNS Records

A
129.226.106.5, 129.226.107.102
AAAA
2402:4e00:1020:1400:0:91c6:dd10:d463
MX
NS
ns-cmn1.qq.com, ns-cnc1.qq.com, ns-os1.qq.com, ns-tel1.qq.com
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.25.41.132:80 href · ×12
118.25.41.132:443 href · ×12
223.6.253.38:80 href · ×7
170.106.112.224:443 href · ×6
47.104.137.90:80 href · ×6
47.91.120.64:443 href · ×6
39.108.77.121:80 href · ×4
47.112.137.55:80 href · ×4
47.97.190.104:80 href · ×3
125.89.144.190:443 href · ×3
120.79.14.23:80 href · ×2
49.234.245.158:443 href · ×2
116.63.49.175:80 href · ×2
101.200.121.112:80 href · ×2
120.77.222.236:80 href · ×2
81.69.128.81:443 href · ×2
39.105.157.165:443 href · ×2
43.136.111.244:8443 href · ×2
39.108.105.15:80 href · ×2
121.40.61.42:80 href · ×2
120.24.236.31:443 href · ×2
175.178.176.194:443 href · ×1
47.94.132.177:443 href · ×1
120.25.152.194:443 href · ×1
124.220.154.51:443 href · ×1
120.79.62.115:443 href · ×1
120.76.180.233:443 href · ×1
8.149.230.40:443 href · ×1
121.40.197.165:443 href · ×1
47.97.40.177:443 href · ×1
120.76.180.233:80 href · ×1
47.115.151.52:443 href · ×1
47.94.115.225:443 href · ×1
120.25.101.25:443 href · ×1
47.110.73.26:80 href · ×1
47.95.65.44:80 href · ×1
119.23.214.113:443 href · ×1
124.223.16.80:80 href · ×1
39.104.88.82:80 href · ×1
120.24.236.31: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
NS ns-cnc1.qq.com 2026-05-26 05:43:11.871 2026-05-31 11:43:40.782
NS ns-tel1.qq.com 2026-05-26 05:43:11.871 2026-05-31 11:43:40.782
NS ns-os1.qq.com 2026-05-26 05:43:11.871 2026-05-31 11:43:40.782
AAAA 2402:4e00:1020:1400:0:91c6:dd10:d463 2026-05-26 05:43:11.871 2026-07-27 18:17:12.415
A 129.226.106.5 2026-05-26 05:43:11.871 2026-07-27 18:17:12.415
A 129.226.107.102 2026-05-26 05:43:11.871 2026-07-27 18:17:12.415
NS ns-cmn1.qq.com 2026-05-26 05:43:11.871 2026-05-31 11:43:40.782