au.dk
Updated:
2021-06-10 07:06:25 UTC (1262 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- au.dk/A
- au.dk/MX
- au.dk/NS
- au.dk/SOA
- au.dk/TXT
Secure (2)
- dk/SOA
- dk/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 14631)
- ./DNSKEY (alg 8, id 20326)
- NSEC3 proving non-existence of au.dk/DS
- dk/DNSKEY (alg 13, id 26074)
- dk/DNSKEY (alg 13, id 9280)
- dk/DS (alg 13, id 9280)
Delegation status
Insecure (1)
- dk to au.dk
Secure (1)
- . to dk
Notices
Errors (3)
- NSEC3 proving non-existence of au.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 au.dk/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- au.dk/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (5)
- . to dk: The glue address(es) for l.nic.dk (192.38.7.242) differed from its authoritative address(es) (130.226.213.138). See RFC 1034, Sec. 4.2.2.
- . to dk: The glue address(es) for l.nic.dk (2001:7f8:1f::1835:242:0) differed from its authoritative address(es) (2001:878:0:e000:82:e2:d5:8a). See RFC 1034, Sec. 4.2.2.
- NSEC3 proving non-existence of au.dk/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of au.dk/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- au.dk/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
