View on GitHub

DNSViz: A DNS visualization tool

dma.mil

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

RRset statusRRset status

Bogus (6)
  • dma.mil/MX
  • dma.mil/NS
  • dma.mil/NS
  • dma.mil/NSEC3PARAM
  • dma.mil/SOA
  • dma.mil/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (4)
  • dma.mil/DNSKEY (alg 8, id 27328)
  • dma.mil/DNSKEY (alg 8, id 48401)
  • dma.mil/DNSKEY (alg 8, id 54154)
  • dma.mil/DNSKEY (alg 8, id 59159)
Secure (8)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 30903)
  • dma.mil/DS (alg 8, id 59159)
  • dma.mil/DS (alg 8, id 59159)
  • mil/DNSKEY (alg 8, id 16801)
  • mil/DNSKEY (alg 8, id 49404)
  • mil/DNSKEY (alg 8, id 51706)
  • mil/DS (alg 8, id 16801)

Delegation statusDelegation status

Bogus (1)
  • mil to dma.mil
Secure (1)
  • . to mil

NoticesNotices

Errors (22)
  • dma.mil zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2608:164:15:503::c, 2608:164:15:503::d)
  • dma.mil/DNSKEY (alg 8, id 27328): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (155.7.145.112, 155.7.145.113, 155.7.208.112, 155.7.208.113, TCP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN)
  • dma.mil/DNSKEY (alg 8, id 48401): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (155.7.145.112, 155.7.145.113, 155.7.208.112, 155.7.208.113, TCP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN)
  • dma.mil/DNSKEY (alg 8, id 54154): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (155.7.145.112, 155.7.145.113, 155.7.208.112, 155.7.208.113, TCP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN)
  • dma.mil/DNSKEY (alg 8, id 59159): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (155.7.145.112, 155.7.145.113, 155.7.208.112, 155.7.208.113, TCP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN)
  • dma.mil/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (155.7.208.113, UDP_-_EDNS0_512_D_KN)
  • dma.mil/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (155.7.145.112, 155.7.145.113, 155.7.208.112, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • dma.mil/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (155.7.208.112, UDP_-_EDNS0_512_D_KN)
  • dma.mil/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (155.7.145.112, 155.7.145.113, 155.7.208.112, UDP_-_EDNS0_4096_D_KN)
  • dma.mil/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (155.7.208.113, UDP_-_EDNS0_4096_D_KN)
  • dma.mil/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2608:164:15:503::c, 2608:164:15:503::d, UDP_-_NOEDNS_)
  • dma.mil/NSEC3PARAM: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (155.7.145.113, 155.7.208.112, 155.7.208.113, UDP_-_EDNS0_4096_D_KN)
  • dma.mil/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (155.7.145.112, 155.7.145.113, 155.7.208.112, 155.7.208.113, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • dma.mil/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (155.7.145.112, 155.7.145.113, 155.7.208.112, 155.7.208.113, UDP_-_EDNS0_4096_D_KN)
  • mil to dma.mil: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (155.7.145.112, 155.7.145.113, 155.7.208.112, 155.7.208.113, TCP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN)
  • mil to dma.mil: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (155.7.145.112, 155.7.145.113, 155.7.208.112, 155.7.208.113, TCP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN)
  • mil/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (199.252.154.234, 199.252.155.234, UDP_-_EDNS0_512_D_KN)
  • dma.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • dma.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • dma.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • xosq0bad1c.dma.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • dma.mil/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (16)
  • dma.mil/DNSKEY (alg 8, id 27328): 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. (155.7.145.113, 155.7.208.112, UDP_-_EDNS0_4096_D_KN)
  • dma.mil/DNSKEY (alg 8, id 48401): 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. (155.7.145.113, 155.7.208.112, UDP_-_EDNS0_4096_D_KN)
  • dma.mil/DNSKEY (alg 8, id 54154): 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. (155.7.145.113, 155.7.208.112, UDP_-_EDNS0_4096_D_KN)
  • dma.mil/DNSKEY (alg 8, id 59159): 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. (155.7.145.113, 155.7.208.112, UDP_-_EDNS0_4096_D_KN)
  • dma.mil/DS (alg 8, id 59159): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • dma.mil/DS (alg 8, id 59159): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • dma.mil/DS (alg 8, id 59159): 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.
  • dma.mil/DS (alg 8, id 59159): 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.
  • dma.mil/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. (155.7.208.112, UDP_-_EDNS0_4096_D_KN)
  • mil to dma.mil: Authoritative AAAA records exist for kaucher.dma.mil, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • mil to dma.mil: Authoritative AAAA records exist for russell.dma.mil, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • mil to dma.mil: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the mil zone): beast.dma.mil, beauty.dma.mil See RFC 1034, Sec. 4.2.2.
  • mil to dma.mil: The glue address(es) for beauty-1.dma.mil (155.7.145.113) differed from its authoritative address(es) (155.7.145.112). See RFC 1034, Sec. 4.2.2.
  • dma.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • xosq0bad1c.dma.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • dma.mil/DNSKEY 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