Skip to content
https://automattic.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
93
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Sao Paulo, Brazil
200 OK
Checks
9
6 PASS 2 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.

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

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

Certificate validity

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

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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
2 A records, 6 ms lookup
PASS
2 A records, 6 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 192.0.78.25, 192.0.78.24
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns2.automattic.com, ns3.automattic.com, ns4.automattic.com, ns1.automattic.com
Info::
2 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: 6 ms
Got: 6 ms
A192.0.78.25, 192.0.78.24
AAAA
CNAME
NSns2.automattic.com, ns3.automattic.com, ns4.automattic.com, ns1.automattic.com
MX
10 mx-ams.automattic.com
10 mx-dfw.automattic.com
TXT
SPF v=spf1 include:_spf.automattic.com include:mail.zendesk.com include:mg-spf.green...
google-site-verification=F4jw0P5BvBnjqDSVJEhYv3LEU2WLuqChlBLJEYA2SO0
spf2.0/mfrom a mx ?all
gradle-verification=1AG8E2HVI4P8EOH4BK5URAEO6JVML
atlassian-domain-verification=HLvi8VknRfLwuOZ7TmiaKM8GgOgai45SxxeWZddVaOBMgWielc...
yahoo-verification-key=8dNdxvmgAf9M2eCeh79q5CpzcsN5GkkT9db3Z5Rr3Sk=
figma-domain-verification=a2e41510ac6b0c5745595c76770385bfd602709c6d04e80ef830c9...
google-site-verification=l3pF3D6Nfuk18StNUFWXaEEIVTjBWWHvvZYP9sXEAcc
CAALookup not available with standard resolver
Resolved in 6 ms

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://automattic.com

https://automattic.com

13 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://automattic.com20013 msHTTP/1.1nginx
A+
Crawlability
robots.txt present, sitemap with 1 URLs
PASS
robots.txt present, sitemap with 1 URLs
Info::
robots.txt is present
Got: 628 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1 entries
Info::
Sitemap index with 1 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 628 B Sitemaps referenced 2 User-agents * Blocking No — crawling allowed
# 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://automattic.com/sitemap.xml
Sitemap: https://automattic.com/news-sitemap.xml

User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php
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 Fri, 30 Jan 2026 17:40:57 +0000

sitemap.xml 200 OK
Type Sitemap Index URLs 1 entries Valid XML Yes
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.automattic.com/
200https://automattic.com/

Preferred variant: non-www

HTTP → HTTPS

301http://automattic.com/ https://automattic.com/

Consistent

A+
Domain Intelligence
automattic.com — via MarkMonitor Inc., 22 years, 1 months old, hosted on WordPress.com (Automattic)
PASS
automattic.com — via MarkMonitor Inc., 22 years, 1 months old, hosted on WordPress.com (Automattic)
Info::
Domain registered until Jun 19, 2033 (7 years, 3 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.
Warning::
Registrar lock is NOT enabled
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.
Info::
Hosting: WordPress.com (Automattic)
Got: AS2635
Domain expiry

2560 days

June 19, 2033

SSL certificate

81 days

Issued by Let's Encrypt

Domain age

22 years, 1 months

Registered June 19, 2004

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

WordPress.com (Automattic)

ASN AS2635

192.0.78.25

Registrar

MarkMonitor Inc.

Unlocked 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
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar MarkMonitor Inc.
Created June 19, 2004 (22 years, 1 months ago)
Expires June 19, 2033 (7 years, 3 months)
Last Updated August 28, 2023
Name Servers ns1.automattic.com, ns2.automattic.com, ns3.automattic.com, ns4.automattic.com
DNSSEC Not enabled
Hosting
IP Address 192.0.78.25
ASN AS2635 (AUTOMATTIC - Automattic, Inc, US)
Provider WordPress.com (Automattic)
Data source: rdap (0.6s)

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

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.

Why this matters

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

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

Connection waterfall

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

Send Feedback