View on GitHub

DNSViz: A DNS visualization tool

ocsp.int-x3.letsencrypt.org

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

RRset statusRRset status

Insecure (7)
  • a771.dscq.akamai.net/A
  • a771.dscq.akamai.net/AAAA
  • a771.dscq.akamai.net/AAAA
  • a771.dscq.akamai.net/AAAA
  • akamai.net/SOA
  • ocsp.int-x3.letsencrypt.org.edgesuite.net/CNAME
  • ocsp.int-x3.letsencrypt.org/CNAME
Secure (5)
  • net/SOA
  • net/SOA
  • net/SOA
  • net/SOA
  • org/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (12)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26116)
  • NSEC3 proving non-existence of akamai.net/DS
  • NSEC3 proving non-existence of edgesuite.net/DS
  • NSEC3 proving non-existence of letsencrypt.org/DS
  • net/DNSKEY (alg 8, id 15314)
  • net/DNSKEY (alg 8, id 35886)
  • net/DS (alg 8, id 35886)
  • org/DNSKEY (alg 8, id 26974)
  • org/DNSKEY (alg 8, id 34266)
  • org/DNSKEY (alg 8, id 63858)
  • org/DS (alg 8, id 26974)

Delegation statusDelegation status

Insecure (4)
  • akamai.net to dscq.akamai.net
  • net to akamai.net
  • net to edgesuite.net
  • org to letsencrypt.org
Secure (2)
  • . to net
  • . to org

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 (8)
  • 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.
  • net to akamai.net: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the net zone): a12-193.akamaitech.net, a5-193.akamaitech.net, zb.akamaitech.net, a6-193.akamaitech.net, a22-193.akamaitech.net, a1-193.akamaitech.net, a3-193.akamaitech.net See RFC 1034, Sec. 4.2.2.
  • net to akamai.net: The following NS name(s) were found in the delegation NS RRset (i.e., in the net zone), but not in the authoritative NS RRset: ns1-1.akamaitech.net, ns6-193.akamaitech.net, ns7-193.akamaitech.net, ze.akamaitech.net, zg.akamaitech.net, zh.akamaitech.net, zi.akamaitech.net See RFC 1034, Sec. 4.2.2.
  • net to edgesuite.net: Authoritative AAAA records exist for a13-64.akam.net, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • net to edgesuite.net: Authoritative AAAA records exist for a5-64.akam.net, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • net to edgesuite.net: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the net zone): a11-64.akam.net, a3-64.akam.net, a9-64.akam.net See RFC 1034, Sec. 4.2.2.
  • net to edgesuite.net: The following NS name(s) were found in the delegation NS RRset (i.e., in the net zone), but not in the authoritative NS RRset: ns4-65.akam.net, ns5-65.akam.net, ns7-65.akam.net See RFC 1034, Sec. 4.2.2.

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