Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Preferred variant: non-www
HTTP → HTTPS
HTTP version does not redirect to HTTPS
BTLS Certificate Expiry & Recommendations77 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
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 Records2 A records, 5 ms lookupPASS
| A | 192.0.78.24, 192.0.78.25 |
| AAAA | — |
| CNAME | — |
| NS | ns1.automattic.com, ns2.automattic.com, ns3.automattic.com |
| MX | 0 mx1.bur.wordpress.com 0 mx1.dfw.wordpress.com |
| TXT | SPF v=spf1 include:_spf.automattic.com -all |
| CAA | Lookup not available with standard resolver |
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
ARedirect Chain1 redirect(s), 357 ms totalPASS
https://wp.com
180 ms · HTTP/1.1
https://wordpress.com/
177 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://wp.com | 301 | 180 ms | HTTP/1.1 | nginx |
| 2 | https://wordpress.com/ | 200 | 177 ms | HTTP/1.1 | nginx |
See the visual redirect chain in the HTTP Probe tab →
A+Crawlabilityrobots.txt present, sitemap with 1 URLsPASS
# If you are regularly crawling WordPress.com sites, please use our firehose to receive real-time push updates instead.
# Please see https://developer.wordpress.com/docs/firehose/ for more details.
Sitemap: https://wordpress.com/sitemap.xml
Sitemap: https://wordpress.com/news-sitemap.xml
Sitemap: https://wordpress.com/go/sitemap.xml
Sitemap: https://wordpress.com/blog/sitemap.xml
Sitemap: https://wordpress.com/support/sitemap.xml
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php
Disallow: /typo/?subdomain=
Disallow: /read/
Disallow: /*/read/
Allow: /forums/topic-tag/reader/
Allow: /*/forums/topic-tag/reader/
Allow: /support/reader/
Allow: /*/support/reader/
Disallow: /reader/
Disallow: /*/reader/
Allow: /log-in/
Allow: /log-in$
Disallow: /log-in?
Disallow: /abuse/?*
Disallow: /abuse?*
Disallow: /plugins/?s=
Disallow: /*/plugins/?s=
Disallow: /*?aff=
Disallow: /*&aff=
Disallow: /*?affiliate=
Disallow: /*&affiliate=
Disallow: /*?cid=
Disallow: /*&cid=
Disallow: /*?irclickid=
Disallow: /*&irclickid=
Disallow: /*/?like_comment=
Disallow: /*?retry=
Disallow: /*?sid=
Disallow: /*?action=
Disallow: /wp-login.php
Disallow: /wp-signup.php
Disallow: /press-this.php
Disallow: /remote-login.php
Disallow: /activate/
Disallow: /cgi-bin/
Disallow: /mshots/v1/
Disallow: /next/
Disallow: /public.api/
# This file was generated on Thu, 16 Apr 2026 17:22:43 +0000
A+Domain Intelligencewp.com — via MarkMonitor Inc., 29 years, 5 months old, hosted on WordPress.com (Automattic)PASS
590 days
March 29, 2028
77 days
Issued by Let's Encrypt
29 years, 5 months
Registered March 28, 1997
Not enabled
Protects against DNS spoofing
WordPress.com (Automattic)
ASN AS2635
192.0.78.24
MarkMonitor Inc.
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.
Learn more ▾ ▴
Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.
Source: ICANN / domain-security best practice