Check-Host.cc

Domain

cn.wordpress.org

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

Run a live full scan of cn.wordpress.org

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
198.143.164.252, 66.6.42.252
AAAA
2607:f978:5:8002::c68f:a4fc, 2620:109:b00a::4206:2afc
MX
10 smtp1-dca.wordpress.org, 10 smtp1-ord.wordpress.org, 10 smtp2-dca.wordpress.org, 10 smtp2-ord.wordpress.org
NS
ns1.wordpress.org, ns2.wordpress.org, ns3.wordpress.org, ns4.wordpress.org
TXT
google-site-verification=UL0sGJ1dZbCT4J7pGrLW3hqM_I1LJ8pUi2WBEI_98kI, google-site-verification=t8FjG1vzC4OFZJ8qL4SkR8xxtLyKldXKbswyeemQS5w, v=spf1 ip4:66.6.42.0/24 ip4:66.155.40.0/24 include:helpscoutemail.com -all, v=spf1 ip4:66.6.42.0/24 ip4:66.155.40.0/24 ip4:198.143.164.0/24 include:helpscoutemail.com -all
CNAME
CAA
0 iodef "mailto:caa@wordpress.org", 0 issue "letsencrypt.org;validationmethods=dns-01;accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/53691143"

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.

45.145.229.7:443 href · ×9
47.117.181.70:443 href · ×6
47.93.101.160:80 href · ×6
69.172.211.73:443 href · ×4
122.51.68.3:443 href · ×4
50.116.14.221:80 href · ×4
154.8.176.28:443 href · ×4
39.97.241.224:80 href · ×4
8.159.156.152:443 href · ×4
47.107.177.58:443 href · ×4
149.129.85.91:443 href · ×4
150.158.114.109:80 href · ×4
155.138.161.53:80 href · ×4
124.220.98.67:443 href · ×4
43.143.113.126:80 href · ×4
193.123.232.28:80 href · ×3
47.121.181.207:80 href · ×3
152.70.245.182:443 href · ×3
129.146.83.233:443 href · ×3
8.148.179.79:80 href · ×3
82.156.16.17:443 href · ×3
39.106.152.131:443 href · ×3
153.127.9.86:443 href · ×3
43.133.233.59:80 href · ×3
8.210.233.199:443 href · ×3
106.15.93.149:80 href · ×3
38.64.57.212:443 href · ×3
132.226.117.239:443 href · ×3
38.147.190.243:443 href · ×3
175.178.181.193:80 href · ×2
112.126.69.70:80 href · ×2
8.145.42.96:80 href · ×2
172.105.239.169:443 href · ×2
101.42.6.27:80 href · ×2
110.42.232.192:443 href · ×2
49.233.22.238:80 href · ×2
118.24.25.95:443 href · ×2
47.92.167.107:443 href · ×2
47.116.7.214:80 href · ×2
43.128.231.117:443 href · ×2
103.27.111.95:80 href · ×2
107.172.5.215:80 href · ×2
39.104.17.227:80 href · ×2
47.95.38.254:443 href · ×2
101.32.18.176:443 href · ×2
47.111.16.83:80 href · ×2
60.205.203.98:80 href · ×2
39.106.205.80:80 href · ×2
47.240.8.181:80 href · ×2
47.111.191.43: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
AAAA 2607:f978:5:8002::c68f:a4fc 2026-05-25 21:56:50.553 2026-06-24 00:02:29.415
A 198.143.164.252 2026-05-25 21:56:50.553 2026-06-24 00:02:29.415
TXT google-site-verification=UL0sGJ1dZbCT4J7pGrLW3hqM_I1LJ8pUi2WBEI_98kI 2026-05-25 22:05:29.416 2026-07-28 20:39:29.599
MX 10 smtp2-ord.wordpress.org 2026-05-25 22:05:29.416 2026-05-31 13:09:40.722
NS ns4.wordpress.org 2026-05-25 22:05:29.416 2026-07-28 20:39:29.599
TXT google-site-verification=t8FjG1vzC4OFZJ8qL4SkR8xxtLyKldXKbswyeemQS5w 2026-05-25 22:05:29.416 2026-07-28 20:39:29.599
NS ns2.wordpress.org 2026-05-25 22:05:29.416 2026-07-28 20:39:29.599
NS ns3.wordpress.org 2026-05-25 22:05:29.416 2026-07-28 20:39:29.599
TXT v=spf1 ip4:66.6.42.0/24 ip4:66.155.40.0/24 ip4:198.143.164.0/24 include:helpscoutemail.com -all 2026-05-25 22:05:29.416 2026-06-24 00:26:21.061
NS ns1.wordpress.org 2026-05-25 22:05:29.416 2026-07-28 20:39:29.599
MX 10 smtp1-ord.wordpress.org 2026-05-25 22:05:29.416 2026-05-31 13:09:40.722
CAA 0 issue "letsencrypt.org;validationmethods=dns-01;accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/53691143" 2026-05-25 23:59:40.866 2026-07-28 20:39:29.599
CAA 0 iodef "mailto:caa@wordpress.org" 2026-05-25 23:59:40.866 2026-07-28 20:39:29.599
MX 10 smtp2-dca.wordpress.org 2026-06-06 04:17:01.281 2026-07-28 20:39:29.599
MX 10 smtp1-dca.wordpress.org 2026-06-06 04:17:01.281 2026-07-28 20:39:29.599
A 66.6.42.252 2026-07-15 22:29:42.589 2026-07-28 20:39:29.599
AAAA 2620:109:b00a::4206:2afc 2026-07-15 22:29:42.589 2026-07-28 20:39:29.599
TXT v=spf1 ip4:66.6.42.0/24 ip4:66.155.40.0/24 include:helpscoutemail.com -all 2026-07-15 22:29:42.589 2026-07-28 20:39:29.599