Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.FIPv6 ReadinessActionIPv6 records exist but unreachableFIX
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.
Learn more ▾ ▴
Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.
Source: RFC 8305 (Happy Eyeballs)
BRedirect Chain2 redirect(s), 133 ms totalREVIEW
https://lencr.org
22 ms · HTTP/1.1
https://letsencrypt.org/docs/lencr.org
90 ms · HTTP/1.1
https://letsencrypt.org/docs/lencr.org/
20 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://lencr.org | 302 | 22 ms | HTTP/1.1 | Netlify |
| 2 | https://letsencrypt.org/docs/lencr.org | 301 | 90 ms | HTTP/1.1 | Netlify |
| 3 | https://letsencrypt.org/docs/lencr.org/ | 200 | 20 ms | HTTP/1.1 | Netlify |
See the visual redirect chain in the HTTP Probe tab →
Each redirect adds latency. Try to minimize the chain to 1 hop.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
If permanent, use 301 instead.
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
CCrawlabilityActionrobots.txt present, sitemap with 0 URLsREVIEW
Search engines may not be able to parse the sitemap. Fix XML validation errors.
An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.
Learn more ▾ ▴
Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.
Source: sitemaps.org / Google Search Central
An empty sitemap provides no value. Add <url> entries for your pages.
An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.
Learn more ▾ ▴
Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.
Source: Google Search Central / sitemaps.org
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
<!DOCTYPE html>
<html lang="en-US" dir="ltr">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
<title>
lencr.org - Let's Encrypt
</title>
<meta name="description" content="What’s lencr.org? lencr.org is a domain name owned by Let’s Encrypt. We use it to host data that is referenced inside the certificates we issue.
Why is my computer fetching this data? Is it malicious? No, the data on lencr.org is never malicious. When a device connects to lencr.org, it’s because client software on that device (like a web browser or an app) connected to another site, saw a Let’s Encrypt certificate, and is trying to verify that it’s valid. This is routine for many clients.
" />
<meta property="og:image" content="https://letsencrypt.org/images/LetsEncrypt-SocialShare.png">
<meta property="og:type" content="website" />
<meta property="og:title" content="lencr.org" />
<meta property="og:description" content="What’s lencr.org? lencr.org is a domain name owned by Let’s Encrypt. We use it to host data that is referenced inside the certificates we issue.
Why is my computer fetching this data? Is it malicious? No, the data on lencr.org is never malicious. When a device connects to lencr.org, it’s because client software on that device (like a web browser or an app) connected to another site, saw a Let’s Encrypt certificate, and is trying to verify that it’s valid. This is routine for many clients.
" />
<meta property="og:url" content="https://letsencrypt.org/docs/lencr.org/" />
<link rel="alternate" type="application/rss+xml" title="Let's Encrypt" href="/feed.xml">
<link rel="stylesheet" href="/css/le-2025-theme-input.32491b9db8ee7d6a9d8e7521b8535a1d1eacab9458d976e4c0d8dcc3ae0552a8.css" integrity="sha256-MkkbnbjufWqdjnUhuFNaHR6sq5RY2XbkwNjcw64FUqg=" crossorigin="anonymous">
<link rel="stylesheet" href="/fontawesome-free-6.5.2-web/css/all.min.css" />
<script src="/js/le-2025-theme.baca0a37d412391799a4e5f6d58968c12b948b4c91c053a3c025ab758ffb70bc.js" integrity="sha256-usoKN9QSOReZpOX21YlowSuUi0yRwFOjwCWrdY/7cLw=" crossorigin="anonymous"></script>
<script src="/js/autoanchor.44783525c73cfeef565e5b8441cd42a848cb630d9f365def73edce4867e6f4c8.js" integrity="sha256-RHg1Jcc8/u9WXluEQc1CqEjLYw2fNl3vc+3OSGfm9Mg=" crossorigin="anonymous"></script>
<script src="/js/number-animation.137c25102252dc89411a5c2d9eb00a383f12425cb7845c8d8ac4c615c0af1f8e.js" integrity="sha256-E3wlECJS3IlBGlwtnrAKOD8SQly3hFyNisTGFcCvH44=" crossorigin="anonymous"></script>
</head>
<body>
<header class="relative bg-white shadow-sm">
<div class="language-section">
<div class="language-bar bg-gray-100 border-b border-gray-200">
<div class="container mx-auto px-4">
<div class="flex justify-end">
<button
id="language-toggle"
aria-expanded="false"
aria-controls="language-section"
class="flex items-center space-x-2 py-1 text-xs text-gray-600 hover:text-gray-900 focus:outline-none focus:ring-2 focus:ring-blue-500">
<span class="text-xs">Languages</span>
<img src="/images/language-icon128px-black.png" class="w-3 h-3" alt="" aria-hidden="true">
</button>
</div>
</div>
</div>
<div id="language-section"
class="hidden h-0 opacity-0 border-b border-gray-200 bg-white"
role="region"
aria-labelledby="language-toggle">
<div class="container mx-auto px-4 py-4">
<div class="grid grid-cols-2 md:grid-cols-3 lg:grid-cols-4 gap-1">
<a href="/docs/lencr.org/"
lang=""
hreflang=""
aria-current="true"
class="flex items-start lg:items-center space-x-2 px-4 py-2 rounded-md bg-blue-50 text-blue-700">
<svg class="w-5 h-5 text-blue-500" fill="none" stroke="currentColor" viewBox="0 0 24 24">
<path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M5 13l4 4L19 7"></path>
</svg>
<span>English</span>
</a>
<a href="/ca/docs/lencr.org/"
lang=""
hreflang=""
class="flex items-start lg:items-center space-x-2 px-4 py-2 rounded-md text-gray-700 hover:bg-gray-50">
<span>Català</span>
</a>
<a href="/cs/docs/lencr.org/"
lang=""
hreflang=""
class="flex items-start lg:items-center space-x-2 px-4 py-2 rounded-md text-gray-700 hover:bg-gray-50">
<span>Čeština</span>
</a>
<a href="/da/docs/lencr.org/"
lang=""
hreflang=""
class="flex items-start lg:items-center space-x-2 px-4 py-2 rounded-md text-gray-700 hover:bg-gray-50">
<span>Dansk</span>
</a>
<a href="/de/docs/lencr.org/"
lang=""
hreflang=""
class="flex items-start lg:items-center space-x-2 px-4 py-2 rounded-md text-gray-700 hover:bg-gray-50">
<span>Deutsch</span>
</a>
<a href="/el/docs/lencr.org/"
lang=""
hreflang=""
class="flex items-start lg:items-center space-x-2 px-4 py-2 rounded-md text-gray-700 hover:bg-gray-50">
<span>Greek</span>
</a>
<a href="/es/docs/lencr.org/"
lang=""
hreflang=""
class="flex items-start lg:items-center space-x-2 px-4 py-2 rounded-md text-gray-700 hover:bg-gray-50">
<span>Español</span>
</a>
<a href="/fi/docs/lencr.org/"
lang=""
hreflang=""
class="flex items-start lg:items-center space-x-2 px-4 py-2 rounded-md text-gray-700 hover:bg-gray-50">
<span>Suomi</span>
</a>
<a href="/fr/docs/lencr.org/"
lang=""
hreflang=""
class="flex items-start lg:items-center space-x-2 px-4 py-2 rounded-md text-gray-700 hover:bg-gray-50">
<span>Français</span>
</a>
<a href="/he/docs/lencr.org/"
lang=""
hreflang=""
class="flex items-start lg:items-center space-x-2 px-4 py-2 rounded-md text-gray-700 hover:bg-gray-50">
<span>עברית</span>
</a>
<a href="/hu/docs/lencr.org/"
lang=""
hreflang=""
class="flex items-start lg:items-center space-x-2 px-4 py-2 rounded-md text-gray-700 hover:bg-gray-50">
<span>Magyar</span>
</a>
<a href="/id/docs/lencr.org/"
lang=""
hreflang=""
class="flex items-start lg:items-center space-x-2 px-4 py-2 rounded-md text-gray-700 hover:bg-gray-50">
<span>Bahasa Indonesia</span>
</a>
<a href="/it/docs/lencr.org/"
lang=""
hreflang=""
class="flex items-start lg:items-center space-x-2 px-4 py-2 rounded-md text-gray-700 hover:bg-gray-50">
<span>Italiano</span>
</a>
<a href="/ja/docs/lencr.org/"
lang=""
hreflang=""
class="flex items-start lg:items-center space-x-2 px-4 py-2 rounded-md text-gray-700 hover:bg-gray-50">
<span>日本語</span>
</a>
<a href="/ko/docs/lencr.org/"
lang=""
hreflang=""
class="flex items-start lg:items-center space-x-2 px-4 py-2 rounded-md text-gray-700 hover:bg-gray-50">
<span>한국어</span>
</a>
<a href="/pl/docs/lencr.org/"
lang=""
hreflang=""
class="flex items-start lg:items-center space-x-2 px-4 py-2 rounded-md text-gray-700 hover:bg-gray-50">
<span>Polish</span>
</a>
<a href="/pt-br/docs/lencr.org/"
lang=""
hreflang=""
class="flex items-start lg:items-center space-x-2 px-4 py-2 rounded-md text-gray-700 hover:bg-gray-50">
<span>Português do Brasil</span>
</a>
<a href="/ru/docs/lencr.org/"
lang=""
hreflang=""
class="flex items-start lg:items-center space-x-2 px-4 py-2 rounded-md text-gray-700 hover:bg-gray-50">
<span>Русский</span>
</a>
<a href="/si/docs/lencr.org/"
lang=""
hreflang=""
class="flex items-start lg:ite
BTLS Certificate Expiry & Recommendations50 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
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
BCDN & DeliveryNetlifyREVIEW
A+DNS Records2 A records, 7 ms lookupPASS
| A | 13.52.188.95, 52.52.192.191 |
| AAAA | 2600:1f1c:446:4900::259, 2600:1f1c:446:4900::258 |
| CNAME | — |
| NS | owen.ns.cloudflare.com, vera.ns.cloudflare.com |
| MX | 0 |
| TXT | SPF v=spf1 -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.
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencelencr.org — via Cloudflare, Inc., 5 years, 10 months old, hosted on AWSPASS
379 days
June 29, 2027
50 days
Issued by Let's Encrypt
5 years, 10 months
Registered June 29, 2020
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
13.52.188.95
Cloudflare, 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