Skip to content
https://ssllabs.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Madrid, Spain
302 Found
Checks
9
4 PASS 4 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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 115 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

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 115 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /ssltest/analyze.html
Disallow: /ssltest/analyze
Disallow: /analyze.html
Disallow: /analyze
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.ssllabs.com/
200https://ssllabs.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://ssllabs.com/ https://ssllabs.com/

Consistent

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

Certificate validity

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

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
1 A records, 31 ms lookup
PASS
1 A records, 31 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 69.67.183.100
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: seth.ns.cloudflare.com, tara.ns.cloudflare.com
Info::
4 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: 31 ms
Got: 31 ms
A69.67.183.100
AAAA
CNAME
NSseth.ns.cloudflare.com, tara.ns.cloudflare.com
MX
1 ssllabs.com.s10a2.psmtp.com
1 ssllabs.com.s10a1.psmtp.com
1 ssllabs.com.s10b1.psmtp.com
1 ssllabs.com.s10b2.psmtp.com
TXT
SPF v=spf1 ip4:64.39.100.69 ~all
_mmd9d3p6bo8e76kei2cv6jfzqeumy0e
z5yzn3x4ypg6n3f02xpwkmrzdvs2m4wn
_zy72o3bsexdkxz5bd572sr9byy64sjx
CAALookup not available with standard resolver
Resolved in 31 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

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
1 redirect(s), 923 ms total
PASS
1 redirect(s), 923 ms total
Info::
Single redirect
Got: https://ssllabs.com → https://www.ssllabs.com/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://ssllabs.com
Info::
Redirect overhead: 923 ms total
Got: 923 ms

https://ssllabs.com

443 ms · HTTP/1.1

302

https://www.ssllabs.com/

480 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ssllabs.com302443 msHTTP/1.1Apache
2https://www.ssllabs.com/200480 msHTTP/1.1Apache

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

A+
Domain Intelligence
ssllabs.com — via MarkMonitor Inc., 17 years, 6 months old, hosted on QUALYS - QUALYS, Inc., US
PASS
ssllabs.com — via MarkMonitor Inc., 17 years, 6 months old, hosted on QUALYS - QUALYS, Inc., US
Info::
Domain registered until Jan 1, 2028 (1 years, 8 months remaining)
Info::
DNSSEC is enabled
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: QUALYS - QUALYS, Inc., US
Got: AS27385
Domain expiry

532 days

January 1, 2028

SSL certificate

94 days

Issued by DigiCert Inc

Domain age

17 years, 6 months

Registered January 1, 2009

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

QUALYS - QUALYS, Inc., US

ASN AS27385

69.67.183.100

Registrar

MarkMonitor Inc.

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar MarkMonitor Inc.
Created January 1, 2009 (17 years, 6 months ago)
Expires January 1, 2028 (1 years, 8 months)
Last Updated December 1, 2025
Name Servers seth.ns.cloudflare.com, tara.ns.cloudflare.com
DNSSEC Enabled
Hosting
IP Address 69.67.183.100
ASN AS27385 (QUALYS - QUALYS, Inc., US)
Provider QUALYS - QUALYS, Inc., US
Data source: rdap (0.5s)

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

Connection waterfall

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

Send Feedback