spikar.gr
Updated:
2021-04-04 10:20:09 UTC (1361 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- spikar.gr/A
- spikar.gr/AAAA
- spikar.gr/MX
- spikar.gr/NS
- spikar.gr/SOA
- spikar.gr/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 14631)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 42351)
- gr/DNSKEY (alg 7, id 33317)
- gr/DNSKEY (alg 7, id 35136)
- gr/DNSKEY (alg 7, id 7835)
- gr/DS (alg 7, id 35136)
- 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 (3)
- gr/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (78.104.145.227, UDP_-_EDNS0_512_D_KN)
- z8qnfh7raj.spikar.gr/A 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 (20)
- 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 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 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.
- 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_KN)
- 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_KN)
- 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_KN)
- 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.
- z8qnfh7raj.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.
JavaScript is required to make the graph below interactive.
