View on GitHub

DNSViz: A DNS visualization tool

safecar.gov

DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Secure (6)
  • safecar.gov/A
  • safecar.gov/AAAA
  • safecar.gov/NS
  • safecar.gov/NSEC3PARAM
  • safecar.gov/SOA
  • safecar.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/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 statusDelegation status

Secure (2)
  • . to gov
  • gov to safecar.gov

NoticesNotices

Errors (3)
  • safecar.gov/CNAME 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.
  • rfg2uz0nxl.safecar.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (20)
  • 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/DNSKEY (alg 8, id 14686): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2001:19e8:d::200, 2001:19e8:d4::100, UDP_-_EDNS0_4096_D_KN)
  • safecar.gov/DNSKEY (alg 8, id 16998): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2001:19e8:d::200, 2001:19e8:d4::100, UDP_-_EDNS0_4096_D_KN)
  • safecar.gov/DNSKEY (alg 8, id 27300): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2001:19e8:d::200, 2001:19e8:d4::100, UDP_-_EDNS0_4096_D_KN)
  • safecar.gov/DNSKEY (alg 8, id 29371): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2001:19e8:d::200, 2001:19e8:d4::100, UDP_-_EDNS0_4096_D_KN)
  • safecar.gov/DNSKEY (alg 8, id 9903): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2001:19e8:d::200, 2001:19e8:d4::100, UDP_-_EDNS0_4096_D_KN)
  • 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.
  • safecar.gov/DNSKEY 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.
  • rfg2uz0nxl.safecar.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.

DNSKEY legend

Full legend
SEP bit setSEP bit set
Revoke bit setRevoke bit set
Trust anchorTrust anchor
Download: png | svg
Warning JavaScript is required to make the graph below interactive.
DNSSEC authentication graph