who.int
Updated:
2020-10-21 11:39:11 UTC (1539 days ago)
Go to most recent »
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 (8)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26116)
- NSEC3 proving non-existence of who.int/DS
- int/DNSKEY (alg 7, id 11742)
- int/DNSKEY (alg 7, id 12465)
- int/DNSKEY (alg 7, id 27433)
- int/DNSKEY (alg 7, id 48939)
- int/DS (alg 7, id 27433)
Delegation status
Insecure (1)
- int to who.int
Secure (1)
- . to int
Notices
Errors (6)
- 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 zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (1.9.217.220)
- who.int/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (1.9.217.220, UDP_-_NOEDNS_)
- who.int/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (1.9.217.220, UDP_-_NOEDNS_)
- who.int/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (10)
- 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.
- RRSIG NSEC3 proving non-existence of who.int/DS alg 7, id 12465: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG int/DNSKEY alg 7, id 27433: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG int/DNSKEY alg 7, id 27433: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG int/DNSKEY alg 7, id 27433: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG int/DNSKEY alg 7, id 27433: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG int/SOA alg 7, id 12465: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- int to who.int: The glue address(es) for whqdns3.who.int (1.9.217.220) differed from its authoritative address(es) (211.24.11.120). See RFC 1034, Sec. 4.2.2.
- who.int/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
