NSEC3 proving non-existence of sjdc.co.jp/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 sjdc.co.jp/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
sjdc.co.jp zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (14.192.44.1)
sjdc.co.jp/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (14.192.44.1, UDP_-_NOEDNS_)
sjdc.co.jp/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (14.192.44.1, UDP_-_NOEDNS_)
sjdc.co.jp/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (5)
NSEC3 proving non-existence of sjdc.co.jp/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of sjdc.co.jp/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
jp to sjdc.co.jp: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the jp zone): ns-491.awsdns-61.com See RFC 1034, Sec. 4.2.2.
jp to sjdc.co.jp: The following NS name(s) were found in the delegation NS RRset (i.e., in the jp zone), but not in the authoritative NS RRset: ns-491.awsdas-61.com See RFC 1034, Sec. 4.2.2.
sjdc.co.jp/DS has warnings; select the "Denial of existence" DNSSEC option to see them.