View on GitHub

DNSViz: A DNS visualization tool

jp.sharp

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

RRset statusRRset status

Insecure (6)
  • hs.llnwd.net/A (NXDOMAIN)
  • jp.sharp/CNAME
  • llnwd.net/SOA
  • ualsharp.hs.llnwd.net/A
  • ualsharp.hs.llnwd.net/A
  • ualsharp.hs.llnwd.net/A
Secure (3)
  • net/SOA
  • net/SOA
  • sharp/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (10)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 9799)
  • NSEC3 proving non-existence of jp.sharp/DS
  • NSEC3 proving non-existence of llnwd.net/DS
  • net/DNSKEY (alg 8, id 35886)
  • net/DNSKEY (alg 8, id 4604)
  • net/DS (alg 8, id 35886)
  • sharp/DNSKEY (alg 8, id 3872)
  • sharp/DNSKEY (alg 8, id 9504)
  • sharp/DS (alg 8, id 3872)

Delegation statusDelegation status

Insecure (2)
  • net to llnwd.net
  • sharp to jp.sharp
Secure (2)
  • . to net
  • . to sharp

NoticesNotices

Errors (7)
  • NSEC3 proving non-existence of jp.sharp/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 jp.sharp/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • ualsharp.hs.llnwd.net/A: A query for ualsharp.hs.llnwd.net results in a NOERROR response, while a query for its ancestor, hs.llnwd.net, returns a name error (NXDOMAIN), which indicates that subdomains of hs.llnwd.net, including ualsharp.hs.llnwd.net, don't exist. See RFC 8020, Sec. 2. (69.28.143.11, UDP_-_EDNS0_4096_D_KN)
  • ualsharp.hs.llnwd.net/A: A query for ualsharp.hs.llnwd.net results in a NOERROR response, while a query for its ancestor, hs.llnwd.net, returns a name error (NXDOMAIN), which indicates that subdomains of hs.llnwd.net, including ualsharp.hs.llnwd.net, don't exist. See RFC 8020, Sec. 2. (69.28.143.12, 69.28.143.14, UDP_-_EDNS0_4096_D_KN)
  • ualsharp.hs.llnwd.net/A: A query for ualsharp.hs.llnwd.net results in a NOERROR response, while a query for its ancestor, hs.llnwd.net, returns a name error (NXDOMAIN), which indicates that subdomains of hs.llnwd.net, including ualsharp.hs.llnwd.net, don't exist. See RFC 8020, Sec. 2. (69.28.143.13, UDP_-_EDNS0_4096_D_KN)
  • 1bmc087una.jp.sharp/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • jp.sharp/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (8)
  • NSEC3 proving non-existence of jp.sharp/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of jp.sharp/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • hs.llnwd.net/A (NXDOMAIN): The server responded with no OPT record, rather than with RCODE FORMERR. See RFC 6891, Sec. 7. (69.28.143.11, 69.28.143.12, 69.28.143.13, 69.28.143.14, UDP_-_EDNS0_4096_D_KN)
  • sharp to jp.sharp: The following NS name(s) were found in the delegation NS RRset (i.e., in the sharp zone), but not in the authoritative NS RRset: ns1.sharp.co.jp, tg1.sharp.co.jp See RFC 1034, Sec. 4.2.2.
  • ualsharp.hs.llnwd.net/A: The server responded with no OPT record, rather than with RCODE FORMERR. See RFC 6891, Sec. 7. (69.28.143.11, UDP_-_EDNS0_4096_D_KN)
  • ualsharp.hs.llnwd.net/A: The server responded with no OPT record, rather than with RCODE FORMERR. See RFC 6891, Sec. 7. (69.28.143.12, 69.28.143.14, UDP_-_EDNS0_4096_D_KN)
  • ualsharp.hs.llnwd.net/A: The server responded with no OPT record, rather than with RCODE FORMERR. See RFC 6891, Sec. 7. (69.28.143.13, UDP_-_EDNS0_4096_D_KN)
  • jp.sharp/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