Skip to content
https://letsencrypt.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
99
GRADE
A+
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from New York, United Stated
200 OK
Checks
9
7 PASS 2 REVIEW
B
TLS Certificate Expiry & Recommendations
62 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

62
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
B
CDN & Delivery
Netlify
REVIEW
Netlify
Info::
Site is served via Netlify CDN
Got: x-nf-request-id: 01KNCVS90DMKG6PQKT67CYQZ8D
CDN Detected: Netlify
Provider Netlify Evidence x-nf-request-id: 01KNCVS90DMKG6PQKT67CYQZ8D
A+
DNS Records
2 A records, 76 ms lookup
PASS
2 A records, 76 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 18.208.88.157, 98.84.224.111
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2600:1f18:16e:df01::258, 2600:1f18:16e:df01::259
Info::
2 nameserver(s) configured
Got: vera.ns.cloudflare.com, owen.ns.cloudflare.com
Info::
5 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: 76 ms
Got: 76 ms
A18.208.88.157, 98.84.224.111
AAAA2600:1f18:16e:df01::258, 2600:1f18:16e:df01::259
CNAME—
NSvera.ns.cloudflare.com, owen.ns.cloudflare.com
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 aspmx3.googlemail.com
10 aspmx2.googlemail.com
TXT
pardot1011011=d160caff32c4415bb46bb82d8c50e5bea7ea1a74f5a149cb96bd952467266044
SPF v=spf1 include:_spf.google.com ip4:23.178.112.0/24 ip4:66.133.109.36 ip4:64.78.1...
sending_domain1011011=f98c68e7636a708a1987c7b9da300d64a354041fa41ea2039fbb02bc18...
CAALookup not available with standard resolver
Resolved in 76 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://letsencrypt.org

https://letsencrypt.org

91 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://letsencrypt.org20091 msHTTP/1.1Netlify
A+
IPv6 Readiness
IPv6 reachable (7 ms)
PASS
IPv6 reachable (7 ms)
Info::
IPv6 is configured and reachable at 2600:1f18:16e:df01::258, 2600:1f18:16e:df01::259
Got: 7 ms connect
IPv6 Ready
AAAA Records 2600:1f18:16e:df01::258, 2600:1f18:16e:df01::259 Connection Reachable (7 ms)
A+
Crawlability
robots.txt present, sitemap with 28 URLs
PASS
robots.txt present, sitemap with 28 URLs
Info::
robots.txt is present
Got: 14 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 28 entries
Info::
Sitemap index with 28 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 14 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
sitemap.xml 200 OK
Type Sitemap Index URLs 28 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::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.letsencrypt.org/
200https://letsencrypt.org/

Preferred variant: non-www

HTTP → HTTPS

301http://letsencrypt.org/ → https://letsencrypt.org/

Consistent

A+
Domain Intelligence
letsencrypt.org — via Cloudflare, Inc., 11 years, 10 months old
PASS
letsencrypt.org — via Cloudflare, Inc., 11 years, 10 months old
Info::
Domain registered until Jul 7, 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: Cloudflare, Inc.
Domain expiry

387 days

July 7, 2027

SSL certificate

62 days

Issued by Let's Encrypt

Domain age

11 years, 10 months

Registered July 7, 2014

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2600:1f18:16e:df01::259

Registrar

Cloudflare, Inc.

Lock status unknown 2 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 Cloudflare, Inc.
Created July 7, 2014 (11 years, 10 months ago)
Expires July 7, 2027 (1 years, 3 months)
Last Updated November 3, 2020
Name Servers owen.ns.cloudflare.com, vera.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2600:1f18:16e:df01::259
Data source: rdap (0.4s)

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

Connection waterfall

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

Send Feedback