View on GitHub

DNSViz: A DNS visualization tool

shell.com

DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
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 (12)
  • ./DNSKEY (alg 8, id 18733)
  • ./DNSKEY (alg 8, id 20326)
  • com/DNSKEY (alg 8, id 30909)
  • com/DNSKEY (alg 8, id 53929)
  • com/DS (alg 8, id 30909)
  • shell.com/DNSKEY (alg 8, id 21682)
  • shell.com/DNSKEY (alg 8, id 42765)
  • shell.com/DNSKEY (alg 8, id 6129)
  • 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 (6)
  • shell.com zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (34.250.153.89)
  • shell.com/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (34.250.153.89, UDP_-_NOEDNS_)
  • shell.com/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (34.250.153.89, UDP_-_NOEDNS_)
  • shell.com/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • bpnazk98ej.shell.com/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • shell.com/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (12)
  • 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 See RFC 1034, Sec. 4.2.2.
  • shell.com/DS (alg 8, id 21682): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • shell.com/DS (alg 8, id 21682): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • 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. See RFC 4509, Sec. 3.
  • 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. See RFC 4509, Sec. 3.
  • shell.com/DS (alg 8, id 979): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • shell.com/DS (alg 8, id 979): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • 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. See RFC 4509, Sec. 3.
  • 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. See RFC 4509, Sec. 3.
  • shell.com/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • bpnazk98ej.shell.com/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • shell.com/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