jyu.fi
Updated:
2023-11-07 08:36:12 UTC (382 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- jyu.fi/A
- jyu.fi/MX
- jyu.fi/NS
- jyu.fi/SOA
- jyu.fi/TXT
Secure (1)
- fi/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46780)
- NSEC3 proving non-existence of jyu.fi/DS
- fi/DNSKEY (alg 8, id 13320)
- fi/DNSKEY (alg 8, id 35221)
- fi/DS (alg 8, id 35221)
Delegation status
Insecure (1)
- fi to jyu.fi
Secure (1)
- . to fi
Notices
Errors (3)
- NSEC3 proving non-existence of jyu.fi/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 jyu.fi/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- jyu.fi/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (5)
- NSEC3 proving non-existence of jyu.fi/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of jyu.fi/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- fi/DS (alg 8, id 35221): No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
- fi/DS (alg 8, id 35221): No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
- jyu.fi/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
