spikar.gr
Updated:
2024-11-08 13:53:04 UTC (44 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (9)
- spikar.gr/A
- spikar.gr/AAAA
- spikar.gr/CDNSKEY
- spikar.gr/CDS
- spikar.gr/MX
- spikar.gr/NS
- spikar.gr/NSEC3PARAM
- spikar.gr/SOA
- spikar.gr/TXT
Secure (1)
- gr/SOA
DNSKEY/DS/NSEC status
Insecure (1)
- spikar.gr/DNSKEY (alg 13, id 4329)
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 61050)
- NSEC3 proving non-existence of spikar.gr/DS
- gr/DNSKEY (alg 8, id 13987)
- gr/DNSKEY (alg 8, id 45264)
- gr/DS (alg 8, id 13987)
Delegation status
Insecure (1)
- gr to spikar.gr
Secure (1)
- . to gr
Notices
Errors (5)
- 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.
- spikar.gr/CDNSKEY: The CDNSKEY RRset must be signed with a key that is represented in both the current DNSKEY and the current DS RRset. See RFC 7344, Sec. 4.1.
- spikar.gr/CDS: The CDS RRset must be signed with a key that is represented in both the current DNSKEY and the current DS RRset. See RFC 7344, Sec. 4.1.
- spikar.gr/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
- 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.
- spikar.gr/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
