Skip to content
https://gravatar.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
92
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from New York, United Stated
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
84 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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
4 A records, 5 ms lookup
PASS
4 A records, 5 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 192.0.80.240, 192.0.80.239, 192.0.80.241, 192.0.80.242
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: ns3.automattic.com, ns2.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: 5 ms
Got: 5 ms
A192.0.80.240, 192.0.80.239, 192.0.80.241, 192.0.80.242
AAAA
CNAME
NSns3.automattic.com, ns2.automattic.com, ns1.automattic.com
MX
10 mx1.dfw.automattic.com
10 mx2.ams.automattic.com
TXT
google-site-verification=EnpZ3Ws1zod-yJk1A56dmmybRJuaFJS5pC5ufe7fY08
SPF v=spf1 include:_spf.automattic.com include:mail.zendesk.com -all
google-site-verification=zcrh49pTocv2U39W4cjPWiyphok2YMYy6qGrqKCiU9k
vontbyjxrq
CAALookup not available with standard resolver
Resolved in 5 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://gravatar.com

https://gravatar.com

136 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://gravatar.com200136 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: 1022 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 does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 1022 B Sitemaps referenced 0 User-agents Amazonbot, GPTBot, CCBot, Google-Extended, FacebookBot, omgili, Bytespider, *, SentiBot, sentibot, omgilibot Blocking No — crawling allowed
User-Agent: *
Disallow: /*.json
Disallow: /*.xml
Disallow: /*.php
Disallow: /*.vcf
Disallow: /*.qr
Disallow: /*.card
Disallow: /accounts/activate/*
Disallow: /accounts/force-by-email/*
Disallow: /account/
Allow: /sitemap.xml
Allow: /sitemap-*.xml

# Do not allow indexing most API endpoints.
Disallow: /v1/
Disallow: /v2/
Disallow: /v3/
Allow: /v3/openapi

User-agent: GPTBot
Allow: /v3/openapi
Allow: /*.md
Disallow: /

User-agent: CCBot
Allow: /v3/openapi
Allow: /*.md
Disallow: /

User-agent: SentiBot
Allow: /v3/openapi
Allow: /*.md
Disallow: /

User-agent: sentibot
Allow: /v3/openapi
Allow: /*.md
Disallow: /

User-agent: Google-Extended
Allow: /v3/openapi
Allow: /*.md
Disallow: /

User-agent: FacebookBot
Allow: /v3/openapi
Allow: /*.md
Disallow: /

User-agent: omgili
Allow: /v3/openapi
Allow: /*.md
Disallow: /

User-agent: omgilibot
Allow: /v3/openapi
Allow: /*.md
Disallow: /

User-agent: Amazonbot
Allow: /v3/openapi
Allow: /*.md
Disallow: /

User-agent: Bytespider
Allow: /v3/openapi
Allow: /*.md
Disallow: /
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

302https://www.gravatar.com/
200https://gravatar.com/

Preferred variant: non-www

HTTP → HTTPS

301http://gravatar.com/ https://gravatar.com/

Consistent

A+
Domain Intelligence
gravatar.com — via MarkMonitor Inc., 22 years old, hosted on WordPress.com (Automattic)
PASS
gravatar.com — via MarkMonitor Inc., 22 years old, hosted on WordPress.com (Automattic)
Info::
Domain registered until Jul 15, 2027 (1 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

367 days

July 15, 2027

SSL certificate

84 days

Issued by Let's Encrypt

Domain age

22 years

Registered July 15, 2004

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

WordPress.com (Automattic)

ASN AS2635

192.0.80.241

Registrar

MarkMonitor Inc.

Unlocked 3 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 July 15, 2004 (22 years ago)
Expires July 15, 2027 (1 years, 3 months)
Last Updated June 13, 2025
Name Servers ns1.automattic.com, ns2.automattic.com, ns3.automattic.com
DNSSEC Not enabled
Hosting
IP Address 192.0.80.241
ASN AS2635 (AUTOMATTIC - Automattic, Inc, US)
Provider WordPress.com (Automattic)
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

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 189 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
3 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
43 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
45 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
136 ms
Total Time Total request time from DNS lookup through full response.
189 ms

Connection waterfall

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

Send Feedback