View on GitHub

DNSViz: A DNS visualization tool

www.sk-nic.sk

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

RRset statusRRset status

Insecure (7)
  • pub-1.tld.sk/A
  • pub-1.tld.sk/A (NODATA)
  • pub-1.tld.sk/AAAA
  • pub-1.tld.sk/AAAA (NODATA)
  • www.sk-nic.sk/A (NODATA)
  • www.sk-nic.sk/AAAA (NODATA)
  • www.sk-nic.sk/CNAME
Secure (2)
  • sk/SOA
  • sk/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (4)
  • NSEC3 proving non-existence of pub-1.tld.sk/A
  • NSEC3 proving non-existence of pub-1.tld.sk/AAAA
  • NSEC3 proving non-existence of www.sk-nic.sk/A
  • NSEC3 proving non-existence of www.sk-nic.sk/AAAA
Secure (9)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 33853)
  • ./DNSKEY (alg 8, id 48903)
  • NSEC3 proving non-existence of sk-nic.sk/DS
  • NSEC3 proving non-existence of tld.sk/DS
  • sk/DNSKEY (alg 13, id 2324)
  • sk/DNSKEY (alg 13, id 49898)
  • sk/DNSKEY (alg 13, id 53710)
  • sk/DS (alg 13, id 2324)

Delegation statusDelegation status

Insecure (2)
  • sk to sk-nic.sk
  • sk to tld.sk
Secure (1)
  • . to sk

NoticesNotices

