View on GitHub

DNSViz: A DNS visualization tool

ss

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

RRset statusRRset status

Secure (3)
  • ss/NS
  • ss/NSEC3PARAM
  • ss/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (8)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 47671)
  • ss/DNSKEY (alg 8, id 30286)
  • ss/DNSKEY (alg 8, id 43817)
  • ss/DNSKEY (alg 8, id 48189)
  • ss/DNSKEY (alg 8, id 6831)
  • ss/DS (alg 8, id 43817)
  • ss/DS (alg 8, id 43817)

Delegation statusDelegation status

Secure (1)
  • . to ss

NoticesNotices

Errors (13)
  • ss zone: The following NS name(s) did not resolve to address(es): root.nic.ss
  • ss zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (196.216.162.70, 2001:43f8:e0:1::70)
  • ss zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (196.216.162.70, 2001:43f8:e0:1::70)
  • ss zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (185.17.236.20, 2a03:dd40:3::20)
  • ss/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (196.216.162.70, 2001:43f8:e0:1::70, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
  • ss/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (185.17.236.20, 2a03:dd40:3::20, UDP_-_NOEDNS_)
  • ss/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (196.216.162.70, 2001:43f8:e0:1::70, UDP_-_NOEDNS_)
  • ss/NSEC3PARAM: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (196.216.162.70, 2001:43f8:e0:1::70, UDP_-_NOEDNS_)
  • ss/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (196.216.162.70, 2001:43f8:e0:1::70, TCP_-_NOEDNS_)
  • ss/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (196.216.162.70, 2001:43f8:e0:1::70, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • t0rgxn81eb.ss/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • ss/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • ss/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
  • . to ss: The following NS name(s) were found in the delegation NS RRset (i.e., in the . zone), but not in the authoritative NS RRset: root.nic.ss See RFC 1034, Sec. 4.2.2.
  • ss/DS (alg 8, id 43817): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ss/DS (alg 8, id 43817): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ss/DS (alg 8, id 43817): 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.
  • ss/DS (alg 8, id 43817): 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.
  • t0rgxn81eb.ss/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ss/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