View on GitHub

DNSViz: A DNS visualization tool

icann.org

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

RRset statusRRset status

Secure (6)
  • icann.org/A
  • icann.org/AAAA
  • icann.org/MX
  • icann.org/NS
  • icann.org/SOA
  • icann.org/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (18)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46594)
  • icann.org/DNSKEY (alg 7, id 17199)
  • icann.org/DNSKEY (alg 7, id 18060)
  • icann.org/DNSKEY (alg 7, id 23584)
  • icann.org/DNSKEY (alg 7, id 43169)
  • icann.org/DNSKEY (alg 7, id 4629)
  • icann.org/DS (alg 7, id 17248)
  • icann.org/DS (alg 7, id 18060)
  • icann.org/DS (alg 7, id 18060)
  • icann.org/DS (alg 7, id 32134)
  • icann.org/DS (alg 7, id 41334)
  • icann.org/DS (alg 7, id 41643)
  • org/DNSKEY (alg 7, id 17883)
  • org/DNSKEY (alg 7, id 21869)
  • org/DNSKEY (alg 7, id 27353)
  • org/DS (alg 7, id 17883)
  • org/DS (alg 7, id 17883)
Non_existent (4)
  • icann.org/DNSKEY (alg 7, id 17248)
  • icann.org/DNSKEY (alg 7, id 32134)
  • icann.org/DNSKEY (alg 7, id 41334)
  • icann.org/DNSKEY (alg 7, id 41643)

Delegation statusDelegation status

Secure (2)
  • . to org
  • org to icann.org

NoticesNotices

Errors (16)
  • icann.org/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (2001:500:8e::53, UDP_-_EDNS0_4096_D_K)
  • icann.org/AAAA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.43.134.53, 2001:500:8e::53, UDP_-_EDNS0_4096_D_K)
  • icann.org/DNSKEY (alg 7, id 17199): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.43.134.53, UDP_-_EDNS0_4096_D_K)
  • icann.org/DNSKEY (alg 7, id 18060): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.43.134.53, UDP_-_EDNS0_4096_D_K)
  • icann.org/DNSKEY (alg 7, id 23584): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.43.134.53, UDP_-_EDNS0_4096_D_K)
  • icann.org/DNSKEY (alg 7, id 43169): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.43.134.53, UDP_-_EDNS0_4096_D_K)
  • icann.org/DNSKEY (alg 7, id 4629): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.43.134.53, UDP_-_EDNS0_4096_D_K)
  • icann.org/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.43.134.53, 2001:500:8e::53, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • icann.org/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.43.134.53, 2001:500:8e::53, UDP_-_EDNS0_4096_D_K)
  • icann.org/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.43.134.53, 2001:500:8e::53, TCP_-_EDNS0_4096_D, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
  • icann.org/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.43.134.53, 2001:500:8e::53, UDP_-_EDNS0_4096_D_K)
  • org to icann.org: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (199.43.134.53, UDP_-_EDNS0_4096_D_K)
  • org to icann.org: The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no DS RR matched a DNSKEY with algorithm 7 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (199.43.134.53, UDP_-_EDNS0_4096_D_K)
  • 76mlet19q5.icann.org/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • icann.org/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • icann.org/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (48)
  • RRSIG icann.org/A alg 7, id 17199: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG icann.org/AAAA alg 7, id 17199: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG icann.org/DNSKEY alg 7, id 18060: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG icann.org/DNSKEY alg 7, id 18060: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG icann.org/DNSKEY alg 7, id 18060: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG icann.org/DNSKEY alg 7, id 18060: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG icann.org/DNSKEY alg 7, id 18060: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG icann.org/DNSKEY alg 7, id 23584: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG icann.org/DNSKEY alg 7, id 23584: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG icann.org/DNSKEY alg 7, id 23584: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG icann.org/DNSKEY alg 7, id 23584: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG icann.org/DNSKEY alg 7, id 23584: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG icann.org/DS alg 7, id 27353: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG icann.org/DS alg 7, id 27353: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG icann.org/DS alg 7, id 27353: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG icann.org/DS alg 7, id 27353: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG icann.org/DS alg 7, id 27353: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG icann.org/DS alg 7, id 27353: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG icann.org/MX alg 7, id 17199: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG icann.org/NS alg 7, id 17199: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG icann.org/SOA alg 7, id 4629: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG icann.org/TXT alg 7, id 17199: 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 27353: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 27353: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 27353: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • icann.org/DS (alg 7, id 17248): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • icann.org/DS (alg 7, id 17248): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • icann.org/DS (alg 7, id 17248): 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.
  • icann.org/DS (alg 7, id 17248): 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.
  • icann.org/DS (alg 7, id 18060): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • icann.org/DS (alg 7, id 18060): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • icann.org/DS (alg 7, id 18060): 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.
  • icann.org/DS (alg 7, id 18060): 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.
  • icann.org/DS (alg 7, id 41643): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • icann.org/DS (alg 7, id 41643): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • icann.org/DS (alg 7, id 41643): 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.
  • icann.org/DS (alg 7, id 41643): 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 17883): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • org/DS (alg 7, id 17883): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • org/DS (alg 7, id 17883): 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 17883): 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.
  • 76mlet19q5.icann.org/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • icann.org/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • icann.org/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • icann.org/DS has warnings; select the "Denial of existence" DNSSEC option to see them.

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