nhtsa.gov
Updated:
2020-11-21 20:17:11 UTC (1461 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (4)
- nhtsa.gov/A
- nhtsa.gov/NS
- nhtsa.gov/SOA
- nhtsa.gov/TXT
DNSKEY/DS/NSEC status
Secure (12)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26116)
- gov/DNSKEY (alg 8, id 15489)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- nhtsa.gov/DNSKEY (alg 8, id 24904)
- nhtsa.gov/DNSKEY (alg 8, id 29568)
- nhtsa.gov/DNSKEY (alg 8, id 55023)
- nhtsa.gov/DS (alg 8, id 24904)
- nhtsa.gov/DS (alg 8, id 24904)
- nhtsa.gov/DS (alg 8, id 9025)
Non_existent (1)
- nhtsa.gov/DNSKEY (alg 8, id 9025)
Delegation status
Secure (2)
- . to gov
- gov to nhtsa.gov
Notices
Errors (4)
- nhtsa.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
- rtw12b5eg9.nhtsa.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- nhtsa.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- nhtsa.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (19)
- gov to nhtsa.gov: Authoritative AAAA records exist for edns1.dot.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- gov to nhtsa.gov: Authoritative AAAA records exist for edns2.dot.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- gov to nhtsa.gov: Authoritative AAAA records exist for edns3.dot.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- gov/DS (alg 8, id 7698): 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.
- gov/DS (alg 8, id 7698): 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.
- nhtsa.gov/DS (alg 8, id 24904): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- nhtsa.gov/DS (alg 8, id 24904): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- nhtsa.gov/DS (alg 8, id 24904): 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.
- nhtsa.gov/DS (alg 8, id 24904): 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.
- nhtsa.gov/DS (alg 8, id 9025): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- nhtsa.gov/DS (alg 8, id 9025): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- nhtsa.gov/DS (alg 8, id 9025): 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.
- nhtsa.gov/DS (alg 8, id 9025): 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.
- nhtsa.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
- rtw12b5eg9.nhtsa.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- nhtsa.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- nhtsa.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
