NSEC3 proving non-existence of jccbi.gov/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 jccbi.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
jccbi.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
jccbi.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
s4eh6yf092.jccbi.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
jccbi.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
jccbi.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
jccbi.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (19)
NSEC3 proving non-existence of jccbi.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of jccbi.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
RRSIG jccbi.gov/DNSKEY alg 10, id 37445: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG jccbi.gov/DNSKEY alg 10, id 37445: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG jccbi.gov/DNSKEY alg 10, id 37445: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG jccbi.gov/DNSKEY alg 10, id 61632: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG jccbi.gov/DNSKEY alg 10, id 61632: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG jccbi.gov/DNSKEY alg 10, id 61632: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG jccbi.gov/NS alg 10, id 37445: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG jccbi.gov/NSEC3PARAM alg 10, id 37445: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG jccbi.gov/SOA alg 10, id 37445: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG jccbi.gov/TXT alg 10, id 37445: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
jccbi.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
jccbi.gov/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
s4eh6yf092.jccbi.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
jccbi.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
jccbi.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
jccbi.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
jccbi.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.