us.gov
Updated:
2022-12-04 05:37:46 UTC (720 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- us.gov/A
- us.gov/AAAA
- us.gov/NS
- us.gov/NSEC3PARAM
- us.gov/SOA
- us.gov/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 18733)
- ./DNSKEY (alg 8, id 20326)
- gov/DNSKEY (alg 8, id 56278)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- us.gov/DNSKEY (alg 8, id 31936)
- us.gov/DNSKEY (alg 8, id 55327)
- us.gov/DNSKEY (alg 8, id 59796)
- us.gov/DS (alg 8, id 55327)
- us.gov/DS (alg 8, id 55327)
Delegation status
Secure (2)
- . to gov
- gov to us.gov
Notices
Errors (3)
- us.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- us.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
- c2jnbirsmd.us.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
- us.gov/DS (alg 8, id 55327): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- us.gov/DS (alg 8, id 55327): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- us.gov/DS (alg 8, id 55327): 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.gov/DS (alg 8, id 55327): 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.
