View on GitHub

DNSViz: A DNS visualization tool

shell.com

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

RRset statusRRset status

Secure (6)
  • shell.com/A
  • shell.com/MX
  • shell.com/NS
  • shell.com/NSEC3PARAM
  • shell.com/SOA
  • shell.com/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (11)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 951)
  • com/DNSKEY (alg 8, id 30909)
  • com/DNSKEY (alg 8, id 36739)
  • com/DS (alg 8, id 30909)
  • shell.com/DNSKEY (alg 8, id 21682)
  • shell.com/DNSKEY (alg 8, id 60561)
  • shell.com/DNSKEY (alg 8, id 7740)
  • shell.com/DS (alg 8, id 21682)
  • shell.com/DS (alg 8, id 21682)
  • shell.com/DS (alg 8, id 979)
Non_existent (1)
  • shell.com/DNSKEY (alg 8, id 979)

Delegation statusDelegation status

Secure (2)
  • . to com
  • com to shell.com

NoticesNotices

Errors (3)
  • shell.com zone: The server(s) were not responsive to queries over UDP. (34.250.153.89, 134.146.80.20)
  • shell.com/A: No response was received from the server over UDP (tried 12 times). (34.250.153.89, 134.146.80.20, UDP_-_NOEDNS_)
  • shell.com/NS: No response was received from the server over UDP (tried 12 times). (34.250.153.89, 134.146.80.20, UDP_-_NOEDNS_)
Warnings (11)
  • ./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. (192.112.36.4, UDP_-_EDNS0_4096_D_KN)
  • ./DNSKEY (alg 8, id 951): 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. (192.112.36.4, UDP_-_EDNS0_4096_D_KN)
  • com to shell.com: The following NS name(s) were found in the delegation NS RRset (i.e., in the com zone), but not in the authoritative NS RRset: dns4.shell.eu
  • shell.com/DS (alg 8, id 21682): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
  • shell.com/DS (alg 8, id 21682): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
  • shell.com/DS (alg 8, id 21682): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset.
  • shell.com/DS (alg 8, id 21682): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset.
  • shell.com/DS (alg 8, id 979): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
  • shell.com/DS (alg 8, id 979): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
  • shell.com/DS (alg 8, id 979): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset.
  • shell.com/DS (alg 8, id 979): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset.

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