View on GitHub

DNSViz: A DNS visualization tool

spikar.gr

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

RRset statusRRset status

Insecure (13)
  • spikar.gr/A
  • spikar.gr/AAAA
  • 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
Secure (1)
  • gr/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (5)
  • NSEC3 proving non-existence of spikar.gr/MX
  • spikar.gr/DNSKEY (alg 13, id 40325)
  • spikar.gr/DNSKEY (alg 13, id 49225)
  • spikar.gr/DNSKEY (alg 8, id 55379)
  • spikar.gr/DNSKEY (alg 8, id 59538)
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 (36)
  • 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.
  • NSEC3 proving non-existence of spikar.gr/MX: 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/MX: 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/MX: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (216.239.32.110, 216.239.34.110, 216.239.36.110, 216.239.38.110, 2001:4860:4802:32::6e, 2001:4860:4802:34::6e, 2001:4860:4802:36::6e, 2001:4860:4802:38::6e, UDP_-_EDNS0_4096_D_K)
  • NSEC3 proving non-existence of spikar.gr/MX: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (216.239.32.110, 216.239.34.110, 216.239.36.110, 216.239.38.110, 2001:4860:4802:32::6e, 2001:4860:4802:34::6e, 2001:4860:4802:36::6e, 2001:4860:4802:38::6e, UDP_-_EDNS0_4096_D_K)
  • NSEC3 proving non-existence of spikar.gr/MX: The following queries resulted in an answer response, even though the bitmap in the NSEC3 RR indicates that the queried records don't exist: spikar.gr/MX See RFC 5155, Sec. 8.5.
  • NSEC3 proving non-existence of spikar.gr/MX: The following queries resulted in an answer response, even though the bitmap in the NSEC3 RR indicates that the queried records don't exist: spikar.gr/MX See RFC 5155, Sec. 8.5.
  • gr/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (139.91.191.3, UDP_-_EDNS0_512_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/A: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (216.239.32.110, 216.239.34.110, 216.239.36.110, 216.239.38.110, 2001:4860:4802:32::6e, 2001:4860:4802:34::6e, 2001:4860:4802:36::6e, 2001:4860:4802:38::6e, UDP_-_EDNS0_4096_D_K)
  • spikar.gr/A: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (185.136.96.99, 185.136.97.99, 185.136.98.99, 185.136.99.99, 2a06:fb00:1::1:99, 2a06:fb00:1::2:99, 2a06:fb00:1::3:99, 2a06:fb00:1::4:99, UDP_-_EDNS0_4096_D_K)
  • spikar.gr/AAAA: 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: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (216.239.32.110, 216.239.34.110, 216.239.36.110, 216.239.38.110, 2001:4860:4802:32::6e, 2001:4860:4802:34::6e, 2001:4860:4802:36::6e, 2001:4860:4802:38::6e, UDP_-_EDNS0_4096_D_K)
  • spikar.gr/AAAA: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (185.136.96.99, 185.136.97.99, 185.136.98.99, 185.136.99.99, 2a06:fb00:1::1:99, 2a06:fb00:1::2:99, 2a06:fb00:1::3:99, 2a06:fb00:1::4:99, 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, 213.175.210.180, 216.239.32.110, 216.239.34.110, 216.239.36.110, 216.239.38.110, 2001:4860:4802:32::6e, 2001:4860:4802:34::6e, 2001:4860:4802:36::6e, 2001:4860:4802:38::6e, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • spikar.gr/DNSKEY (alg 13, id 40325): The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (185.136.96.99, 185.136.97.99, 185.136.98.99, 185.136.99.99, 2a06:fb00:1::1:99, 2a06:fb00:1::2:99, 2a06:fb00:1::3:99, 2a06:fb00:1::4:99, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • spikar.gr/DNSKEY (alg 13, id 49225): The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (185.136.96.99, 185.136.97.99, 185.136.98.99, 185.136.99.99, 2a06:fb00:1::1:99, 2a06:fb00:1::2:99, 2a06:fb00:1::3:99, 2a06:fb00:1::4:99, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • spikar.gr/DNSKEY (alg 8, id 55379): The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (216.239.32.110, 216.239.34.110, 216.239.36.110, 216.239.38.110, 2001:4860:4802:32::6e, 2001:4860:4802:34::6e, 2001:4860:4802:36::6e, 2001:4860:4802:38::6e, UDP_-_EDNS0_4096_D_K)
  • spikar.gr/DNSKEY (alg 8, id 59538): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (46.226.193.13, 185.136.96.99, 185.136.97.99, 185.136.98.99, 185.136.99.99, 213.175.210.180, 2a06:fb00:1::1:99, 2a06:fb00:1::2:99, 2a06:fb00:1::3:99, 2a06:fb00:1::4:99, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • spikar.gr/DNSKEY (alg 8, id 59538): The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (216.239.32.110, 216.239.34.110, 216.239.36.110, 216.239.38.110, 2001:4860:4802:32::6e, 2001:4860:4802:34::6e, 2001:4860:4802:36::6e, 2001:4860:4802:38::6e, UDP_-_EDNS0_4096_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/MX: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (185.136.96.99, 185.136.97.99, 185.136.98.99, 185.136.99.99, 2a06:fb00:1::1:99, 2a06:fb00:1::2:99, 2a06:fb00:1::3:99, 2a06:fb00:1::4:99, 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. (46.226.193.13, 213.175.210.180, UDP_-_EDNS0_4096_D_K)
  • spikar.gr/NS: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (216.239.32.110, 216.239.34.110, 216.239.36.110, 216.239.38.110, 2001:4860:4802:32::6e, 2001:4860:4802:34::6e, 2001:4860:4802:36::6e, 2001:4860:4802:38::6e, UDP_-_EDNS0_4096_D_K)
  • spikar.gr/NS: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (185.136.96.99, 185.136.97.99, 185.136.98.99, 185.136.99.99, 2a06:fb00:1::1:99, 2a06:fb00:1::2:99, 2a06:fb00:1::3:99, 2a06:fb00:1::4:99, 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. (46.226.193.13, 213.175.210.180, TCP_-_EDNS0_4096_D, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
  • spikar.gr/SOA: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (216.239.32.110, 216.239.34.110, 216.239.36.110, 216.239.38.110, 2001:4860:4802:32::6e, 2001:4860:4802:34::6e, 2001:4860:4802:36::6e, 2001:4860:4802:38::6e, UDP_-_EDNS0_4096_D_K)
  • spikar.gr/SOA: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (185.136.96.99, 185.136.97.99, 185.136.98.99, 185.136.99.99, 2a06:fb00:1::1:99, 2a06:fb00:1::2:99, 2a06:fb00:1::3:99, 2a06:fb00:1::4:99, TCP_-_EDNS0_4096_D, TCP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
  • 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/TXT: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (216.239.32.110, 216.239.34.110, 216.239.36.110, 216.239.38.110, 2001:4860:4802:32::6e, 2001:4860:4802:34::6e, 2001:4860:4802:36::6e, 2001:4860:4802:38::6e, UDP_-_EDNS0_4096_D_K)
  • spikar.gr/TXT: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (185.136.96.99, 185.136.97.99, 185.136.98.99, 185.136.99.99, 2a06:fb00:1::1:99, 2a06:fb00:1::2:99, 2a06:fb00:1::3:99, 2a06:fb00:1::4:99, UDP_-_EDNS0_4096_D_K)
  • spikar.gr/DNSKEY 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.
  • mbopukeh1j.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.
Warnings (18)
  • 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.
  • NSEC3 proving non-existence of spikar.gr/MX: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of spikar.gr/MX: 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.
  • 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, 213.175.210.180, 216.239.32.110, 216.239.34.110, 216.239.36.110, 216.239.38.110, 2001:4860:4802:32::6e, 2001:4860:4802:34::6e, 2001:4860:4802:36::6e, 2001:4860:4802:38::6e, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • spikar.gr/DNSKEY (alg 8, id 55379): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (46.226.193.13, 185.136.96.99, 185.136.97.99, 185.136.98.99, 185.136.99.99, 213.175.210.180, 2a06:fb00:1::1:99, 2a06:fb00:1::2:99, 2a06:fb00:1::3:99, 2a06:fb00:1::4:99, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • mbopukeh1j.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