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 (2)
  • ss/NS
  • ss/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (9)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26116)
  • ./DNSKEY (alg 8, id 46594)
  • ss/DNSKEY (alg 8, id 43817)
  • ss/DNSKEY (alg 8, id 48189)
  • ss/DNSKEY (alg 8, id 62899)
  • ss/DNSKEY (alg 8, id 64023)
  • 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 server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (185.28.194.194, 185.38.108.108, 196.1.4.230)
  • ss zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (185.28.194.194, 185.38.108.108, 196.1.4.230)
  • ss/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (185.28.194.194, 185.38.108.108, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • ss/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (196.1.4.230, UDP_-_EDNS0_512_D_K, UDP_-_NOEDNS_)
  • ss/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (185.28.194.194, 185.38.108.108, UDP_-_EDNS0_4096_D_K)
  • ss/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (196.1.4.230, UDP_-_NOEDNS_)
  • ss/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (185.28.194.194, 185.38.108.108, TCP_-_EDNS0_4096_D)
  • ss/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (185.28.194.194, 185.38.108.108, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
  • ss/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (196.1.4.230, TCP_-_NOEDNS_)
  • ss/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (196.1.4.230, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • wz2ujchx78.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 (6)
  • 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.
  • wz2ujchx78.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