spikar.gr
Updated:
2024-09-30 17:59:58 UTC (5 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Secure (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
DNSKEY/DS/NSEC status
Secure (9)
- ./DNSKEY (alg 8, id 20038)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 61050)
- gr/DNSKEY (alg 8, id 13987)
- gr/DNSKEY (alg 8, id 45264)
- gr/DS (alg 8, id 13987)
- spikar.gr/DNSKEY (alg 13, id 4329)
- spikar.gr/DS (alg 13, id 4329)
- spikar.gr/DS (alg 13, id 4329)
Delegation status
Secure (2)
- . to gr
- gr to spikar.gr
Notices
Warnings (7)
- spikar.gr/CDS: The contents of the DS RRset are inconsistent with those of the CDS RRset. See RFC 7344, Sec. 3, RFC 7344, Sec. 5.
- spikar.gr/DS (alg 13, id 4329): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- spikar.gr/DS (alg 13, id 4329): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- spikar.gr/DS (alg 13, id 4329): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- spikar.gr/DS (alg 13, id 4329): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- spikar.gr/DS (alg 13, id 4329): In the spirit of RFC 4509, DS records with digest type 1 (SHA-1) might be ignored when DS records with digest type 4 (SHA-384) exist in the same RRset. See RFC 4509, Sec. 3.
- spikar.gr/DS (alg 13, id 4329): In the spirit of RFC 4509, DS records with digest type 1 (SHA-1) might be ignored when DS records with digest type 4 (SHA-384) exist in the same RRset. See RFC 4509, Sec. 3.
JavaScript is required to make the graph below interactive.
