letsencrypt.org
Updated:
2024-10-24 17:26:56 UTC (59 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (14)
- letsencrypt.org/A
- letsencrypt.org/A
- letsencrypt.org/A
- letsencrypt.org/A
- letsencrypt.org/A
- letsencrypt.org/AAAA
- letsencrypt.org/AAAA
- letsencrypt.org/AAAA
- letsencrypt.org/AAAA
- letsencrypt.org/AAAA
- letsencrypt.org/MX
- letsencrypt.org/NS
- letsencrypt.org/SOA
- letsencrypt.org/TXT
Secure (1)
- org/SOA
DNSKEY/DS/NSEC status
Secure (7)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 61050)
- NSEC3 proving non-existence of letsencrypt.org/DS
- org/DNSKEY (alg 8, id 15678)
- org/DNSKEY (alg 8, id 26974)
- org/DNSKEY (alg 8, id 42393)
- org/DS (alg 8, id 26974)
Delegation status
Insecure (1)
- org to letsencrypt.org
Secure (1)
- . to org
Notices
Warnings (7)
- ./DNSKEY (alg 8, id 20326): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
- ./DNSKEY (alg 8, id 61050): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
- NSEC3 proving non-existence of letsencrypt.org/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of letsencrypt.org/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- org/DS (alg 8, id 26974): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
- org/DS (alg 8, id 26974): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
- letsencrypt.org/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
