data.gov
Updated:
2021-09-23 14:26:41 UTC (1157 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- data.gov/A
- data.gov/NS
- data.gov/NSEC3PARAM
- data.gov/SOA
- data.gov/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 14748)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26838)
- data.gov/DNSKEY (alg 8, id 47650)
- data.gov/DNSKEY (alg 8, id 62308)
- data.gov/DS (alg 8, id 47650)
- data.gov/DS (alg 8, id 47650)
- gov/DNSKEY (alg 8, id 57735)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Delegation status
Secure (2)
- . to gov
- gov to data.gov
Notices
Errors (4)
- h5dkaoj4es.data.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- data.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- data.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
- data.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
- data.gov/DS (alg 8, id 47650): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- data.gov/DS (alg 8, id 47650): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- data.gov/DS (alg 8, id 47650): 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.
- data.gov/DS (alg 8, id 47650): 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.
