RRSIG biopreferred.gov/DNSKEY alg 8, id 18828: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 11 hours, 33 minutes after it expires at 2024-10-12 12:24:10+00:00. See RFC 4035, Sec. 5.3.3.
RRSIG biopreferred.gov/DNSKEY alg 8, id 18828: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 11 hours, 33 minutes after it expires at 2024-10-12 12:24:10+00:00. See RFC 4035, Sec. 5.3.3.
RRSIG biopreferred.gov/DNSKEY alg 8, id 18828: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 11 hours, 33 minutes after it expires at 2024-10-12 12:24:10+00:00. See RFC 4035, Sec. 5.3.3.
RRSIG biopreferred.gov/DNSKEY alg 8, id 5920: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 11 hours, 33 minutes after it expires at 2024-10-12 12:24:10+00:00. See RFC 4035, Sec. 5.3.3.
RRSIG biopreferred.gov/DNSKEY alg 8, id 5920: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 11 hours, 33 minutes after it expires at 2024-10-12 12:24:10+00:00. See RFC 4035, Sec. 5.3.3.
RRSIG biopreferred.gov/DNSKEY alg 8, id 5920: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 11 hours, 33 minutes after it expires at 2024-10-12 12:24:10+00:00. See RFC 4035, Sec. 5.3.3.
RRSIG biopreferred.gov/DNSKEY alg 8, id 6574: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 11 hours, 33 minutes after it expires at 2024-10-12 12:24:10+00:00. See RFC 4035, Sec. 5.3.3.
RRSIG biopreferred.gov/DNSKEY alg 8, id 6574: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 11 hours, 33 minutes after it expires at 2024-10-12 12:24:10+00:00. See RFC 4035, Sec. 5.3.3.
RRSIG biopreferred.gov/DNSKEY alg 8, id 6574: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 11 hours, 33 minutes after it expires at 2024-10-12 12:24:10+00:00. See RFC 4035, Sec. 5.3.3.
biopreferred.gov/CDNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.141.126.202, 199.141.126.206, 2600:12f0:0:ac04::202, 2600:12f0:0:ac04::206, UDP_-_NOEDNS_)
biopreferred.gov/CDS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.141.126.202, 199.141.126.206, 2600:12f0:0:ac04::202, 2600:12f0:0:ac04::206, UDP_-_NOEDNS_)
edtmn.ovjyp.biopreferred.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
biopreferred.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
biopreferred.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
biopreferred.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
biopreferred.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (8)
biopreferred.gov/DS (alg 8, id 25579): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
biopreferred.gov/DS (alg 8, id 25579): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
biopreferred.gov/DS (alg 8, id 25579): 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.
biopreferred.gov/DS (alg 8, id 25579): 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.
edtmn.ovjyp.biopreferred.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
biopreferred.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
biopreferred.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
biopreferred.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.