View on GitHub

DNSViz: A DNS visualization tool

0.7.4.0.1.0.0.2.ip6.arpa

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

RRset statusRRset status

Insecure (2)
  • 0.7.4.0.1.0.0.2.ip6.arpa/NS
  • 0.7.4.0.1.0.0.2.ip6.arpa/SOA
Secure (1)
  • 4.0.1.0.0.2.ip6.arpa/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (18)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 48903)
  • 4.0.1.0.0.2.ip6.arpa/DNSKEY (alg 5, id 4940)
  • 4.0.1.0.0.2.ip6.arpa/DNSKEY (alg 5, id 58008)
  • 4.0.1.0.0.2.ip6.arpa/DNSKEY (alg 5, id 64824)
  • 4.0.1.0.0.2.ip6.arpa/DS (alg 5, id 64824)
  • NSEC proving non-existence of 0.7.4.0.1.0.0.2.ip6.arpa/DS
  • arpa/DNSKEY (alg 8, id 21985)
  • arpa/DNSKEY (alg 8, id 42581)
  • arpa/DS (alg 8, id 42581)
  • arpa/DS (alg 8, id 42581)
  • ip6.arpa/DNSKEY (alg 8, id 21619)
  • ip6.arpa/DNSKEY (alg 8, id 64060)
  • ip6.arpa/DNSKEY (alg 8, id 64576)
  • ip6.arpa/DNSKEY (alg 8, id 6486)
  • ip6.arpa/DS (alg 8, id 13880)
  • ip6.arpa/DS (alg 8, id 45094)
  • ip6.arpa/DS (alg 8, id 64060)
Non_existent (2)
  • ip6.arpa/DNSKEY (alg 8, id 13880)
  • ip6.arpa/DNSKEY (alg 8, id 45094)

Delegation statusDelegation status

Insecure (1)
  • 4.0.1.0.0.2.ip6.arpa to 0.7.4.0.1.0.0.2.ip6.arpa
Secure (3)
  • . to arpa
  • arpa to ip6.arpa
  • ip6.arpa to 4.0.1.0.0.2.ip6.arpa

NoticesNotices

Errors (1)
  • arpa zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:500:2::c)
Warnings (21)
  • 4.0.1.0.0.2.ip6.arpa/DS (alg 5, id 64824): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • 4.0.1.0.0.2.ip6.arpa/DS (alg 5, id 64824): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • RRSIG 4.0.1.0.0.2.ip6.arpa/DNSKEY alg 5, id 58008: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG 4.0.1.0.0.2.ip6.arpa/DNSKEY alg 5, id 58008: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG 4.0.1.0.0.2.ip6.arpa/DNSKEY alg 5, id 58008: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG 4.0.1.0.0.2.ip6.arpa/DNSKEY alg 5, id 64824: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG 4.0.1.0.0.2.ip6.arpa/DNSKEY alg 5, id 64824: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG 4.0.1.0.0.2.ip6.arpa/DNSKEY alg 5, id 64824: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG 4.0.1.0.0.2.ip6.arpa/SOA alg 5, id 58008: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG NSEC proving non-existence of 0.7.4.0.1.0.0.2.ip6.arpa/DS alg 5, id 58008: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • arpa/DS (alg 8, id 42581): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • arpa/DS (alg 8, id 42581): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • arpa/DS (alg 8, id 42581): 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.
  • arpa/DS (alg 8, id 42581): 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.
  • ip6.arpa/DS (alg 8, id 13880): 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. (192.112.36.4, UDP_-_EDNS0_4096_D_K)
  • ip6.arpa/DS (alg 8, id 13880): 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. (192.112.36.4, UDP_-_EDNS0_4096_D_K)
  • ip6.arpa/DS (alg 8, id 45094): 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. (192.112.36.4, UDP_-_EDNS0_4096_D_K)
  • ip6.arpa/DS (alg 8, id 45094): 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. (192.112.36.4, UDP_-_EDNS0_4096_D_K)
  • ip6.arpa/DS (alg 8, id 64060): 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. (192.112.36.4, UDP_-_EDNS0_4096_D_K)
  • ip6.arpa/DS (alg 8, id 64060): 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. (192.112.36.4, UDP_-_EDNS0_4096_D_K)
  • 0.7.4.0.1.0.0.2.ip6.arpa/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