who.int
Updated:
2022-07-22 11:20:26 UTC (873 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 20826)
- NSEC3 proving non-existence of who.int/DS
- int/DNSKEY (alg 7, id 10424)
- int/DNSKEY (alg 7, id 27433)
- int/DNSKEY (alg 7, id 59348)
- int/DNSKEY (alg 7, id 9849)
- 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.
- int zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (128.86.1.20, 137.39.1.3, 2001:630:0:8::14, 2001:630:0:9::14)
- int/DNSKEY: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (128.86.1.20, TCP_-_EDNS0_4096_D_KN)
- int/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (137.39.1.3, 2001:630:0:8::14, 2001:630:0:9::14, UDP_-_EDNS0_4096_D_KN)
- who.int/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (15)
- 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 10424: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG NSEC3 proving non-existence of who.int/DS alg 7, id 59348: 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/DNSKEY alg 7, id 9849: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG int/DNSKEY alg 7, id 9849: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG int/DNSKEY alg 7, id 9849: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG int/DNSKEY alg 7, id 9849: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG int/SOA alg 7, id 10424: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG int/SOA alg 7, id 59348: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- who.int/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
