Check-Host.cc

Domain

jq.qq.com

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

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

DNS Records

A
43.129.2.192, 43.159.233.222
AAAA
240d:c000:2010:1803:0:9a9d:8c8d:79bf, 240d:c000:2010:1807:0:9a9d:8c6a:9f37
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.

43.138.212.71:8088 href · ×19
47.110.44.76:80 href · ×14
47.104.212.122:443 href · ×12
120.24.148.192:81 href · ×11
154.8.136.217:80 href · ×8
82.156.122.67:80 href · ×8
43.248.117.183:81 href · ×8
47.103.20.186:443 href · ×7
192.9.156.16:443 href · ×6
82.157.187.138:80 href · ×5
106.12.145.180:80 href · ×5
124.223.7.39:80 href · ×4
149.30.242.146:80 href · ×4
115.190.230.123:80 href · ×4
106.53.30.177:80 href · ×4
120.48.164.160:80 href · ×4
193.112.105.33:80 href · ×4
119.188.165.6:8088 href · ×4
47.115.160.108:80 href · ×4
82.156.38.77:80 href · ×4
82.157.198.105:443 href · ×4
103.10.85.46:80 href · ×4
47.103.220.93:80 href · ×4
81.68.218.180:80 href · ×4
119.29.3.207:80 href · ×4
123.57.129.46:443 href · ×4
47.109.58.62:80 href · ×4
43.99.60.214:80 href · ×4
120.76.42.212:80 href · ×4
47.119.179.90:443 href · ×4
111.230.93.12:80 href · ×4
159.75.93.238:80 href · ×4
47.114.85.75:80 href · ×4
39.106.166.216:80 href · ×4
60.205.128.56:80 href · ×4
182.92.216.225:443 href · ×4
43.143.199.106:80 href · ×3
120.24.175.127:443 href · ×3
49.233.45.13:80 href · ×3
39.104.13.96:80 href · ×3
8.153.175.126:443 href · ×3
118.24.57.87:443 href · ×3
49.235.122.18:80 href · ×3
101.43.234.2:80 href · ×3
27.150.183.53:80 href · ×3
39.98.60.253:443 href · ×3
8.163.110.91:80 href · ×3
111.228.8.34:80 href · ×3
49.235.122.18:443 href · ×3
121.40.149.69:443 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

Domain timeline pending

Passive-DNS history accumulates as our forward-DNS crawler observes A/AAAA/MX/NS/TXT records over time.