View on GitHub

DNSViz: A DNS visualization tool

sourceware.org

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

RRset statusRRset status

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

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (12)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 48903)
  • org/DNSKEY (alg 7, id 17883)
  • org/DNSKEY (alg 7, id 27074)
  • org/DNSKEY (alg 7, id 37022)
  • org/DS (alg 7, id 17883)
  • org/DS (alg 7, id 17883)
  • org/DS (alg 7, id 9795)
  • sourceware.org/DNSKEY (alg 5, id 1828)
  • sourceware.org/DNSKEY (alg 5, id 96)
  • sourceware.org/DS (alg 5, id 1828)
  • sourceware.org/DS (alg 5, id 96)
Non_existent (1)
  • org/DNSKEY (alg 7, id 9795)

Delegation statusDelegation status

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

NoticesNotices

Errors (3)
  • sourceware.org zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (209.132.180.131)
  • sourceware.org/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (209.132.180.131, UDP_-_NOEDNS_)
  • sourceware.org/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (209.132.180.131, UDP_-_NOEDNS_)
Warnings (34)
  • 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 37022: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 37022: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 37022: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sourceware.org/A alg 5, id 96: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sourceware.org/AAAA alg 5, id 96: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sourceware.org/DNSKEY alg 5, id 1828: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sourceware.org/DNSKEY alg 5, id 1828: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sourceware.org/DNSKEY alg 5, id 96: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sourceware.org/DNSKEY alg 5, id 96: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sourceware.org/DS alg 7, id 37022: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sourceware.org/DS alg 7, id 37022: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sourceware.org/MX alg 5, id 96: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sourceware.org/NS alg 5, id 96: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sourceware.org/SOA alg 5, id 96: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sourceware.org/TXT alg 5, id 96: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • org to sourceware.org: Authoritative AAAA records exist for server2.sourceware.org, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • org to sourceware.org: Authoritative AAAA records exist for server3.sourceware.org, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • org to sourceware.org: Authoritative AAAA records exist for sourceware.org, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • org to sourceware.org: The glue address(es) for sourceware.org (209.132.180.131) differed from its authoritative address(es) (8.43.85.97). See RFC 1034, Sec. 4.2.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): 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.
  • 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.
  • vp95zl07jm.sourceware.org/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • sourceware.org/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • sourceware.org/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • sourceware.org/CNAME 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