treasury.gov/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (164.95.95.155, 2610:108:3000:100a::155, UDP_-_EDNS0_4096_D_K)
treasury.gov/AAAA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (164.95.95.155, 2610:108:3000:100a::155, UDP_-_EDNS0_4096_D_K)
treasury.gov/DNSKEY (alg 7, id 4037): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (164.95.95.155, 2610:108:3000:100a::155, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
treasury.gov/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (164.95.95.155, 2610:108:3000:100a::155, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
treasury.gov/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (164.95.95.155, 2610:108:3000:100a::155, UDP_-_EDNS0_4096_D_K)
treasury.gov/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (164.95.95.155, 2610:108:3000:100a::155, TCP_-_EDNS0_4096_D, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
treasury.gov/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (164.95.95.155, 2610:108:3000:100a::155, UDP_-_EDNS0_4096_D_K)
3z9ykpx1f6.treasury.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
treasury.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (35)
RRSIG treasury.gov/A alg 7, id 4037: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG treasury.gov/A alg 7, id 4037: The value of the Signature Inception field of the RRSIG RR (2020-11-04 08:42:15+00:00) is within possible clock skew range (41 seconds) of the current time (2020-11-04 08:42:56+00:00). See RFC 4035, Sec. 5.3.1.
RRSIG treasury.gov/AAAA alg 7, id 4037: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG treasury.gov/AAAA alg 7, id 4037: The value of the Signature Inception field of the RRSIG RR (2020-11-04 08:42:15+00:00) is within possible clock skew range (41 seconds) of the current time (2020-11-04 08:42:56+00:00). See RFC 4035, Sec. 5.3.1.
RRSIG treasury.gov/DNSKEY alg 7, id 37335: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG treasury.gov/DNSKEY alg 7, id 37335: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG treasury.gov/DNSKEY alg 7, id 37335: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG treasury.gov/DNSKEY alg 7, id 37335: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG treasury.gov/DNSKEY alg 7, id 37335: The value of the Signature Inception field of the RRSIG RR (2020-11-04 08:42:15+00:00) is within possible clock skew range (41 seconds) of the current time (2020-11-04 08:42:56+00:00). See RFC 4035, Sec. 5.3.1.
RRSIG treasury.gov/DNSKEY alg 7, id 37335: The value of the Signature Inception field of the RRSIG RR (2020-11-04 08:42:15+00:00) is within possible clock skew range (41 seconds) of the current time (2020-11-04 08:42:56+00:00). See RFC 4035, Sec. 5.3.1.
RRSIG treasury.gov/DNSKEY alg 7, id 4037: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG treasury.gov/DNSKEY alg 7, id 4037: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG treasury.gov/DNSKEY alg 7, id 4037: The value of the Signature Inception field of the RRSIG RR (2020-11-04 08:42:15+00:00) is within possible clock skew range (41 seconds) of the current time (2020-11-04 08:42:56+00:00). See RFC 4035, Sec. 5.3.1.
RRSIG treasury.gov/DNSKEY alg 7, id 4037: The value of the Signature Inception field of the RRSIG RR (2020-11-04 08:42:15+00:00) is within possible clock skew range (41 seconds) of the current time (2020-11-04 08:42:56+00:00). See RFC 4035, Sec. 5.3.1.
RRSIG treasury.gov/MX alg 7, id 4037: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG treasury.gov/MX alg 7, id 4037: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG treasury.gov/MX alg 7, id 4037: The value of the Signature Inception field of the RRSIG RR (2020-11-04 08:42:17+00:00) is within possible clock skew range (39 seconds) of the current time (2020-11-04 08:42:56+00:00). See RFC 4035, Sec. 5.3.1.
RRSIG treasury.gov/MX alg 7, id 4037: The value of the Signature Inception field of the RRSIG RR (2020-11-04 08:42:19+00:00) is within possible clock skew range (37 seconds) of the current time (2020-11-04 08:42:56+00:00). See RFC 4035, Sec. 5.3.1.
RRSIG treasury.gov/NS alg 7, id 4037: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG treasury.gov/NS alg 7, id 4037: The value of the Signature Inception field of the RRSIG RR (2020-11-04 08:42:15+00:00) is within possible clock skew range (41 seconds) of the current time (2020-11-04 08:42:56+00:00). See RFC 4035, Sec. 5.3.1.
RRSIG treasury.gov/SOA alg 7, id 4037: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG treasury.gov/SOA alg 7, id 4037: The value of the Signature Inception field of the RRSIG RR (2020-11-04 08:42:15+00:00) is within possible clock skew range (41 seconds) of the current time (2020-11-04 08:42:56+00:00). See RFC 4035, Sec. 5.3.1.
RRSIG treasury.gov/TXT alg 7, id 4037: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG treasury.gov/TXT alg 7, id 4037: The value of the Signature Inception field of the RRSIG RR (2020-11-04 08:42:28+00:00) is within possible clock skew range (28 seconds) of the current time (2020-11-04 08:42:56+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.
treasury.gov/DS (alg 7, id 37335): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
treasury.gov/DS (alg 7, id 37335): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
treasury.gov/DS (alg 7, id 37335): 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.
treasury.gov/DS (alg 7, id 37335): 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.
treasury.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
3z9ykpx1f6.treasury.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
treasury.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.