who.int
Updated:
2024-11-22 14:36:16 UTC (19 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- who.int/A
- who.int/MX
- who.int/NS
- who.int/SOA
- who.int/TXT
Secure (1)
- int/SOA
DNSKEY/DS/NSEC status
Secure (7)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 61050)
- NSEC3 proving non-existence of who.int/DS
- int/DNSKEY (alg 13, id 45581)
- int/DNSKEY (alg 13, id 54453)
- int/DNSKEY (alg 13, id 59895)
- int/DS (alg 13, id 59895)
Delegation status
Insecure (1)
- int to who.int
Secure (1)
- . to int
Notices
Errors (3)
- NSEC3 proving non-existence of who.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 who.int/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- who.int/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
- NSEC3 proving non-existence of who.int/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of who.int/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- who.int/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
- who.int/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
