View on GitHub

DNSViz: A DNS visualization tool

govmu.org

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

RRset statusRRset status

Secure (5)
  • govmu.org/A
  • govmu.org/MX
  • govmu.org/NS
  • govmu.org/SOA
  • govmu.org/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (13)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46594)
  • govmu.org/DNSKEY (alg 8, id 231)
  • govmu.org/DNSKEY (alg 8, id 39870)
  • govmu.org/DNSKEY (alg 8, id 46771)
  • govmu.org/DNSKEY (alg 8, id 65062)
  • govmu.org/DS (alg 8, id 46771)
  • govmu.org/DS (alg 8, id 65062)
  • 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)

Delegation statusDelegation status

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

NoticesNotices

Errors (1)
  • ./DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2001:500:12::d0d, UDP_-_EDNS0_512_D_K)
Warnings (15)
  • ./DNSKEY (alg 8, id 20326): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2001:500:12::d0d, UDP_-_EDNS0_4096_D_K)
  • ./DNSKEY (alg 8, id 46594): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2001:500:12::d0d, UDP_-_EDNS0_4096_D_K)
  • RRSIG govmu.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 govmu.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 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.
  • 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.
  • govmu.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