NSEC3 proving non-existence of google.com.au/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 google.com.au/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
google.com.au/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (11)
NSEC3 proving non-existence of google.com.au/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of google.com.au/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
au/DS (alg 8, id 18875): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
au/DS (alg 8, id 18875): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
au/DS (alg 8, id 18875): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
au/DS (alg 8, id 18875): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
com.au/DS (alg 8, id 14185): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
com.au/DS (alg 8, id 14185): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
com.au/DS (alg 8, id 14185): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
com.au/DS (alg 8, id 14185): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
google.com.au/DS has warnings; select the "Denial of existence" DNSSEC option to see them.