Check-Host.cc

Domain

developer.wordpress.org

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

Run a live full scan of developer.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
4
A/AAAA targets
Subdomains
CT + scan + body
Record Types
6
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.

68.171.222.236:443 href · ×39
107.180.115.199:443 href · ×20
154.38.189.25:443 href · ×18
68.183.197.56:80 href · ×13
45.76.99.127:80 href · ×12
173.231.244.81:443 href · ×12
148.66.155.133:443 href · ×10
50.62.203.144:443 href · ×10
188.166.114.106:443 href · ×10
157.245.18.173:443 href · ×9
92.205.89.233:443 href · ×9
162.246.58.104:443 href · ×8
72.167.45.48:443 href · ×8
107.180.50.173:80 href · ×8
69.49.233.190:443 href · ×8
104.152.110.166:8443 href · ×8
20.193.133.223:443 href · ×7
172.104.239.229:443 href · ×7
173.205.124.84:80 href · ×7
103.186.120.145:80 href · ×7
184.168.20.130:443 href · ×7
84.247.2.151:443 href · ×7
69.163.179.248:443 href · ×7
43.229.85.165:443 href · ×6
45.32.245.52:80 href · ×6
146.71.72.6:443 href · ×6
164.92.90.236:80 href · ×6
159.223.80.192:443 href · ×6
154.16.119.61:80 href · ×6
185.181.255.59:443 href · ×6
103.211.202.96:443 href · ×6
208.109.70.243:443 href · ×5
145.239.199.33:80 href · ×5
165.22.218.222:80 href · ×5
216.194.161.148:443 href · ×5
134.209.126.97:443 href · ×5
213.74.194.120:443 href · ×5
159.203.79.27:443 href · ×5
167.235.234.92:443 href · ×5
81.169.253.27:80 href · ×5
69.195.85.183:443 href · ×5
95.216.42.142:443 href · ×5
216.194.161.148:80 href · ×5
54.245.52.129:443 href · ×5
50.63.135.12:80 href · ×4
20.224.68.172:443 href · ×4
159.69.107.231:443 href · ×4
34.100.164.29:80 href · ×4
109.234.36.116:80 href · ×4
185.8.129.106:443 href · ×4

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:13:35.709
A 198.143.164.252 2026-05-25 21:56:50.553 2026-06-23 20:13:35.709
TXT google-site-verification=UL0sGJ1dZbCT4J7pGrLW3hqM_I1LJ8pUi2WBEI_98kI 2026-05-26 00:17:38.499 2026-07-28 19:48:54.308
MX 10 smtp2-ord.wordpress.org 2026-05-26 00:17:38.499 2026-05-31 10:21:40.736
NS ns4.wordpress.org 2026-05-26 00:17:38.499 2026-07-28 19:48:54.308
TXT google-site-verification=t8FjG1vzC4OFZJ8qL4SkR8xxtLyKldXKbswyeemQS5w 2026-05-26 00:17:38.499 2026-07-28 19:48:54.308
NS ns2.wordpress.org 2026-05-26 00:17:38.499 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:17:38.499 2026-07-28 19:48:54.308
NS ns3.wordpress.org 2026-05-26 00:17:38.499 2026-07-28 19:48:54.308
CAA 0 iodef "mailto:caa@wordpress.org" 2026-05-26 00:17:38.499 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:17:38.499 2026-06-23 20:13:35.709
NS ns1.wordpress.org 2026-05-26 00:17:38.499 2026-07-28 19:48:54.308
MX 10 smtp1-ord.wordpress.org 2026-05-26 00:17:38.499 2026-05-31 10:21:40.736
MX 10 smtp2-dca.wordpress.org 2026-06-14 22:52:09.672 2026-07-28 19:48:54.308
MX 10 smtp1-dca.wordpress.org 2026-06-14 22:52:09.672 2026-07-28 19:48:54.308
A 66.6.42.252 2026-07-15 22:29:42.589 2026-07-28 19:48:54.308
AAAA 2620:109:b00a::4206:2afc 2026-07-15 22:29:42.589 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-15 22:29:42.589 2026-07-28 19:48:54.308