treasury.fed.us
Updated:
2022-02-25 07:56:16 UTC (1035 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (2)
- fed.us/SOA
- treasury.fed.us/A (NXDOMAIN)
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 (1)
- us to fed.us
Secure (1)
- . to us
Notices
Errors (2)
- 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.
Warnings (6)
- 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.
- 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.
