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.
RRSIG jp.sharp/CNAME alg 8, id 26718: The Signer's Name field of the RRSIG RR (sharp) does not match the name of the zone containing the RRset (jp.sharp). See RFC 4035, Sec. 5.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/TXT has errors; select the "Denial of existence" DNSSEC option to see them.
jp.sharp/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
dui2qv9bz8.jp.sharp/A has errors; select the "Denial of existence" DNSSEC option to see them.
jp.sharp/SOA has errors; select the "Denial of existence" DNSSEC option to see them.
jp.sharp/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
jp.sharp/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
jp.sharp/MX has errors; select the "Denial of existence" DNSSEC option to see them.
jp.sharp/NS 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 (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.