spikar.gr
Updated:
2023-11-26 11:07:29 UTC (392 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (7)
- spikar.gr/A
- spikar.gr/AAAA
- spikar.gr/MX
- spikar.gr/NS
- spikar.gr/NSEC3PARAM
- spikar.gr/SOA
- spikar.gr/TXT
DNSKEY/DS/NSEC status
Secure (8)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46780)
- 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
Errors (1)
- gr zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (194.0.4.10)
Warnings (6)
- 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.
