View on GitHub

DNSViz: A DNS visualization tool

ocsp.int-x3.letsencrypt.org

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

RRset statusRRset status

Insecure (13)
  • a771.dscq.akamai.net.0.1.cn.akamaitech.net/A
  • a771.dscq.akamai.net.0.1.cn.akamaitech.net/A
  • a771.dscq.akamai.net.0.1.cn.akamaitech.net/AAAA
  • a771.dscq.akamai.net.0.1.cn.akamaitech.net/AAAA
  • a771.dscq.akamai.net/A
  • a771.dscq.akamai.net/A
  • a771.dscq.akamai.net/AAAA
  • a771.dscq.akamai.net/AAAA
  • a771.dscq.akamai.net/CNAME
  • akamai.net/SOA
  • akamaitech.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 (15)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 33853)
  • NSEC3 proving non-existence of akamai.net/DS
  • NSEC3 proving non-existence of akamaitech.net/DS
  • NSEC3 proving non-existence of edgesuite.net/DS
  • NSEC3 proving non-existence of letsencrypt.org/DS
  • net/DNSKEY (alg 8, id 24512)
  • net/DNSKEY (alg 8, id 35886)
  • net/DS (alg 8, id 35886)
  • org/DNSKEY (alg 7, id 17883)
  • org/DNSKEY (alg 7, id 33209)
  • org/DNSKEY (alg 7, id 37022)
  • org/DNSKEY (alg 7, id 9795)
  • org/DS (alg 7, id 9795)
  • org/DS (alg 7, id 9795)

Delegation statusDelegation status

Insecure (6)
  • akamai.net to dscq.akamai.net
  • akamaitech.net to cn.akamaitech.net
  • net to akamai.net
  • net to akamaitech.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 (45)
  • 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.
  • RRSIG NSEC3 proving non-existence of letsencrypt.org/DS alg 7, id 33209: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG NSEC3 proving non-existence of letsencrypt.org/DS alg 7, id 33209: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 17883: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 17883: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 17883: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 17883: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 33209: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 33209: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 33209: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 33209: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 9795: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 9795: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 9795: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 9795: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/SOA alg 7, id 33209: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • a771.dscq.akamai.net/CNAME: The server returned CNAME for a771.dscq.akamai.net, but records of other types exist at that name. See RFC 2181, Sec. 10.1.
  • akamai.net to dscq.akamai.net: The glue address(es) for n1dscq.akamai.net (23.218.80.29, 104.114.77.13) differed from its authoritative address(es) (23.218.80.29). See RFC 1034, Sec. 4.2.2.
  • akamai.net to dscq.akamai.net: The glue address(es) for n2dscq.akamai.net (23.213.184.17, 23.218.80.228) differed from its authoritative address(es) (23.218.80.228). See RFC 1034, Sec. 4.2.2.
  • akamai.net to dscq.akamai.net: The glue address(es) for n3dscq.akamai.net (23.40.65.30, 23.218.80.30) differed from its authoritative address(es) (23.218.80.30). See RFC 1034, Sec. 4.2.2.
  • akamai.net to dscq.akamai.net: The glue address(es) for n4dscq.akamai.net (23.32.15.201, 23.40.65.39) differed from its authoritative address(es) (23.32.15.201). See RFC 1034, Sec. 4.2.2.
  • akamai.net to dscq.akamai.net: The glue address(es) for n5dscq.akamai.net (23.40.65.37, 204.2.136.63) differed from its authoritative address(es) (204.2.136.63). See RFC 1034, Sec. 4.2.2.
  • akamai.net to dscq.akamai.net: The glue address(es) for n6dscq.akamai.net (23.40.65.31, 23.218.80.14) differed from its authoritative address(es) (23.218.80.14). See RFC 1034, Sec. 4.2.2.
  • akamai.net to dscq.akamai.net: The glue address(es) for n7dscq.akamai.net (23.213.184.22, 23.218.80.39) differed from its authoritative address(es) (23.218.80.39). See RFC 1034, Sec. 4.2.2.
  • akamaitech.net to cn.akamaitech.net: The glue address(es) for n1cn.akamaitech.net (184.51.100.5, 184.51.100.14) differed from its authoritative address(es) (184.51.100.14). See RFC 1034, Sec. 4.2.2.
  • akamaitech.net to cn.akamaitech.net: The glue address(es) for n1cn.akamaitech.net (2600:1407:4:f000:81a:dc72:9ccd:dcf8, 2600:1407:4:f000:81d::) differed from its authoritative address(es) (2600:1407:4:f000:81a:dc72:9ccd:dcf8). See RFC 1034, Sec. 4.2.2.
  • akamaitech.net to cn.akamaitech.net: The glue address(es) for n2cn.akamaitech.net (184.51.100.12, 184.51.100.13) differed from its authoritative address(es) (184.51.100.13). See RFC 1034, Sec. 4.2.2.
  • akamaitech.net to cn.akamaitech.net: The glue address(es) for n3cn.akamaitech.net (184.51.100.5, 184.51.100.14) differed from its authoritative address(es) (184.51.100.5). See RFC 1034, Sec. 4.2.2.
  • akamaitech.net to cn.akamaitech.net: The glue address(es) for n4cn.akamaitech.net (184.51.100.4, 184.51.100.7) differed from its authoritative address(es) (184.51.100.7). See RFC 1034, Sec. 4.2.2.
  • akamaitech.net to cn.akamaitech.net: The glue address(es) for n5cn.akamaitech.net (63.141.195.108, 184.51.100.6) differed from its authoritative address(es) (184.51.100.6). See RFC 1034, Sec. 4.2.2.
  • akamaitech.net to cn.akamaitech.net: The glue address(es) for n6cn.akamaitech.net (23.62.236.140, 184.51.100.6) differed from its authoritative address(es) (23.62.236.140). See RFC 1034, Sec. 4.2.2.
  • akamaitech.net to cn.akamaitech.net: The glue address(es) for n7cn.akamaitech.net (184.84.242.53, 216.156.225.138) differed from its authoritative address(es) (184.84.242.53). See RFC 1034, Sec. 4.2.2.
  • 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 akamaitech.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): zb.akamaitech.net See RFC 1034, Sec. 4.2.2.
  • net to akamaitech.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: 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.
  • org/DS (alg 7, id 9795): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • org/DS (alg 7, id 9795): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • org/DS (alg 7, id 9795): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • org/DS (alg 7, id 9795): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.

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