View on GitHub

DNSViz: A DNS visualization tool

usfj.mil

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

RRset statusRRset status

Bogus (3)
  • usfj.mil/NS
  • usfj.mil/SOA
  • usfj.mil/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (4)
  • usfj.mil/DNSKEY (alg 8, id 14407)
  • usfj.mil/DNSKEY (alg 8, id 32869)
  • usfj.mil/DNSKEY (alg 8, id 53116)
  • usfj.mil/DNSKEY (alg 8, id 9982)
Secure (9)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26116)
  • mil/DNSKEY (alg 8, id 24363)
  • mil/DNSKEY (alg 8, id 35118)
  • mil/DNSKEY (alg 8, id 51349)
  • mil/DS (alg 8, id 51349)
  • mil/DS (alg 8, id 51349)
  • usfj.mil/DS (alg 8, id 9982)
  • usfj.mil/DS (alg 8, id 9982)

Delegation statusDelegation status

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

NoticesNotices

Errors (18)
  • mil to usfj.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. (205.56.181.106, 205.56.181.107, UDP_-_EDNS0_4096_D_K)
  • mil to usfj.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. (205.56.181.106, 205.56.181.107, UDP_-_EDNS0_4096_D_K)
  • mil zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (199.252.162.234)
  • mil zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (199.252.162.234)
  • mil zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (199.252.154.234, 199.252.180.234)
  • mil/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.252.157.234, UDP_-_NOEDNS_)
  • mil/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (199.252.157.234, 199.252.162.234, UDP_-_EDNS0_512_D_K)
  • mil/DNSKEY: No response was received from the server over UDP (tried 8 times). See RFC 1035, Sec. 4.2. (199.252.162.234, UDP_-_EDNS0_4096_D)
  • usfj.mil zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (199.211.150.67)
  • usfj.mil/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.211.150.66, UDP_-_NOEDNS_)
  • usfj.mil/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.211.150.67, UDP_-_NOEDNS_)
  • usfj.mil/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.211.150.66, UDP_-_NOEDNS__0x20)
  • usfj.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • usfj.mil/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • usfj.mil/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • usfj.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • usfj.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • 1s7cbogn4m.usfj.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (19)
  • mil to usfj.mil: The following NS name(s) were found in the delegation NS RRset (i.e., in the mil zone), but not in the authoritative NS RRset: pnocxns1.pr.navy.mil, pnocxns2.pr.navy.mil See RFC 1034, Sec. 4.2.2.
  • mil/DS (alg 8, id 51349): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • mil/DS (alg 8, id 51349): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • mil/DS (alg 8, id 51349): 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.
  • mil/DS (alg 8, id 51349): 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.
  • usfj.mil/DS (alg 8, id 9982): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • usfj.mil/DS (alg 8, id 9982): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • usfj.mil/DS (alg 8, id 9982): 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.
  • usfj.mil/DS (alg 8, id 9982): 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.
  • usfj.mil/DS (alg 8, id 9982): 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. (199.252.162.234, UDP_-_EDNS0_4096_D_K)
  • usfj.mil/DS (alg 8, id 9982): 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. (199.252.162.234, UDP_-_EDNS0_4096_D_K)
  • usfj.mil/DS (alg 8, id 9982): 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. (199.252.162.234, UDP_-_EDNS0_4096_D_K)
  • usfj.mil/DS (alg 8, id 9982): 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. (199.252.162.234, UDP_-_EDNS0_4096_D_K)
  • usfj.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • usfj.mil/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • usfj.mil/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • usfj.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • usfj.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 1s7cbogn4m.usfj.mil/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