Errors (46)
  • NSEC3 proving non-existence of pub-1.tld.sk/A: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of pub-1.tld.sk/A: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of pub-1.tld.sk/A: No NSEC3 RR matches the SNAME (pub-1.tld.sk). See RFC 5155, Sec. 8.5.
  • NSEC3 proving non-existence of pub-1.tld.sk/A: No NSEC3 RR matches the SNAME (pub-1.tld.sk). See RFC 5155, Sec. 8.5.
  • NSEC3 proving non-existence of pub-1.tld.sk/AAAA: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of pub-1.tld.sk/AAAA: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of pub-1.tld.sk/AAAA: No NSEC3 RR matches the SNAME (pub-1.tld.sk). See RFC 5155, Sec. 8.5.
  • NSEC3 proving non-existence of pub-1.tld.sk/AAAA: No NSEC3 RR matches the SNAME (pub-1.tld.sk). See RFC 5155, Sec. 8.5.
  • NSEC3 proving non-existence of sk-nic.sk/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of sk-nic.sk/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of tld.sk/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of tld.sk/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of www.sk-nic.sk/A: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of www.sk-nic.sk/A: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of www.sk-nic.sk/A: No NSEC3 RR matches the SNAME (www.sk-nic.sk). See RFC 5155, Sec. 8.5.
  • NSEC3 proving non-existence of www.sk-nic.sk/A: No NSEC3 RR matches the SNAME (www.sk-nic.sk). See RFC 5155, Sec. 8.5.
  • NSEC3 proving non-existence of www.sk-nic.sk/AAAA: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of www.sk-nic.sk/AAAA: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of www.sk-nic.sk/AAAA: No NSEC3 RR matches the SNAME (www.sk-nic.sk). See RFC 5155, Sec. 8.5.
  • NSEC3 proving non-existence of www.sk-nic.sk/AAAA: No NSEC3 RR matches the SNAME (www.sk-nic.sk). See RFC 5155, Sec. 8.5.
  • RRSIG NSEC3 proving non-existence of pub-1.tld.sk/A alg 13, id 53710: The Signer's Name field of the RRSIG RR (sk) does not match the name of the zone containing the RRset (tld.sk). See RFC 4035, Sec. 5.3.1.
  • RRSIG NSEC3 proving non-existence of pub-1.tld.sk/A alg 13, id 53710: The Signer's Name field of the RRSIG RR (sk) does not match the name of the zone containing the RRset (tld.sk). See RFC 4035, Sec. 5.3.1.
  • RRSIG NSEC3 proving non-existence of pub-1.tld.sk/AAAA alg 13, id 53710: The Signer's Name field of the RRSIG RR (sk) does not match the name of the zone containing the RRset (tld.sk). See RFC 4035, Sec. 5.3.1.
  • RRSIG NSEC3 proving non-existence of pub-1.tld.sk/AAAA alg 13, id 53710: The Signer's Name field of the RRSIG RR (sk) does not match the name of the zone containing the RRset (tld.sk). See RFC 4035, Sec. 5.3.1.
  • RRSIG NSEC3 proving non-existence of www.sk-nic.sk/A alg 13, id 53710: The Signer's Name field of the RRSIG RR (sk) does not match the name of the zone containing the RRset (sk-nic.sk). See RFC 4035, Sec. 5.3.1.
  • RRSIG NSEC3 proving non-existence of www.sk-nic.sk/A alg 13, id 53710: The Signer's Name field of the RRSIG RR (sk) does not match the name of the zone containing the RRset (sk-nic.sk). See RFC 4035, Sec. 5.3.1.
  • RRSIG NSEC3 proving non-existence of www.sk-nic.sk/AAAA alg 13, id 53710: The Signer's Name field of the RRSIG RR (sk) does not match the name of the zone containing the RRset (sk-nic.sk). See RFC 4035, Sec. 5.3.1.
  • RRSIG NSEC3 proving non-existence of www.sk-nic.sk/AAAA alg 13, id 53710: The Signer's Name field of the RRSIG RR (sk) does not match the name of the zone containing the RRset (sk-nic.sk). See RFC 4035, Sec. 5.3.1.
  • pub-1.tld.sk/A (NODATA): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (194.169.218.16, 2001:67c:13cc::1:16, UDP_-_EDNS0_4096_D_K)
  • pub-1.tld.sk/A (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (194.169.218.16, 2001:67c:13cc::1:16, UDP_-_EDNS0_4096_D_K)
  • pub-1.tld.sk/A: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (185.24.64.16, 212.18.248.16, 212.18.249.16, 2a04:2b00:13cc::1:16, 2a04:2b00:13ee::16, 2a04:2b00:13ff::16, UDP_-_NOEDNS_)
  • pub-1.tld.sk/AAAA (NODATA): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (194.169.218.16, 2001:67c:13cc::1:16, UDP_-_EDNS0_4096_D_K)
  • pub-1.tld.sk/AAAA (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (194.169.218.16, 2001:67c:13cc::1:16, UDP_-_EDNS0_4096_D_K)
  • pub-1.tld.sk/AAAA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (185.24.64.16, 212.18.248.16, 212.18.249.16, 2a04:2b00:13cc::1:16, 2a04:2b00:13ee::16, 2a04:2b00:13ff::16, UDP_-_NOEDNS_)
  • sk-nic.sk zone: The server(s) did not respond authoritatively for the namespace. See RFC 1035, Sec. 4.1.1. (185.24.64.16, 194.169.218.16, 212.18.248.16, 212.18.249.16, 2001:67c:13cc::1:16, 2a04:2b00:13cc::1:16, 2a04:2b00:13ee::16, 2a04:2b00:13ff::16)
  • sk-nic.sk/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (185.24.64.16, 212.18.248.16, 212.18.249.16, 2a04:2b00:13cc::1:16, 2a04:2b00:13ee::16, 2a04:2b00:13ff::16, UDP_-_EDNS0_512_D_K, UDP_-_NOEDNS_)
  • tld.sk zone: The server(s) did not respond authoritatively for the namespace. See RFC 1035, Sec. 4.1.1. (185.24.64.16, 194.169.218.16, 212.18.248.16, 212.18.249.16, 2001:67c:13cc::1:16, 2a04:2b00:13cc::1:16, 2a04:2b00:13ee::16, 2a04:2b00:13ff::16)
  • tld.sk zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (109.71.66.141, 109.71.66.142)
  • tld.sk/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (185.24.64.16, 212.18.248.16, 212.18.249.16, 2a04:2b00:13cc::1:16, 2a04:2b00:13ee::16, 2a04:2b00:13ff::16, UDP_-_EDNS0_512_D_K, UDP_-_NOEDNS_)
  • www.sk-nic.sk/A (NODATA): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (194.169.218.16, 2001:67c:13cc::1:16, UDP_-_EDNS0_4096_D_K)
  • www.sk-nic.sk/A (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (194.169.218.16, 2001:67c:13cc::1:16, UDP_-_EDNS0_4096_D_K)
  • www.sk-nic.sk/A: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (185.24.64.16, 212.18.248.16, 212.18.249.16, 2a04:2b00:13cc::1:16, 2a04:2b00:13ee::16, 2a04:2b00:13ff::16, UDP_-_NOEDNS_)
  • www.sk-nic.sk/AAAA (NODATA): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (194.169.218.16, 2001:67c:13cc::1:16, UDP_-_EDNS0_4096_D_K)
  • www.sk-nic.sk/AAAA (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (194.169.218.16, 2001:67c:13cc::1:16, UDP_-_EDNS0_4096_D_K)
  • www.sk-nic.sk/AAAA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (185.24.64.16, 212.18.248.16, 212.18.249.16, 2a04:2b00:13cc::1:16, 2a04:2b00:13ee::16, 2a04:2b00:13ff::16, UDP_-_NOEDNS_)
  • sk-nic.sk/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
  • sk to sk-nic.sk: The following NS name(s) were found in the delegation NS RRset (i.e., in the sk zone), but not in the authoritative NS RRset: e.tld.sk, f.tld.sk, g.tld.sk, h.tld.sk See RFC 1034, Sec. 4.2.2.
  • sk to tld.sk: The following NS name(s) were found in the delegation NS RRset (i.e., in the sk zone), but not in the authoritative NS RRset: e.tld.sk, f.tld.sk, g.tld.sk, h.tld.sk, signer-1.tld.sk, signer-2.tld.sk See RFC 1034, Sec. 4.2.2.
  • sk-nic.sk/DNSKEY: The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (194.169.218.16, 2001:67c:13cc::1:16, UDP_-_EDNS0_512_D_K)
  • tld.sk/DNSKEY: The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (194.169.218.16, 2001:67c:13cc::1:16, UDP_-_EDNS0_512_D_K)

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