View on GitHub

DNSViz: A DNS visualization tool

veterans.gov

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

RRset statusRRset status

Secure (5)
  • veterans.gov/A
  • veterans.gov/AAAA
  • veterans.gov/NS
  • veterans.gov/SOA
  • veterans.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (10)
  • ./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)
  • veterans.gov/DNSKEY (alg 8, id 46609)
  • veterans.gov/DNSKEY (alg 8, id 60934)
  • veterans.gov/DS (alg 8, id 60934)
  • veterans.gov/DS (alg 8, id 60934)

Delegation statusDelegation status

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

NoticesNotices

Errors (6)
  • veterans.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2607:f250:d024:3001:152:180:20:20)
  • veterans.gov/A: There was an error communicating with the server over UDP (EACCES). See RFC 1035, Sec. 4.2. (2607:f250:d024:3001:152:180:20:20, UDP_-_EDNS0_4096_D_K)
  • veterans.gov/NS: There was an error communicating with the server over UDP (EACCES). See RFC 1035, Sec. 4.2. (2607:f250:d024:3001:152:180:20:20, UDP_-_EDNS0_4096_D_K)
  • veterans.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • veterans.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • vfuhrbkj0m.veterans.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (19)
  • gov to veterans.gov: Authoritative AAAA records exist for ns05.dol.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • gov to veterans.gov: Authoritative AAAA records exist for ns06.dol.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • gov to veterans.gov: Authoritative AAAA records exist for stlns08.dol.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.
  • veterans.gov/A: 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. (152.180.11.239, UDP_-_EDNS0_4096_D_K)
  • veterans.gov/AAAA: 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. (152.180.11.239, UDP_-_EDNS0_4096_D_K)
  • veterans.gov/DS (alg 8, id 60934): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • veterans.gov/DS (alg 8, id 60934): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • veterans.gov/DS (alg 8, id 60934): 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.
  • veterans.gov/DS (alg 8, id 60934): 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.
  • veterans.gov/NS: 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. (152.180.11.239, UDP_-_EDNS0_4096_D_K)
  • veterans.gov/SOA: 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. (152.180.11.239, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
  • veterans.gov/TXT: 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. (152.180.11.239, UDP_-_EDNS0_4096_D_K)
  • veterans.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • veterans.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • vfuhrbkj0m.veterans.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