Check-Host.cc

Domain

ja.wordpress.org

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

Run a live full scan of ja.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.

219.94.215.58:443 href · ×5
118.27.2.146:443 href · ×4
153.126.162.120:80 href · ×4
153.126.159.35:80 href · ×4
140.227.88.9:80 href · ×4
153.126.135.100:443 href · ×4
54.199.189.203:443 href · ×4
118.27.15.214:443 href · ×4
54.199.189.203:80 href · ×4
150.60.44.127:80 href · ×4
153.121.60.81:80 href · ×4
153.127.242.118:443 href · ×4
183.90.233.59:443 href · ×3
150.60.50.51:80 href · ×3
140.227.21.106:80 href · ×3
133.242.227.71:80 href · ×3
157.7.221.98:443 href · ×2
54.95.101.32:443 href · ×2
61.126.18.247:80 href · ×2
103.5.178.65:443 href · ×2
161.34.18.163:443 href · ×2
116.80.15.237:80 href · ×2
153.127.62.175:80 href · ×2
203.179.132.247:80 href · ×2
153.126.205.237:443 href · ×2
153.127.252.148:80 href · ×2
210.154.236.177:443 href · ×2
35.212.150.32:443 href · ×2
57.181.33.219:443 href · ×2
160.16.85.127:443 href · ×2
34.149.167.59:443 href · ×2
18.182.190.16:443 href · ×2
61.126.17.80:443 href · ×2
141.147.146.74:80 href · ×2
52.196.48.105:443 href · ×2
61.44.57.204:443 href · ×2
49.212.135.217:443 href · ×2
61.126.48.124:80 href · ×2
158.199.188.74:80 href · ×2
163.44.3.161:80 href · ×2
18.179.64.231:80 href · ×2
157.205.179.174:80 href · ×2
210.154.237.10:80 href · ×2
13.231.24.109:80 href · ×2
133.17.110.177:443 href · ×2
153.187.143.81:443 href · ×2
35.200.67.55:80 href · ×2
13.113.194.161:80 href · ×2
219.117.220.212:443 href · ×2
164.46.50.108: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

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-23 20:39:21.191
A 198.143.164.252 2026-05-25 21:56:50.553 2026-06-23 20:39:21.191
TXT google-site-verification=UL0sGJ1dZbCT4J7pGrLW3hqM_I1LJ8pUi2WBEI_98kI 2026-05-26 00:03:35.658 2026-07-28 19:48:54.308
MX 10 smtp2-ord.wordpress.org 2026-05-26 00:03:35.658 2026-05-31 13:15:40.713
NS ns4.wordpress.org 2026-05-26 00:03:35.658 2026-07-28 19:48:54.308
TXT google-site-verification=t8FjG1vzC4OFZJ8qL4SkR8xxtLyKldXKbswyeemQS5w 2026-05-26 00:03:35.658 2026-07-28 19:48:54.308
NS ns2.wordpress.org 2026-05-26 00:03:35.658 2026-07-28 19:48:54.308
CAA 0 issue "letsencrypt.org;validationmethods=dns-01;accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/53691143" 2026-05-26 00:03:35.658 2026-07-28 19:48:54.308
NS ns3.wordpress.org 2026-05-26 00:03:35.658 2026-07-28 19:48:54.308
CAA 0 iodef "mailto:caa@wordpress.org" 2026-05-26 00:03:35.658 2026-07-28 19:48:54.308
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-26 00:03:35.658 2026-06-23 20:39:21.191
NS ns1.wordpress.org 2026-05-26 00:03:35.658 2026-07-28 19:48:54.308
MX 10 smtp1-ord.wordpress.org 2026-05-26 00:03:35.658 2026-05-31 13:15:40.713
MX 10 smtp2-dca.wordpress.org 2026-06-14 22:08:58.337 2026-07-28 19:48:54.308
MX 10 smtp1-dca.wordpress.org 2026-06-14 22:08:58.337 2026-07-28 19:48:54.308
A 66.6.42.252 2026-07-16 00:01:48.367 2026-07-28 19:48:54.308
AAAA 2620:109:b00a::4206:2afc 2026-07-16 00:01:48.367 2026-07-28 19:48:54.308
TXT v=spf1 ip4:66.6.42.0/24 ip4:66.155.40.0/24 include:helpscoutemail.com -all 2026-07-16 00:01:48.367 2026-07-28 19:48:54.308