View on GitHub

DNSViz: A DNS visualization tool

spikar.gr

« 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 (15)
  • spikar.gr/A
  • spikar.gr/A (NODATA)
  • spikar.gr/AAAA
  • spikar.gr/AAAA (NODATA)
  • spikar.gr/MX
  • spikar.gr/MX (NODATA)
  • spikar.gr/NS
  • spikar.gr/NS
  • spikar.gr/NS
  • spikar.gr/SOA
  • spikar.gr/SOA
  • spikar.gr/SOA
  • spikar.gr/TXT
  • spikar.gr/TXT
  • spikar.gr/TXT (NODATA)
Secure (1)
  • gr/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (2)
  • spikar.gr/DNSKEY (alg 13, id 40325)
  • spikar.gr/DNSKEY (alg 13, id 49225)
Secure (7)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 48903)
  • NSEC3 proving non-existence of spikar.gr/DS
  • gr/DNSKEY (alg 7, id 33317)
  • gr/DNSKEY (alg 7, id 35136)
  • gr/DNSKEY (alg 7, id 7835)
  • gr/DS (alg 7, id 35136)

Delegation statusDelegation status

Insecure (1)
  • gr to spikar.gr
Secure (1)
  • . to gr

NoticesNotices

Errors (19)
  • NSEC3 proving non-existence of spikar.gr/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 spikar.gr/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • gr/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (78.104.145.227, 139.91.191.3, UDP_-_EDNS0_512_D_K)
  • spikar.gr/A (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (208.80.124.4, 208.80.125.4, 208.80.126.4, 208.80.127.4, 208.94.148.4, 208.94.149.4, 2600:1800:10::1, 2600:1800:15::1, 2600:1801:11::1, 2600:1801:13::1, 2600:1802:12::1, 2600:1802:14::1, UDP_-_EDNS0_4096_D_K)
  • spikar.gr/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (46.226.193.13, 213.175.210.180, UDP_-_EDNS0_4096_D_K)
  • spikar.gr/AAAA (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (46.226.193.13, 208.80.124.4, 208.80.125.4, 208.80.126.4, 208.80.127.4, 208.94.148.4, 208.94.149.4, 213.175.210.180, 2600:1800:10::1, 2600:1800:15::1, 2600:1801:11::1, 2600:1801:13::1, 2600:1802:12::1, 2600:1802:14::1, UDP_-_EDNS0_4096_D_K)
  • spikar.gr/DNSKEY (alg 13, id 40325): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (46.226.193.13, 208.80.124.4, 208.80.125.4, 208.80.126.4, 208.80.127.4, 208.94.148.4, 208.94.149.4, 213.175.210.180, 2600:1800:10::1, 2600:1800:15::1, 2600:1801:11::1, 2600:1801:13::1, 2600:1802:12::1, 2600:1802:14::1, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • spikar.gr/MX (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (208.80.124.4, 208.80.125.4, 208.80.126.4, 208.80.127.4, 208.94.148.4, 208.94.149.4, 2600:1800:10::1, 2600:1800:15::1, 2600:1801:11::1, 2600:1801:13::1, 2600:1802:12::1, 2600:1802:14::1, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • spikar.gr/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (46.226.193.13, 213.175.210.180, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • spikar.gr/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (208.80.124.4, 208.80.125.4, 208.80.126.4, 208.80.127.4, 208.94.148.4, 208.94.149.4, 2600:1800:10::1, 2600:1800:15::1, 2600:1801:11::1, 2600:1801:13::1, 2600:1802:12::1, 2600:1802:14::1, UDP_-_EDNS0_4096_D_K)
  • spikar.gr/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (46.226.193.13, 213.175.210.180, UDP_-_EDNS0_4096_D_K)
  • spikar.gr/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (208.80.124.4, 208.80.125.4, 208.80.126.4, 208.80.127.4, 208.94.148.4, 208.94.149.4, 2600:1800:10::1, 2600:1800:15::1, 2600:1801:11::1, 2600:1801:13::1, 2600:1802:12::1, 2600:1802:14::1, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • spikar.gr/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (46.226.193.13, 213.175.210.180, UDP_-_EDNS0_4096_D_K)
  • spikar.gr/TXT (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (208.80.124.4, 208.80.125.4, 208.80.126.4, 208.80.127.4, 208.94.148.4, 208.94.149.4, 2600:1800:10::1, 2600:1800:15::1, 2600:1801:11::1, 2600:1801:13::1, 2600:1802:12::1, 2600:1802:14::1, UDP_-_EDNS0_4096_D_K)
  • spikar.gr/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (46.226.193.13, 213.175.210.180, UDP_-_EDNS0_4096_D_K)
  • spikar.gr/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • ls1m9r7fy2.spikar.gr/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • spikar.gr/DS has errors; select the "Denial of existence" DNSSEC option to see them.
  • spikar.gr/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (21)
  • NSEC3 proving non-existence of spikar.gr/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of spikar.gr/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • RRSIG NSEC3 proving non-existence of spikar.gr/DS alg 7, id 7835: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG NSEC3 proving non-existence of spikar.gr/DS alg 7, id 7835: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gr/DNSKEY alg 7, id 35136: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gr/DNSKEY alg 7, id 35136: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gr/DNSKEY alg 7, id 35136: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gr/DNSKEY alg 7, id 7835: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gr/DNSKEY alg 7, id 7835: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gr/DNSKEY alg 7, id 7835: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gr/SOA alg 7, id 7835: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • gr to spikar.gr: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the gr zone): ns10.dnsmadeeasy.com, ns14.dnsmadeeasy.com, ns13.dnsmadeeasy.com, ns12.dnsmadeeasy.com, ns11.dnsmadeeasy.com, ns15.dnsmadeeasy.com See RFC 1034, Sec. 4.2.2.
  • gr/DNSKEY (alg 7, id 33317): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (78.104.145.227, 139.91.191.3, UDP_-_EDNS0_4096_D_K)
  • gr/DNSKEY (alg 7, id 35136): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (78.104.145.227, 139.91.191.3, UDP_-_EDNS0_4096_D_K)
  • gr/DNSKEY (alg 7, id 7835): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (78.104.145.227, 139.91.191.3, UDP_-_EDNS0_4096_D_K)
  • gr/DS (alg 7, id 35136): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (192.36.148.17, UDP_-_EDNS0_4096_D_K)
  • gr/DS (alg 7, id 35136): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (192.36.148.17, UDP_-_EDNS0_4096_D_K)
  • spikar.gr/DNSKEY (alg 13, id 49225): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (46.226.193.13, 208.80.124.4, 208.80.125.4, 208.80.126.4, 208.80.127.4, 208.94.148.4, 208.94.149.4, 213.175.210.180, 2600:1800:10::1, 2600:1800:15::1, 2600:1801:11::1, 2600:1801:13::1, 2600:1802:12::1, 2600:1802:14::1, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • ls1m9r7fy2.spikar.gr/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • spikar.gr/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • spikar.gr/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