brainplus.jp.sharp
Updated:
2020-11-03 05:45:18 UTC (1480 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (4)
- brainplus.jp.sharp/NS
- brainplus.jp.sharp/SOA
- jp.sharp/CNAME
- sharp/SOA
Secure (1)
- sharp/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26116)
- NSEC3 proving non-existence of jp.sharp/DS
- sharp/DNSKEY (alg 8, id 3872)
- sharp/DNSKEY (alg 8, id 9504)
- sharp/DS (alg 8, id 3872)
Delegation status
Insecure (2)
- jp.sharp to brainplus.jp.sharp
- sharp to jp.sharp
Secure (1)
- . 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.
- jp.sharp to brainplus.jp.sharp: An SOA RR with owner name (sharp) not matching the zone name (jp.sharp) was returned with the NODATA response. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (61.214.248.154, 61.214.248.155, UDP_-_EDNS0_4096_D_K)
- sharp/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (61.214.248.154, 61.214.248.155, UDP_-_EDNS0_4096_D_K)
- brainplus.jp.sharp/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
- 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.
JavaScript is required to make the graph below interactive.
