Domain

map.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 map.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

43.129.2.172, 43.129.2.244

AAAA

240d:c000:2010:1803:0:9a8f:f6f7:8727, 240d:c000:2010:1803:0:9a8f:f6fd:a5a6

—

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.

47.87.68.168:443 href · ×10

120.46.128.76:80 href · ×8

39.106.13.58:443 href · ×6

58.87.103.94:80 href · ×6

113.250.188.194:443 href · ×6

47.112.200.226:80 href · ×6

106.227.95.198:443 href · ×6

150.139.234.141:443 href · ×6

122.4.235.94:443 href · ×5

14.22.73.242:80 href · ×5

220.171.53.2:443 href · ×4

139.129.23.38:443 href · ×4

123.57.84.184:80 href · ×4

8.152.155.18:443 href · ×4

1.13.164.154:443 href · ×4

43.136.20.10:8443 href · ×4

118.31.127.26:443 href · ×4

8.133.4.216:80 href · ×4

218.60.119.210:443 href · ×4

123.207.27.47:443 href · ×4

1.13.159.193:443 href · ×4

47.109.50.75:443 href · ×4

47.101.69.242:443 href · ×4

175.27.224.171:443 href · ×4

36.103.192.69:443 href · ×4

47.100.173.86:443 href · ×4

8.159.140.230:443 href · ×4

49.232.82.225:443 href · ×4

159.75.175.248:80 href · ×4

61.154.79.10:443 href · ×4

139.196.255.194:443 href · ×4

47.121.192.34:443 href · ×4

61.156.90.74:443 href · ×4

60.8.92.228:81 href · ×4

118.89.16.206:80 href · ×4

111.229.34.203:80 href · ×4

139.155.246.251:443 href · ×4

118.178.32.201:443 href · ×4

1.12.250.105:443 href · ×4

118.31.175.202:443 href · ×3

39.101.174.94:443 href · ×3

114.55.234.201:443 href · ×3

47.93.188.57:80 href · ×3

1.95.85.249:80 href · ×3

47.93.14.236:8088 href · ×3

114.55.209.117:80 href · ×3

111.229.171.234:443 href · ×3

47.105.56.217:443 href · ×3

36.133.182.33:80 href · ×3

36.133.201.231:443 href · ×3

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.