dotgov.gov
Updated:
2022-01-11 17:38:54 UTC (1048 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (7)
- dotgov.gov/A
- dotgov.gov/AAAA
- dotgov.gov/MX
- dotgov.gov/NS
- dotgov.gov/NSEC3PARAM
- dotgov.gov/SOA
- dotgov.gov/TXT
DNSKEY/DS/NSEC status
Secure (12)
- ./DNSKEY (alg 8, id 14748)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 9799)
- dotgov.gov/DNSKEY (alg 8, id 53938)
- dotgov.gov/DNSKEY (alg 8, id 6408)
- dotgov.gov/DNSKEY (alg 8, id 9549)
- dotgov.gov/DS (alg 8, id 9549)
- dotgov.gov/DS (alg 8, id 9549)
- gov/DNSKEY (alg 8, id 6229)
- gov/DNSKEY (alg 8, id 7030)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Delegation status
Secure (2)
- . to gov
- gov to dotgov.gov
Notices
Errors (2)
- 4bo0cl8gqi.dotgov.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- dotgov.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (6)
- dotgov.gov/DS (alg 8, id 9549): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- dotgov.gov/DS (alg 8, id 9549): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- dotgov.gov/DS (alg 8, id 9549): 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.
- dotgov.gov/DS (alg 8, id 9549): 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.
- 4bo0cl8gqi.dotgov.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- dotgov.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
