Skip to content
https://developer.wordpress.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
97
GRADE
A+
FIX
1
REVIEW
1
PASS
7
INFO
0
Probed from New York, United Stated
200 OK
Checks
9
7 PASS 1 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

B
TLS Certificate Expiry & Recommendations
82 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

82
days left
0d 30d 60d 90d+

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A
DNS Records
1 A records, 2 ms lookup
PASS
1 A records, 2 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 198.143.164.252
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2607:f978:5:8002::c68f:a4fc
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: wordpress.org
Info::
4 nameserver(s) configured
Got: ns1.wordpress.org, ns3.wordpress.org, ns4.wordpress.org, ns2.wordpress.org
Info::
1 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 2 ms
Got: 2 ms
A198.143.164.252
AAAA2607:f978:5:8002::c68f:a4fc
CNAMEwordpress.org
NSns1.wordpress.org, ns3.wordpress.org, ns4.wordpress.org, ns2.wordpress.org
MX
10 mail.wordpress.org
TXT
google-site-verification=UL0sGJ1dZbCT4J7pGrLW3hqM_I1LJ8pUi2WBEI_98kI
google-site-verification=t8FjG1vzC4OFZJ8qL4SkR8xxtLyKldXKbswyeemQS5w
SPF v=spf1 ip4:66.155.40.0/24 ip4:198.143.164.0/24 include:helpscoutemail.com -all
CAALookup not available with standard resolver
Resolved in 2 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more ▾

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://developer.wordpress.org

https://developer.wordpress.org

61 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://developer.wordpress.org20061 msHTTP/1.1nginx
A+
IPv6 Readiness
IPv6 reachable (18 ms)
PASS
IPv6 reachable (18 ms)
Info::
IPv6 is configured and reachable at 2607:f978:5:8002::c68f:a4fc
Got: 18 ms connect
IPv6 Ready
AAAA Records 2607:f978:5:8002::c68f:a4fc Connection Reachable (18 ms)
A+
Crawlability
robots.txt present, sitemap with 2 URLs
PASS
robots.txt present, sitemap with 2 URLs
Info::
robots.txt is present
Got: 366 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 2 entries
Info::
Sitemap index with 2 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 366 B Sitemaps referenced 4 User-agents * Blocking No — crawling allowed
Sitemap: https://developer.wordpress.org/sitemap.xml
Sitemap: https://developer.wordpress.org/news-sitemap.xml
Sitemap: https://developer.wordpress.org/news/sitemap.xml
Sitemap: https://developer.wordpress.org/news/news-sitemap.xml
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php
Allow: /wp-admin/load-scripts.php
Allow: /wp-admin/load-styles.php
sitemap.xml 200 OK
Type Sitemap Index URLs 2 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

https://www.developer.wordpress.org/
200https://developer.wordpress.org/

HTTP → HTTPS

301http://developer.wordpress.org/ → https://developer.wordpress.org/

Consistent

A+
Domain Intelligence
wordpress.org — via MarkMonitor Inc., 23 years, 4 months old
PASS
wordpress.org — via MarkMonitor Inc., 23 years, 4 months old
Info::
Domain registered until Mar 28, 2035 (9 years, 1 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: MarkMonitor Inc.
Domain expiry

3207 days

March 28, 2035

SSL certificate

82 days

Issued by Let's Encrypt

Domain age

23 years, 4 months

Registered March 28, 2003

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2607:f978:5:8002::c68f:a4fc

Registrar

MarkMonitor Inc.

Lock status unknown 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
Registrar MarkMonitor Inc.
Created March 28, 2003 (23 years, 4 months ago)
Expires March 28, 2035 (9 years, 1 months)
Last Updated July 6, 2025
Name Servers ns1.wordpress.org, ns2.wordpress.org, ns3.wordpress.org, ns4.wordpress.org
DNSSEC Not enabled
Hosting
IP Address 2607:f978:5:8002::c68f:a4fc
Data source: rdap (0.1s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

A+
HTTP Probe Timing
Total 87 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
4 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
19 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
22 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
63 ms
Total Time Total request time from DNS lookup through full response.
88 ms

Connection waterfall

DNS Lookup 4 ms TCP Connect 19 ms TLS Handshake 22 ms Server Processing 19 ms Content Transfer 25 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback