View on GitHub

DNSViz: A DNS visualization tool

northcom.mil

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

RRset statusRRset status

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

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (2)
  • northcom.mil/DNSKEY (alg 8, id 4192)
  • northcom.mil/DNSKEY (alg 8, id 60249)
Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 47671)
  • mil/DNSKEY (alg 8, id 39748)
  • mil/DNSKEY (alg 8, id 56347)
  • mil/DS (alg 8, id 56347)
  • northcom.mil/DS (alg 8, id 49609)
Non_existent (1)
  • northcom.mil/DNSKEY (alg 8, id 49609)

Delegation statusDelegation status

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

NoticesNotices

Errors (7)
  • mil to northcom.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. (164.236.0.19, 164.236.0.20, 164.236.160.19, 164.236.160.20, UDP_-_EDNS0_4096_D_KN)
  • mil to northcom.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. (164.236.0.19, 164.236.0.20, 164.236.160.19, 164.236.160.20, UDP_-_EDNS0_4096_D_KN)
  • northcom.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • w2o98ql3d7.northcom.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • northcom.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • northcom.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • northcom.mil/MX has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (9)
  • northcom.mil/DS (alg 8, id 49609): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • northcom.mil/DS (alg 8, id 49609): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • northcom.mil/DS (alg 8, id 49609): 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.
  • northcom.mil/DS (alg 8, id 49609): 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.
  • northcom.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • w2o98ql3d7.northcom.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • northcom.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • northcom.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • northcom.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