View on GitHub

DNSViz: A DNS visualization tool

northcom.mil

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

RRset statusRRset status

Secure (7)
  • northcom.mil/NS
  • northcom.mil/NSEC3PARAM
  • northcom.mil/NSEC3PARAM
  • northcom.mil/NSEC3PARAM
  • northcom.mil/NSEC3PARAM
  • northcom.mil/SOA
  • northcom.mil/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

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

Delegation statusDelegation status

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

NoticesNotices

Errors (6)
  • mil/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (199.252.143.234, UDP_-_EDNS0_512_D_KN)
  • northcom.mil/CNAME 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.
  • 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.
  • 4f31agqhko.northcom.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (13)
  • northcom.mil/DS (alg 8, id 4192): 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 4192): 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 4192): 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 4192): 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): 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.
  • northcom.mil/MX 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.
  • 4f31agqhko.northcom.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
Mouse over and click elements in the graph below to see more detail.
Created with Raphaël 2.1.2mil(2022-06-17 15:31:35 UTC)northcom.mil(2022-06-17 15:31:42 UTC).(2022-06-17 14:25:40 UTC)mil/DNSKEYDNSKEYalg=8, id=397481024 bitsDNSKEYalg=8, id=563472048 bitsDSdigest alg=2DNSKEYalg=8, id=516211024 bitsDSdigest algs=1,2DSdigest alg=2DSdigest alg=1northcom.mil/NSnorthcom.mil/SOAnorthcom.mil/NSEC3PARAMnorthcom.mil/NSEC3PARAMnorthcom.mil/NSEC3PARAMnorthcom.mil/NSEC3PARAMnorthcom.mil/TXTDNSKEYalg=8, id=602492048 bitsDNSKEYalg=8, id=41922048 bitsDNSKEYalg=8, id=49609DNSKEYalg=8, id=476712048 bitsDNSKEYalg=8, id=203262048 bits