View on GitHub

DNSViz: A DNS visualization tool

itu.int

Updated: 2024-05-21 11:51:46 UTC (34 days ago) Update now
« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Insecure (6)
  • itu.int/A
  • itu.int/AAAA
  • itu.int/MX
  • itu.int/NS
  • itu.int/SOA
  • itu.int/TXT
Secure (1)
  • int/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (9)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 5613)
  • NSEC3 proving non-existence of itu.int/DS
  • int/DNSKEY (alg 13, id 59895)
  • int/DNSKEY (alg 13, id 64238)
  • int/DNSKEY (alg 7, id 27433)
  • int/DNSKEY (alg 7, id 47712)
  • int/DNSKEY (alg 7, id 49257)
  • int/DS (alg 7, id 27433)

Delegation statusDelegation status

Insecure (1)
  • int to itu.int
Secure (1)
  • . to int

NoticesNotices

Errors (3)
  • NSEC3 proving non-existence of itu.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 itu.int/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • itu.int/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (12)
  • NSEC3 proving non-existence of itu.int/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of itu.int/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • RRSIG NSEC3 proving non-existence of itu.int/DS alg 7, id 49257: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG int/DNSKEY alg 7, id 27433: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG int/DNSKEY alg 7, id 27433: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG int/DNSKEY alg 7, id 27433: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG int/DNSKEY alg 7, id 27433: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG int/DNSKEY alg 7, id 27433: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG int/SOA alg 7, id 49257: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • itu.int/MX: The server responded with no OPT record, rather than with RCODE FORMERR. See RFC 6891, Sec. 7. (205.251.192.35, 205.251.195.44, 205.251.196.40, 205.251.199.74, 2600:9000:5300:2300::1, 2600:9000:5303:2c00::1, 2600:9000:5304:2800::1, 2600:9000:5307:4a00::1, UDP_-_EDNS0_512_D_KN)
  • itu.int/TXT: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2600:9000:5300:2300::1, UDP_-_EDNS0_4096_D_KN)
  • itu.int/DS has warnings; select the "Denial of existence" DNSSEC option to see them.

DNSKEY legend

Full legend
SEP bit setSEP bit set
Revoke bit setRevoke bit set
Trust anchorTrust anchor
Download: png | svg
Warning JavaScript is required to make the graph below interactive.
DNSSEC authentication graph