data.gov
Updated:
2022-01-31 19:04:08 UTC (1026 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 (9)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 9799)
- data.gov/DNSKEY (alg 8, id 13171)
- data.gov/DNSKEY (alg 8, id 31294)
- data.gov/DS (alg 8, id 31294)
- data.gov/DS (alg 8, id 31294)
- 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 data.gov
Notices
Errors (5)
- gov/DS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (192.228.79.201, UDP_-_NOEDNS_)
- 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.
- ygserawz43.data.gov/A 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 31294): 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 31294): 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 31294): 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 31294): 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.
