View on GitHub

DNSViz: A DNS visualization tool

eucom.mil

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

RRset statusRRset status

Bogus (4)
  • eucom.mil/NS (NODATA)
  • eucom.mil/NSEC3PARAM (NODATA)
  • eucom.mil/SOA (NODATA)
  • eucom.mil/TXT (NODATA)
Secure (4)
  • eucom.mil/NS
  • eucom.mil/NSEC3PARAM
  • eucom.mil/SOA
  • eucom.mil/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (11)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 61050)
  • eucom.mil/DNSKEY (alg 8, id 16755)
  • eucom.mil/DNSKEY (alg 8, id 31684)
  • eucom.mil/DNSKEY (alg 8, id 54693)
  • eucom.mil/DS (alg 8, id 31684)
  • eucom.mil/DS (alg 8, id 31684)
  • mil/DNSKEY (alg 8, id 20335)
  • mil/DNSKEY (alg 8, id 26770)
  • mil/DNSKEY (alg 8, id 63500)
  • mil/DS (alg 8, id 63500)

Delegation statusDelegation status

Secure (2)
  • . to mil
  • mil to eucom.mil

NoticesNotices

Errors (28)
  • eucom.mil zone: The server(s) did not respond authoritatively for the namespace. See RFC 1035, Sec. 4.1.1. (215.76.62.40, 215.76.62.41)
  • eucom.mil/DNSKEY (alg 8, id 16755): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (215.76.62.40, 215.76.62.41, UDP_-_EDNS0_4096_D_KN)
  • eucom.mil/DNSKEY (alg 8, id 31684): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (215.76.62.40, 215.76.62.41, UDP_-_EDNS0_4096_D_KN)
  • eucom.mil/DNSKEY (alg 8, id 54693): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (215.76.62.40, 215.76.62.41, UDP_-_EDNS0_4096_D_KN)
  • eucom.mil/NS (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (215.76.62.40, 215.76.62.41, UDP_-_EDNS0_4096_D_KN)
  • eucom.mil/NS (NODATA): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (215.76.62.40, UDP_-_EDNS0_4096_D_KN)
  • eucom.mil/NS (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (215.76.62.40, UDP_-_EDNS0_4096_D_KN)
  • eucom.mil/NS (NODATA): The response was an upward referral. See https://www.dns-oarc.net/oarc/articles/upward-referrals-considered-harmful. (215.76.62.41, UDP_-_EDNS0_4096_D_KN)
  • eucom.mil/NSEC3PARAM (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (215.76.62.40, UDP_-_EDNS0_4096_D_KN)
  • eucom.mil/NSEC3PARAM (NODATA): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (215.76.62.40, UDP_-_EDNS0_4096_D_KN)
  • eucom.mil/NSEC3PARAM (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (215.76.62.40, UDP_-_EDNS0_4096_D_KN)
  • eucom.mil/NSEC3PARAM: The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (215.76.62.41, UDP_-_EDNS0_4096_D_KN)
  • eucom.mil/SOA (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (215.76.62.40, 215.76.62.41, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • eucom.mil/SOA (NODATA): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (215.76.62.40, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • eucom.mil/SOA (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (215.76.62.40, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • eucom.mil/SOA (NODATA): The response was an upward referral. See https://www.dns-oarc.net/oarc/articles/upward-referrals-considered-harmful. (215.76.62.41, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • eucom.mil/TXT (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (215.76.62.40, 215.76.62.41, UDP_-_EDNS0_4096_D_KN)
  • eucom.mil/TXT (NODATA): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (215.76.62.40, UDP_-_EDNS0_4096_D_KN)
  • eucom.mil/TXT (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (215.76.62.40, UDP_-_EDNS0_4096_D_KN)
  • eucom.mil/TXT (NODATA): The response was an upward referral. See https://www.dns-oarc.net/oarc/articles/upward-referrals-considered-harmful. (215.76.62.41, UDP_-_EDNS0_4096_D_KN)
  • eucom.mil/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • jr2wi.yor7g.eucom.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • eucom.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • eucom.mil/CDNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • eucom.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • eucom.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • eucom.mil/CDS has errors; select the "Denial of existence" DNSSEC option to see them.
  • eucom.mil/MX has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (14)
  • ./DNSKEY: The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_512_D_KN)
  • eucom.mil/DNSKEY: The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (215.76.62.40, 215.76.62.41, UDP_-_EDNS0_512_D_KN)
  • eucom.mil/DS (alg 8, id 31684): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • eucom.mil/DS (alg 8, id 31684): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • eucom.mil/DS (alg 8, id 31684): 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.
  • eucom.mil/DS (alg 8, id 31684): 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.
  • eucom.mil/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • jr2wi.yor7g.eucom.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • eucom.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • eucom.mil/CDNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • eucom.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • eucom.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • eucom.mil/CDS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • eucom.mil/MX 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