treasury.fed.us
Updated:
2022-02-24 02:56:49 UTC (1031 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (4)
- fed.us/SOA
- treasury.fed.us/NS
- treasury.fed.us/SOA
- treasury.fed.us/TXT
Secure (1)
- us/SOA
DNSKEY/DS/NSEC status
Secure (7)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 9799)
- NSEC3 proving non-existence of fed.us/DS
- us/DNSKEY (alg 8, id 21364)
- us/DNSKEY (alg 8, id 53985)
- us/DS (alg 8, id 21364)
- us/DS (alg 8, id 21364)
Delegation status
Insecure (2)
- fed.us to treasury.fed.us
- us to fed.us
Secure (1)
- . to us
Notices
Errors (16)
- NSEC3 proving non-existence of fed.us/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of fed.us/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- treasury.fed.us zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (166.123.208.249, 2610:108:4000:100a::249)
- treasury.fed.us zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (166.123.208.249, 2610:108:4000:100a::249)
- treasury.fed.us/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (166.123.208.249, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- treasury.fed.us/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (166.123.208.249, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_KN)
- treasury.fed.us/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (166.123.208.249, 2610:108:4000:100a::249, TCP_-_EDNS0_4096_D_N)
- treasury.fed.us/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (166.123.208.249, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- treasury.fed.us/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (166.123.208.249, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_KN)
- treasury.fed.us/A has errors; select the "Denial of existence" DNSSEC option to see them.
- treasury.fed.us/MX has errors; select the "Denial of existence" DNSSEC option to see them.
- treasury.fed.us/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- f3wq5x186s.treasury.fed.us/A has errors; select the "Denial of existence" DNSSEC option to see them.
- treasury.fed.us/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- treasury.fed.us/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- treasury.fed.us/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
- NSEC3 proving non-existence of fed.us/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of fed.us/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- fed.us to treasury.fed.us: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the fed.us zone): ceextauth1.treasury.gov See RFC 1034, Sec. 4.2.2.
- us/DS (alg 8, id 21364): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- us/DS (alg 8, id 21364): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- us/DS (alg 8, id 21364): 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.
- us/DS (alg 8, id 21364): 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.
JavaScript is required to make the graph below interactive.
