NSEC3 proving non-existence of wunderground.com/DS
cloud/DNSKEY (alg 8, id 2538)
cloud/DNSKEY (alg 8, id 49804)
cloud/DS (alg 8, id 49804)
cloud/DS (alg 8, id 49804)
com/DNSKEY (alg 8, id 30909)
com/DNSKEY (alg 8, id 58540)
com/DS (alg 8, id 30909)
Delegation status
Insecure (3)
appdomain.cloud to containers.appdomain.cloud
cloud to appdomain.cloud
com to wunderground.com
Secure (2)
. to cloud
. to com
Notices
Errors (2)
NSEC3 proving non-existence of appdomain.cloud/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 appdomain.cloud/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
Warnings (6)
NSEC3 proving non-existence of appdomain.cloud/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of appdomain.cloud/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
cloud/DS (alg 8, id 49804): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
cloud/DS (alg 8, id 49804): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
cloud/DS (alg 8, id 49804): 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.
cloud/DS (alg 8, id 49804): 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.