upu.int
Updated:
2024-12-09 21:23:20 UTC (33 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 20326)
- ./DNSKEY (alg 8, id 61050)
- NSEC3 proving non-existence of upu.int/DS
- int/DNSKEY (alg 13, id 45581)
- 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 (4)
- 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.
- int/DNSKEY: No response was received from the server over UDP (tried 2 times). See RFC 1035, Sec. 4.2. (128.86.1.20, 137.39.1.3, 193.0.9.4, 193.63.94.20, 199.43.133.53, 199.43.134.53, 199.43.135.53, 2001:500:8d::53, 2001:500:8e::53, 2001:500:8f::53, 2001:630:0:8::14, 2001:630:0:9::14, 2001:67c:e0::4, UDP_-_EDNS0_512_D_KN)
- upu.int/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
- 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.
