Check-Host.cc

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

a.app.qq.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 a.app.qq.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
4
A/AAAA targets
Subdomains
—
CT + scan + body
Record Types
2
seen in DNS
Observed Certs
1
in our scans

DNS Records

A
43.135.106.212, 43.135.106.42
AAAA
240d:c000:2010:1807:0:95ab:8f9:b409, 240d:c000:2010:1807:0:95ab:90c:1a71
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.92.158.100:80 href · ×20
121.42.224.44:80 href · ×18
39.106.80.117:80 href · ×18
1.95.80.42:80 href · ×14
47.116.100.46:80 href · ×12
121.42.137.184:80 href · ×9
118.190.122.172:443 href · ×9
139.224.63.104:443 href · ×9
121.42.225.41:443 href · ×9
139.129.22.212:80 href · ×9
47.111.117.21:443 href · ×6
47.95.65.44:80 href · ×6
8.133.187.215:443 href · ×6
123.206.57.180:8081 href · ×6
120.79.225.104:80 href · ×6
39.98.224.141:443 href · ×5
124.222.147.186:443 href · ×5
114.215.29.196:443 href · ×5
39.98.224.141:80 href · ×5
111.231.208.202:443 href · ×5
47.100.240.178:80 href · ×5
61.160.247.253:443 href · ×5
120.79.95.229:80 href · ×5
120.46.6.160:80 href · ×4
139.198.19.156:443 href · ×4
123.57.1.96:443 href · ×4
118.190.172.182:80 href · ×4
121.42.206.16:80 href · ×4
8.137.123.37:80 href · ×4
49.233.49.192:80 href · ×4
115.29.234.170:443 href · ×4
121.199.64.139:443 href · ×3
47.94.44.135:443 href · ×3
52.88.158.210:80 href · ×3
106.54.42.72:80 href · ×3
47.93.63.232:443 href · ×3
47.93.159.143:443 href · ×3
8.219.219.229:443 href · ×3
47.99.89.8:80 href · ×3
47.99.69.174:80 href · ×3
8.220.183.69:443 href · ×3
47.104.173.206:443 href · ×3
47.94.44.135:80 href · ×3
47.98.46.20:443 href · ×3
59.110.217.214:80 href · ×3
114.55.225.154:443 href · ×2
120.79.244.105:80 href · ×2
120.79.244.105:443 href · ×2
58.56.78.71:80 href · ×2
39.104.97.26:80 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 43.135.106.212 2026-05-25 22:02:50.525 2026-07-28 19:31:00.676
AAAA 240d:c000:2010:1807:0:95ab:8f9:b409 2026-05-25 22:02:50.525 2026-07-28 19:31:00.676
AAAA 240d:c000:2010:1807:0:95ab:90c:1a71 2026-05-25 22:02:50.525 2026-07-28 19:31:00.676
A 43.135.106.42 2026-05-25 22:02:50.525 2026-07-28 19:31:00.676