View on GitHub

DNSViz: A DNS visualization tool

www.bfm.fju.edu.tw

Updated: 2024-08-15 12:22:26 UTC (280 days ago) Update now
« 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 (1)
  • www.bfm.fju.edu.tw/A
Secure (2)
  • edu.tw/SOA
  • edu.tw/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (11)
  • ./DNSKEY (alg 8, id 20038)
  • ./DNSKEY (alg 8, id 20326)
  • NSEC3 proving non-existence of fju.edu.tw/DS
  • edu.tw/DNSKEY (alg 8, id 12423)
  • edu.tw/DNSKEY (alg 8, id 17793)
  • edu.tw/DNSKEY (alg 8, id 24025)
  • edu.tw/DNSKEY (alg 8, id 34914)
  • edu.tw/DS (alg 8, id 24025)
  • tw/DNSKEY (alg 8, id 41124)
  • tw/DNSKEY (alg 8, id 51277)
  • tw/DS (alg 8, id 51277)

Delegation statusDelegation status

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

NoticesNotices

Errors (6)
  • NSEC3 proving non-existence of fju.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 fju.edu.tw/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • edu.tw zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:288:0:233::3, 2001:288:0:233::4)
  • edu.tw/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:288:0:34::133, 2001:288:0:34::134, UDP_-_NOEDNS_)
  • edu.tw/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2001:288:0:34::133, 2001:288:0:34::134, 2001:45b1:0:5::24, 2001:45b1:0:5::25, UDP_-_EDNS0_512_D_KN)
  • fju.edu.tw zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (122.255.93.135)
Warnings (7)
  • ./DNSKEY (alg 8, id 20038): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
  • ./DNSKEY (alg 8, id 20326): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
  • NSEC3 proving non-existence of fju.edu.tw/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of fju.edu.tw/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • edu.tw to fju.edu.tw: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the edu.tw zone): nttdns.fju.edu.tw See RFC 1034, Sec. 4.2.2.
  • edu.tw to fju.edu.tw: The glue address(es) for dns2.fju.edu.tw (140.136.247.251) differed from its authoritative address(es) (140.136.200.8, 140.136.247.251). See RFC 1034, Sec. 4.2.2.
  • edu.tw to fju.edu.tw: The glue address(es) for fns2.fju.edu.tw (140.136.200.88) differed from its authoritative address(es) (140.136.200.88, 140.136.247.251). See RFC 1034, Sec. 4.2.2.

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