View on GitHub

DNSViz: A DNS visualization tool

sks-keyservers.net

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

RRset statusRRset status

Secure (3)
  • sks-keyservers.net/A
  • sks-keyservers.net/NS
  • sks-keyservers.net/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (9)
  • ./DNSKEY (alg 8, id 14631)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26838)
  • net/DNSKEY (alg 8, id 35886)
  • net/DNSKEY (alg 8, id 6203)
  • net/DS (alg 8, id 35886)
  • sks-keyservers.net/DNSKEY (alg 8, id 30729)
  • sks-keyservers.net/DNSKEY (alg 8, id 59791)
  • sks-keyservers.net/DS (alg 8, id 30729)

Delegation statusDelegation status

Secure (2)
  • . to net
  • net to sks-keyservers.net

NoticesNotices

Errors (15)
  • sks-keyservers.net zone: The following NS name(s) did not resolve to address(es): ns.dan.host, ns.dan.xxx
  • sks-keyservers.net zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (23.128.97.53, 2607:7c80:53::53)
  • sks-keyservers.net zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (23.128.97.53, 2607:7c80:53::53)
  • sks-keyservers.net/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (23.128.97.53, 2607:7c80:53::53, UDP_-_EDNS0_4096_D_KN)
  • sks-keyservers.net/DNSKEY: The TCP connection was interrupted (ECONNRESET). See RFC 1035, Sec. 4.2. (116.203.66.222, TCP_-_EDNS0_4096_D_KN)
  • sks-keyservers.net/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (23.128.97.53, 2607:7c80:53::53, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • sks-keyservers.net/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (23.128.97.53, 2607:7c80:53::53, UDP_-_EDNS0_4096_D_KN)
  • sks-keyservers.net/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (23.128.97.53, 2607:7c80:53::53, TCP_-_EDNS0_4096_D_N)
  • sks-keyservers.net/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (23.128.97.53, 2607:7c80:53::53, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • sks-keyservers.net/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • sks-keyservers.net/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • sks-keyservers.net/TXT has errors; select the "Denial of existence" DNSSEC option to see them.
  • sks-keyservers.net/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • d479qemoig.sks-keyservers.net/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • sks-keyservers.net/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
  • net to sks-keyservers.net: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the net zone): ns-global.kjsl.com, ns.dan.host See RFC 1034, Sec. 4.2.2.
  • sks-keyservers.net/DS (alg 8, id 30729): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • sks-keyservers.net/DS (alg 8, id 30729): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.

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