ku.dk
Updated:
2022-11-10 09:49:11 UTC (743 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- ku.dk/A
- ku.dk/MX
- ku.dk/NS
- ku.dk/SOA
- ku.dk/TXT
Secure (1)
- dk/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 18733)
- ./DNSKEY (alg 8, id 20326)
- NSEC3 proving non-existence of ku.dk/DS
- dk/DNSKEY (alg 13, id 2329)
- dk/DNSKEY (alg 13, id 29434)
- dk/DS (alg 13, id 29434)
Delegation status
Insecure (1)
- dk to ku.dk
Secure (1)
- . to dk
Notices
Errors (4)
- NSEC3 proving non-existence of ku.dk/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 ku.dk/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- dk zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2a00:d78:0:102:193:176:144:15)
- ku.dk/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (5)
- NSEC3 proving non-existence of ku.dk/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of ku.dk/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- dk to ku.dk: Authoritative AAAA records exist for ns1.ku.dk, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- dk to ku.dk: Authoritative AAAA records exist for ns2.ku.dk, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- ku.dk/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
