Check-Host.cc

Domain

cc.163.com

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

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

DNS Records

A
34.95.101.94
AAAA
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

Subject: *.cc.163.com
Issuer: GeoTrust TLS ECC CA G1
SANs: *.cc.163.com, cc.163.com
Subject: *.cc.163.com
Issuer: GeoTrust TLS ECC CA G1
SANs: *.cc.163.com, cc.163.com
Subject: *.cc.163.com
Issuer: GeoTrust TLS ECC CA G1
SANs: *.cc.163.com, cc.163.com
Subject: ros.patch.netease.com
Issuer: ros.patch.netease.com
SANs: 206.189.83.142, allysdk.easebar.com, allysdk.matrix.easebar.com, api.cc.163.com, appdump.x.netease.com, applogsg.matrix.netease.com, cc.163.com, client.gdl.netease.com, g103.gdl.netease.com, g103.gph.netease.com, g61.gph.netease.com, g61.update.easebar.com, listerr.nie.netease.com, matrix.netease.com, mgbsdksgtest.matrix.netease.com, mpay-os-server.webapp.163.com, nie.gdl.netease.com, nie.netease.com, qrcode-service.webapp.163.com, res.ros.netease.com, ros.gph.netease.com, ros.patch.netease.com, s.win.163.com, unisdk.update.netease.com
Subject: *.cc.163.com
Issuer: GeoTrust TLS ECC CA G1
SANs: *.cc.163.com, cc.163.com
Subject: *.cc.163.com
Issuer: GeoTrust TLS ECC CA G1
SANs: *.cc.163.com, cc.163.com
Subject: *.cc.163.com
Issuer: GeoTrust TLS ECC CA G1
SANs: *.cc.163.com, cc.163.com
Subject: *.cc.163.com
Issuer: GeoTrust TLS ECC CA G1
SANs: *.cc.163.com, cc.163.com
Subject: *.cc.163.com
Issuer: GeoTrust TLS ECC CA G1
SANs: *.cc.163.com, cc.163.com
Subject: *.cc.163.com
Issuer: GeoTrust TLS ECC CA G1
SANs: *.cc.163.com, cc.163.com
Subject: *.cc.163.com
Issuer: GeoTrust TLS ECC CA G1
SANs: *.cc.163.com, cc.163.com
Subject: *.cc.163.com
Issuer: GeoTrust G2 TLS CN RSA4096 SHA256 2022 CA1
SANs: *.cc.163.com, cc.163.com
Subject: *.cc.163.com
Issuer: GeoTrust G2 TLS CN RSA4096 SHA256 2022 CA1
SANs: *.cc.163.com, cc.163.com

IPs Citing This Domain

Hosts whose HTML body references this domain. Strong signal for origin/mirror/embed discovery.

43.128.47.99:443 href · ×2
124.221.178.197:80 href · ×2
106.54.24.206:80 href · ×1
42.186.125.232:80 href · ×1
124.223.4.156:80 href · ×1
43.132.129.239:443 href · ×1
42.186.125.232:443 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
A 34.95.101.94 2026-05-26 07:55:56.671 2026-07-27 21:58:55.553