View on GitHub

DNSViz: A DNS visualization tool

sks-keyservers.net

Updated: 2022-08-11 16:38:57 UTC (887 days ago) Update now
« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 20826)
  • net/DNSKEY (alg 8, id 35886)
  • net/DNSKEY (alg 8, id 4403)
  • net/DS (alg 8, id 35886)
  • sks-keyservers.net/DS (alg 8, id 30729)
Non_existent (1)
  • sks-keyservers.net/DNSKEY (alg 8, id 30729)

Delegation statusDelegation status

Bogus (1)
  • net to sks-keyservers.net
Secure (1)
  • . to net

NoticesNotices

Errors (29)
  • net to sks-keyservers.net: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11.
  • sks-keyservers.net zone: The following NS name(s) did not resolve to address(es): 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. (82.148.225.245, 116.203.66.222, 192.146.137.10, 2001:67c:26b4:7:21e:bff:fec7:87a, 2a00:1b98:1:0:20c:29ff:fe83:d782, 2a01:4f8:c0c:97af:ca62:cd80:657f:18cc)
  • 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. (82.148.225.245, 116.203.66.222, 192.146.137.10, 2001:67c:26b4:7:21e:bff:fec7:87a, 2a00:1b98:1:0:20c:29ff:fe83:d782, 2a01:4f8:c0c:97af:ca62:cd80:657f:18cc)
  • sks-keyservers.net zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (192.146.137.185)
  • sks-keyservers.net zone: There was an error resolving the following NS name(s) to address(es): s01.sks-keyservers.net
  • sks-keyservers.net/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (192.146.137.185, UDP_-_NOEDNS_)
  • sks-keyservers.net/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (192.146.137.10, 2001:67c:26b4:7:21e:bff:fec7:87a, UDP_-_EDNS0_4096_D_KN)
  • sks-keyservers.net/A: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (82.148.225.245, 116.203.66.222, 2a00:1b98:1:0:20c:29ff:fe83:d782, 2a01:4f8:c0c:97af:ca62:cd80:657f:18cc, UDP_-_NOEDNS_)
  • sks-keyservers.net/AAAA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (192.146.137.10, 2001:67c:26b4:7:21e:bff:fec7:87a, UDP_-_EDNS0_4096_D_KN)
  • sks-keyservers.net/AAAA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (82.148.225.245, 116.203.66.222, 2a00:1b98:1:0:20c:29ff:fe83:d782, 2a01:4f8:c0c:97af:ca62:cd80:657f:18cc, UDP_-_NOEDNS_)
  • sks-keyservers.net/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (192.146.137.10, 2001:67c:26b4:7:21e:bff:fec7:87a, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • sks-keyservers.net/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (82.148.225.245, 116.203.66.222, 2a00:1b98:1:0:20c:29ff:fe83:d782, 2a01:4f8:c0c:97af:ca62:cd80:657f:18cc, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
  • sks-keyservers.net/MX: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (192.146.137.10, 2001:67c:26b4:7:21e:bff:fec7:87a, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • sks-keyservers.net/MX: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (82.148.225.245, 116.203.66.222, 2a00:1b98:1:0:20c:29ff:fe83:d782, 2a01:4f8:c0c:97af:ca62:cd80:657f:18cc, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
  • sks-keyservers.net/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (192.146.137.185, UDP_-_NOEDNS_)
  • sks-keyservers.net/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (192.146.137.10, 2001:67c:26b4:7:21e:bff:fec7:87a, UDP_-_EDNS0_4096_D_KN)
  • sks-keyservers.net/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (82.148.225.245, 116.203.66.222, 2a00:1b98:1:0:20c:29ff:fe83:d782, 2a01:4f8:c0c:97af:ca62:cd80:657f:18cc, UDP_-_NOEDNS_)
  • sks-keyservers.net/NSEC3PARAM: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (192.146.137.10, 2001:67c:26b4:7:21e:bff:fec7:87a, UDP_-_EDNS0_4096_D_KN)
  • sks-keyservers.net/NSEC3PARAM: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (82.148.225.245, 116.203.66.222, 2a00:1b98:1:0:20c:29ff:fe83:d782, 2a01:4f8:c0c:97af:ca62:cd80:657f:18cc, UDP_-_NOEDNS_)
  • sks-keyservers.net/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (192.146.137.10, 2001:67c:26b4:7:21e:bff:fec7:87a, TCP_-_EDNS0_4096_D_N)
  • sks-keyservers.net/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (192.146.137.10, 2001:67c:26b4:7:21e:bff:fec7:87a, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • sks-keyservers.net/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (82.148.225.245, 116.203.66.222, 2a00:1b98:1:0:20c:29ff:fe83:d782, 2a01:4f8:c0c:97af:ca62:cd80:657f:18cc, TCP_-_NOEDNS_)
  • sks-keyservers.net/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (82.148.225.245, 116.203.66.222, 2a00:1b98:1:0:20c:29ff:fe83:d782, 2a01:4f8:c0c:97af:ca62:cd80:657f:18cc, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • sks-keyservers.net/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (192.146.137.10, 2001:67c:26b4:7:21e:bff:fec7:87a, UDP_-_EDNS0_4096_D_KN)
  • sks-keyservers.net/TXT: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (82.148.225.245, 116.203.66.222, 2a00:1b98:1:0:20c:29ff:fe83:d782, 2a01:4f8:c0c:97af:ca62:cd80:657f:18cc, UDP_-_NOEDNS_)
  • gd94osulfp.sks-keyservers.net/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • sks-keyservers.net/DNSKEY 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.
Warnings (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