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 (3)
  • army.mil/NS
  • army.mil/SOA
  • army.mil/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (15)
  • ./DNSKEY (alg 8, id 14631)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 42351)
  • army.mil/DNSKEY (alg 8, id 20994)
  • army.mil/DNSKEY (alg 8, id 30256)
  • army.mil/DNSKEY (alg 8, id 48396)
  • army.mil/DNSKEY (alg 8, id 53850)
  • army.mil/DNSKEY (alg 8, id 62140)
  • army.mil/DS (alg 8, id 62140)
  • army.mil/DS (alg 8, id 62140)
  • mil/DNSKEY (alg 8, id 11853)
  • mil/DNSKEY (alg 8, id 19128)
  • mil/DNSKEY (alg 8, id 51349)
  • mil/DS (alg 8, id 51349)
  • mil/DS (alg 8, id 51349)

Delegation statusDelegation status

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

NoticesNotices

Errors (19)
  • 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 48396: 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 48396: 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 48396: 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 48396: 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 62140: 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 62140: 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 62140: 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 62140: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • 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. (130.114.200.6, UDP_-_EDNS0_4096_D_KN)
  • army.mil/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • uqj60pr2iy.army.mil/A 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.
  • army.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • 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.
Warnings (14)
  • army.mil/DNSKEY (alg 8, id 53850): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (130.114.200.6, UDP_-_EDNS0_4096_D_KN)
  • army.mil/DS (alg 8, id 62140): 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 62140): 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 62140): 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 62140): 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): 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.
  • uqj60pr2iy.army.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • army.mil/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • army.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • army.mil/AAAA 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