treasurydirect.gov
Updated:
2020-11-12 13:17:47 UTC (1521 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (1)
- treasurydirect.gov/SOA
Secure (6)
- treasurydirect.gov/A
- treasurydirect.gov/AAAA
- treasurydirect.gov/MX
- treasurydirect.gov/NS
- treasurydirect.gov/SOA
- treasurydirect.gov/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26116)
- gov/DNSKEY (alg 8, id 15489)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- treasurydirect.gov/DNSKEY (alg 8, id 13269)
- treasurydirect.gov/DNSKEY (alg 8, id 44890)
- treasurydirect.gov/DS (alg 8, id 44890)
- treasurydirect.gov/DS (alg 8, id 44890)
Delegation status
Secure (2)
- . to gov
- gov to treasurydirect.gov
Notices
Errors (9)
- treasurydirect.gov/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (166.123.208.249, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_K)
- treasurydirect.gov/AAAA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (166.123.208.249, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_K)
- treasurydirect.gov/DNSKEY (alg 8, id 13269): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (166.123.208.249, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
- treasurydirect.gov/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (166.123.208.249, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
- treasurydirect.gov/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (166.123.208.249, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_K)
- treasurydirect.gov/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (166.123.208.249, 2610:108:4000:100a::249, TCP_-_EDNS0_4096_D, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
- treasurydirect.gov/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (166.123.208.249, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_K)
- ou5bstkl4a.treasurydirect.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- treasurydirect.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (10)
- 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.
- treasurydirect.gov/DS (alg 8, id 44890): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- treasurydirect.gov/DS (alg 8, id 44890): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- treasurydirect.gov/DS (alg 8, id 44890): 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.
- treasurydirect.gov/DS (alg 8, id 44890): 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.
- ou5bstkl4a.treasurydirect.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- treasurydirect.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
