upu.int
Updated:
2024-08-06 20:28:42 UTC (100 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- upu.int/A
- upu.int/MX
- upu.int/NS
- upu.int/SOA
- upu.int/TXT
Secure (1)
- int/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 20038)
- ./DNSKEY (alg 8, id 20326)
- NSEC3 proving non-existence of upu.int/DS
- int/DNSKEY (alg 13, id 14296)
- int/DNSKEY (alg 13, id 59895)
- int/DS (alg 13, id 59895)
Delegation status
Insecure (1)
- int to upu.int
Secure (1)
- . to int
Notices
Errors (3)
- NSEC3 proving non-existence of upu.int/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 upu.int/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- upu.int/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (5)
- ./DNSKEY (alg 8, id 20038): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
- ./DNSKEY (alg 8, id 20326): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
- NSEC3 proving non-existence of upu.int/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of upu.int/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- upu.int/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
