dot.gov
Updated:
2021-10-28 01:00:13 UTC (1124 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- dot.gov/A
- dot.gov/MX
- dot.gov/NS
- dot.gov/NSEC3PARAM
- dot.gov/SOA
- dot.gov/TXT
DNSKEY/DS/NSEC status
Secure (11)
- ./DNSKEY (alg 8, id 14748)
- ./DNSKEY (alg 8, id 20326)
- dot.gov/DNSKEY (alg 8, id 35556)
- dot.gov/DNSKEY (alg 8, id 41838)
- dot.gov/DNSKEY (alg 8, id 47748)
- dot.gov/DNSKEY (alg 8, id 49516)
- dot.gov/DS (alg 8, id 49516)
- dot.gov/DS (alg 8, id 49516)
- gov/DNSKEY (alg 8, id 6229)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Delegation status
Secure (2)
- . to gov
- gov to dot.gov
Notices
Errors (3)
- dot.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- 8kjthv7c14.dot.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- dot.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
- dot.gov/DS (alg 8, id 49516): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- dot.gov/DS (alg 8, id 49516): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- dot.gov/DS (alg 8, id 49516): 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.
- dot.gov/DS (alg 8, id 49516): 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.
- dot.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- 8kjthv7c14.dot.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- dot.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
