View on GitHub

DNSViz: A DNS visualization tool

acme-v02.api.letsencrypt.org

DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Insecure (2)
  • acme-v02.api.letsencrypt.org/CNAME
  • prod.api.letsencrypt.org/CNAME
Secure (3)
  • ca80a1adb12a4fbdac5ffcbc944e9a61.pacloudflare.com/A
  • ca80a1adb12a4fbdac5ffcbc944e9a61.pacloudflare.com/AAAA
  • org/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (13)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26838)
  • NSEC3 proving non-existence of letsencrypt.org/DS
  • com/DNSKEY (alg 8, id 30909)
  • com/DNSKEY (alg 8, id 39343)
  • com/DS (alg 8, id 30909)
  • org/DNSKEY (alg 8, id 26974)
  • org/DNSKEY (alg 8, id 39681)
  • org/DNSKEY (alg 8, id 63813)
  • org/DS (alg 8, id 26974)
  • pacloudflare.com/DNSKEY (alg 13, id 2371)
  • pacloudflare.com/DNSKEY (alg 13, id 34505)
  • pacloudflare.com/DS (alg 13, id 2371)

Delegation statusDelegation status

Insecure (1)
  • org to letsencrypt.org
Secure (3)
  • . to com
  • . to org
  • com to pacloudflare.com

NoticesNotices

Errors (2)
  • NSEC3 proving non-existence of letsencrypt.org/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of letsencrypt.org/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
Warnings (2)
  • 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.

DNSKEY legend

Full legend
SEP bit setSEP bit set
Revoke bit setRevoke bit set
Trust anchorTrust anchor
Download: png | svg
Warning JavaScript is required to make the graph below interactive.
DNSSEC authentication graph