View on GitHub

DNSViz: A DNS visualization tool

www.edu.tw

« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Insecure (4)
  • www.edu.tw/A
  • www.edu.tw/AAAA
  • www.edu.tw/NS
  • www.edu.tw/SOA
Secure (4)
  • edu.tw/SOA
  • edu.tw/SOA
  • edu.tw/SOA
  • edu.tw/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (14)
  • ./DNSKEY (alg 8, id 14631)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26838)
  • NSEC3 proving non-existence of www.edu.tw/DS
  • edu.tw/DNSKEY (alg 8, id 13840)
  • edu.tw/DNSKEY (alg 8, id 33619)
  • edu.tw/DNSKEY (alg 8, id 35388)
  • edu.tw/DNSKEY (alg 8, id 3630)
  • edu.tw/DS (alg 8, id 13840)
  • edu.tw/DS (alg 8, id 33619)
  • tw/DNSKEY (alg 8, id 17220)
  • tw/DNSKEY (alg 8, id 30126)
  • tw/DNSKEY (alg 8, id 40792)
  • tw/DS (alg 8, id 40792)

Delegation statusDelegation status

Insecure (1)
  • edu.tw to www.edu.tw
Secure (2)
  • . to tw
  • tw to edu.tw

NoticesNotices

Errors (4)
  • NSEC3 proving non-existence of www.edu.tw/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 www.edu.tw/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • tw zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:b020:0:77::1)
  • www.edu.tw/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
  • NSEC3 proving non-existence of www.edu.tw/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of www.edu.tw/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • edu.tw/DNSKEY (alg 8, id 13840): 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. (2001:45b1:0:5::24, 2001:45b1:0:5::25, UDP_-_EDNS0_4096_D_KN)
  • edu.tw/DNSKEY (alg 8, id 33619): 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. (2001:45b1:0:5::24, 2001:45b1:0:5::25, UDP_-_EDNS0_4096_D_KN)
  • edu.tw/DNSKEY (alg 8, id 35388): 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. (2001:45b1:0:5::24, 2001:45b1:0:5::25, UDP_-_EDNS0_4096_D_KN)
  • edu.tw/DNSKEY (alg 8, id 3630): 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. (2001:45b1:0:5::24, 2001:45b1:0:5::25, UDP_-_EDNS0_4096_D_KN)
  • www.edu.tw/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