jancsi.cz
Updated:
2023-01-29 21:38:33 UTC (693 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (4)
- jancsi.cz/A
- jancsi.cz/AAAA
- jancsi.cz/NS
- jancsi.cz/SOA
Secure (1)
- cz/SOA
DNSKEY/DS/NSEC status
Insecure (3)
- jancsi.cz/DNSKEY (alg 13, id 13507)
- jancsi.cz/DNSKEY (alg 13, id 53803)
- jancsi.cz/DNSKEY (alg 13, id 54314)
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 951)
- NSEC3 proving non-existence of jancsi.cz/DS
- cz/DNSKEY (alg 13, id 13839)
- cz/DNSKEY (alg 13, id 20237)
- cz/DS (alg 13, id 20237)
Delegation status
Insecure (1)
- cz to jancsi.cz
Secure (1)
- . to cz
Notices
Errors (3)
- jancsi.cz/SOA: DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 10 times) with the DO bit set. See RFC 4035, Sec. 3.2.1. (2a0e:acc0::cafe:cafe:cafe, UDP_-_EDNS0_4096_)
- jancsi.cz/SOA: No response was received from the server over UDP (tried 10 times) until the DO EDNS flag was cleared (however, this server appeared to respond legitimately to other queries with the DO EDNS flag set). See RFC 6891, Sec. 6.1.4. (2a0e:acc0::cafe:cafe:cafe, UDP_-_EDNS0_4096_D_KN)
- jancsi.cz/SOA: The DNSSEC records necessary to validate the response could not be retrieved from the server. See RFC 4035, Sec. 3.1.1, RFC 4035, Sec. 3.1.3. (2a0e:acc0::cafe:cafe:cafe, UDP_-_EDNS0_4096_D_KN)
Warnings (13)
- NSEC3 proving non-existence of jancsi.cz/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of jancsi.cz/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- jancsi.cz/A: 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. (2a0e:acc0::cafe:cafe:cafe, UDP_-_EDNS0_4096_D_KN)
- jancsi.cz/DNSKEY (alg 13, id 13507): 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. (2a0e:acc0::caff:caff:caff, UDP_-_EDNS0_4096_D_KN)
- jancsi.cz/DNSKEY (alg 13, id 53803): 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. (2a0e:acc0::caff:caff:caff, UDP_-_EDNS0_4096_D_KN)
- jancsi.cz/DNSKEY (alg 13, id 54314): 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. (2a0e:acc0::caff:caff:caff, UDP_-_EDNS0_4096_D_KN)
- jancsi.cz/NS: 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. (2a0e:acc0::cafe:cafe:cafe, UDP_-_EDNS0_4096_D_KN)
- jancsi.cz/TXT has warnings; select the "Denial of existence" DNSSEC option to see them.
- jancsi.cz/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- jancsi.cz/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
- jancsi.cz/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
- iqhuep3olz.jancsi.cz/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- jancsi.cz/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
