View on GitHub

DNSViz: A DNS visualization tool

www.babushop.com.tw

Updated: 2020-11-09 08:16:43 UTC (1877 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 (2)
  • babushop.com.tw/A (NXDOMAIN)
  • www.babushop.com.tw/A (NXDOMAIN)
Secure (4)
  • com.tw/SOA
  • com.tw/SOA
  • com.tw/SOA
  • com.tw/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (10)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26116)
  • NSEC3 proving non-existence of babushop.com.tw/A
  • NSEC3 proving non-existence of www.babushop.com.tw/A
  • com.tw/DNSKEY (alg 8, id 31120)
  • com.tw/DNSKEY (alg 8, id 49395)
  • com.tw/DS (alg 8, id 31120)
  • tw/DNSKEY (alg 8, id 40792)
  • tw/DNSKEY (alg 8, id 58488)
  • tw/DS (alg 8, id 40792)

Delegation statusDelegation status

Secure (2)
  • . to tw
  • tw to com.tw

NoticesNotices

Errors (7)
  • NSEC3 proving non-existence of babushop.com.tw/A: 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 babushop.com.tw/A: 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.babushop.com.tw/A: 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.babushop.com.tw/A: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • com.tw zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:cd8:400::196, 2001:b000:1e0:c000::12)
  • tw zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:cd8:400::195, 2001:b000:1e0:c000::11, 2001:b020:0:77::1)
  • com.tw/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
  • NSEC3 proving non-existence of babushop.com.tw/A: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of babushop.com.tw/A: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of www.babushop.com.tw/A: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of www.babushop.com.tw/A: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • tw/DNSKEY (alg 8, id 40792): 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:dd8:12::53, UDP_-_EDNS0_4096_D_K)
  • tw/DNSKEY (alg 8, id 58488): 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:dd8:12::53, UDP_-_EDNS0_4096_D_K)
  • com.tw/CNAME 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