safecar.gov
Updated:
2021-10-26 12:58:53 UTC (1122 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- safecar.gov/A
- safecar.gov/AAAA
- safecar.gov/NS
- safecar.gov/NSEC3PARAM
- safecar.gov/SOA
- safecar.gov/TXT
DNSKEY/DS/NSEC status
Secure (14)
- ./DNSKEY (alg 8, id 14748)
- ./DNSKEY (alg 8, id 20326)
- gov/DNSKEY (alg 8, id 6229)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- safecar.gov/DNSKEY (alg 8, id 14686)
- safecar.gov/DNSKEY (alg 8, id 16998)
- safecar.gov/DNSKEY (alg 8, id 27300)
- safecar.gov/DNSKEY (alg 8, id 29371)
- safecar.gov/DNSKEY (alg 8, id 9903)
- safecar.gov/DS (alg 8, id 14686)
- safecar.gov/DS (alg 8, id 14686)
- safecar.gov/DS (alg 8, id 29371)
- safecar.gov/DS (alg 8, id 29371)
Delegation status
Secure (2)
- . to gov
- gov to safecar.gov
Notices
Errors (6)
- safecar.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:19e8:d::100, 2001:19e8:d::200, 2001:19e8:d4::100)
- safecar.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:19e8:d::100, 2001:19e8:d::200, 2001:19e8:d4::100, UDP_-_NOEDNS_)
- safecar.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:19e8:d::100, 2001:19e8:d::200, 2001:19e8:d4::100, UDP_-_NOEDNS_)
- safecar.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- e51xdpiub3.safecar.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- safecar.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (14)
- gov to safecar.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 safecar.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 safecar.gov: Authoritative AAAA records exist for edns3.dot.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- safecar.gov/DS (alg 8, id 14686): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- safecar.gov/DS (alg 8, id 14686): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- safecar.gov/DS (alg 8, id 14686): 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.
- safecar.gov/DS (alg 8, id 14686): 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.
- safecar.gov/DS (alg 8, id 29371): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- safecar.gov/DS (alg 8, id 29371): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- safecar.gov/DS (alg 8, id 29371): 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.
- safecar.gov/DS (alg 8, id 29371): 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.
- safecar.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- e51xdpiub3.safecar.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- safecar.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
