treasuryauctions.gov/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (164.95.95.155, 166.123.208.249, 2610:108:3000:100a::155, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_K)
treasuryauctions.gov/AAAA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (164.95.95.155, 166.123.208.249, 2610:108:3000:100a::155, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_K)
treasuryauctions.gov/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (164.95.95.155, 166.123.208.249, 2610:108:3000:100a::155, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
treasuryauctions.gov/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (164.95.95.155, 166.123.208.249, 2610:108:3000:100a::155, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_K)
treasuryauctions.gov/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (164.95.95.155, 166.123.208.249, 2610:108:3000:100a::155, 2610:108:4000:100a::249, TCP_-_EDNS0_4096_D, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
treasuryauctions.gov/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (164.95.95.155, 166.123.208.249, 2610:108:3000:100a::155, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_K)
5wl3u0c1rx.treasuryauctions.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
treasuryauctions.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (10)
RRSIG treasuryauctions.gov/DNSKEY alg 8, id 46786: The value of the Signature Inception field of the RRSIG RR (2020-11-04 07:05:49+00:00) is within possible clock skew range (0 seconds) of the current time (2020-11-04 07:05:49+00:00). See RFC 4035, Sec. 5.3.1.
gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
gov/DS (alg 8, id 7698): 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.
gov/DS (alg 8, id 7698): 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.
treasuryauctions.gov/DS (alg 8, id 46786): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
treasuryauctions.gov/DS (alg 8, id 46786): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
treasuryauctions.gov/DS (alg 8, id 46786): 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.
treasuryauctions.gov/DS (alg 8, id 46786): 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.
treasuryauctions.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.