jp.sharp
Updated:
2020-10-27 10:24:06 UTC (1519 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (2)
- jp.sharp/CNAME
- ualsharp.hs.llnwd.net/A
Secure (3)
- net/SOA
- net/SOA
- sharp/SOA
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26116)
- NSEC3 proving non-existence of jp.sharp/DS
- NSEC3 proving non-existence of llnwd.net/DS
- net/DNSKEY (alg 8, id 15314)
- net/DNSKEY (alg 8, id 35886)
- 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 status
Insecure (2)
- net to llnwd.net
- sharp to jp.sharp
Secure (2)
- . to net
- . to sharp
Notices
Errors (5)
- 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.
- net zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:500:856e::30, 2001:502:1ca1::30, 2001:503:83eb::30, 2001:503:a83e::2:30)
- jp.sharp/DS has errors; select the "Denial of existence" DNSSEC option to see them.
- uyg2h4svm6.jp.sharp/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
- 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.
- 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.
- jp.sharp/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
