Check-Host.cc

Domain

kdocs.cn

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

Run a live full scan of kdocs.cn

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
8
A/AAAA targets
Subdomains
31
CT + scan + body
Record Types
3
seen in DNS
Observed Certs
5
in our scans

DNS Records

A
172.96.115.150, 98.98.145.230, 98.98.78.134
AAAA
MX
NS
ns3.dnsv5.com, ns4.dnsv5.com
TXT
globalsign-domain-verification=qWmLXXET2rnZyKt-y2QVzDDivsjexXO_ldk-SHhFry, google-site-verification=OyouGYT1NJ_EnwluZ7FYBl-m4Ou8HBziKo5QlOr1x9o, v=spf1 -all
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

Every subdomain we know about — harvested from CT-log SANs, scan-observed certs and HTML body references — paired with its current A/AAAA target.

Subdomain Resolves to Last seen
f.kdocs.cn 2026-07-26 22:47:09.700
kdocs.cn 2026-07-27 07:02:22.555
www.kdocs.cn 2026-07-28 14:28:46.692
365.kdocs.cn 2026-07-24 08:51:20.706
developer.kdocs.cn 2026-06-15 01:22:55.677
p.kdocs.cn 2026-06-20 01:51:58.737
test09.kdocs.cn 2026-06-01 15:33:43.551
weboffice-ksc-bj.kdocs.cn
1970-01-01 00:00:00.000

Tech Stack

Tech detection pending

Wappalyzer-rules detect CMS, frameworks, analytics, JS libs and server-side languages on this domain.

TLS Certificates

Subject: *.kdocs.cn
Issuer: GeoTrust G2 TLS CN RSA4096 SHA256 2022 CA1
SANs: *.kdocs.cn, kdocs.cn
Subject: *.kdocs.cn
Issuer: GeoTrust G2 TLS CN RSA4096 SHA256 2022 CA1
SANs: *.kdocs.cn, kdocs.cn
Subject: *.kdocs.cn
Issuer: GeoTrust G2 TLS CN RSA4096 SHA256 2022 CA1
SANs: *.kdocs.cn, kdocs.cn

IPs Citing This Domain

No citing IPs found yet

As the world-sweep progresses, hosts referencing this domain in their HTML will surface here.

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
TXT v=spf1 -all 2026-05-25 22:09:29.497 2026-05-31 01:59:40.813
NS ns3.dnsv5.com 2026-05-25 22:09:29.497 2026-05-31 01:59:40.813
TXT google-site-verification=OyouGYT1NJ_EnwluZ7FYBl-m4Ou8HBziKo5QlOr1x9o 2026-05-25 22:09:29.497 2026-05-31 01:59:40.813
TXT globalsign-domain-verification=qWmLXXET2rnZyKt-y2QVzDDivsjexXO_ldk-SHhFry 2026-05-25 22:09:29.497 2026-05-31 01:59:40.813
A 98.98.145.230 2026-05-25 22:09:29.497 2026-07-27 07:02:22.555
NS ns4.dnsv5.com 2026-05-25 22:09:29.497 2026-05-31 01:59:40.813
A 98.98.78.134 2026-05-26 05:13:56.978 2026-07-26 14:36:44.369
A 172.96.115.150 2026-05-26 05:13:56.978 2026-07-26 14:36:44.369