View on GitHub

DNSViz: A DNS visualization tool

army.mil

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

RRset statusRRset status

Secure (7)
  • army.mil/A
  • army.mil/AAAA
  • army.mil/NS
  • army.mil/SOA
  • army.mil/SOA
  • army.mil/SOA
  • army.mil/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (13)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46594)
  • army.mil/DNSKEY (alg 8, id 23943)
  • army.mil/DNSKEY (alg 8, id 30256)
  • army.mil/DNSKEY (alg 8, id 49608)
  • army.mil/DNSKEY (alg 8, id 61578)
  • army.mil/DS (alg 8, id 30256)
  • army.mil/DS (alg 8, id 30256)
  • mil/DNSKEY (alg 8, id 15684)
  • mil/DNSKEY (alg 8, id 4983)
  • mil/DNSKEY (alg 8, id 7765)
  • mil/DS (alg 8, id 7765)
  • mil/DS (alg 8, id 7765)

Delegation statusDelegation status

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

NoticesNotices

Errors (22)
  • RRSIG army.mil/DNSKEY alg 8, id 30256: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG army.mil/DNSKEY alg 8, id 30256: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG army.mil/DNSKEY alg 8, id 30256: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG army.mil/DNSKEY alg 8, id 30256: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG army.mil/DNSKEY alg 8, id 61578: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG army.mil/DNSKEY alg 8, id 61578: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG army.mil/DNSKEY alg 8, id 61578: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG army.mil/DNSKEY alg 8, id 61578: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • army.mil zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (130.114.200.6)
  • army.mil zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (130.114.200.6)
  • army.mil/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (130.114.200.6, UDP_-_EDNS0_4096_D_K)
  • army.mil/AAAA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (130.114.200.6, UDP_-_EDNS0_4096_D_K)
  • army.mil/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (130.114.200.6, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • army.mil/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (130.114.200.6, UDP_-_EDNS0_4096_D_K)
  • army.mil/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (130.114.200.6, TCP_-_EDNS0_4096_D)
  • army.mil/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (130.114.200.6, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
  • army.mil/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (130.114.200.6, UDP_-_EDNS0_4096_D_K)
  • mil to army.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. (140.153.43.44, UDP_-_EDNS0_4096_D_K)
  • army.mil/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • 2cws75nqr9.army.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • army.mil/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • army.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (10)
  • army.mil/DS (alg 8, id 30256): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • army.mil/DS (alg 8, id 30256): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • army.mil/DS (alg 8, id 30256): 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.
  • army.mil/DS (alg 8, id 30256): 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 7765): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • mil/DS (alg 8, id 7765): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • mil/DS (alg 8, id 7765): 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 7765): 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.
  • army.mil/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • army.mil/CNAME 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