./DNSKEY (alg 8, id 20038): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
./DNSKEY (alg 8, id 20326): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
RRSIG lbl.gov/A alg 7, id 48167: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG lbl.gov/DNSKEY alg 7, id 33234: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG lbl.gov/DNSKEY alg 7, id 33234: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG lbl.gov/DNSKEY alg 7, id 48167: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG lbl.gov/DNSKEY alg 7, id 48167: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG lbl.gov/MX alg 7, id 48167: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG lbl.gov/NS alg 7, id 48167: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG lbl.gov/SOA alg 7, id 48167: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG lbl.gov/TXT alg 7, id 48167: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
gov/DS (alg 13, id 2536): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
gov/DS (alg 13, id 2536): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
lbl.gov/DS (alg 7, id 33234): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
lbl.gov/DS (alg 7, id 33234): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
lbl.gov/DS (alg 7, id 33234): 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.
lbl.gov/DS (alg 7, id 33234): 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.
lbl.gov/CDNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
lbl.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
lbl.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
lbl.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
lbl.gov/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
lbl.gov/CDS has warnings; select the "Denial of existence" DNSSEC option to see them.
rj2im.vq4ek.lbl.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.