View on GitHub

DNSViz: A DNS visualization tool

hpc.mil

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

RRset statusRRset status

Bogus (2)
  • hpc.mil/A
  • hpc.mil/NS

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (7)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46780)
  • hpc.mil/DS (alg 13, id 51716)
  • mil/DNSKEY (alg 8, id 16801)
  • mil/DNSKEY (alg 8, id 29343)
  • mil/DNSKEY (alg 8, id 51225)
  • mil/DS (alg 8, id 16801)
Non_existent (2)
  • hpc.mil/DNSKEY (alg 13, id 15771)
  • hpc.mil/DNSKEY (alg 13, id 51716)

Delegation statusDelegation status

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

NoticesNotices

Errors (17)
  • hpc.mil zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (140.32.59.226)
  • hpc.mil zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (140.32.45.226, 140.32.61.226, 2001:480:a0:f003::226, 2001:480:a1:f003::226, 2001:480:b0:f003::226)
  • hpc.mil/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (140.32.45.226, 140.32.61.226, 2001:480:a0:f003::226, 2001:480:a1:f003::226, 2001:480:b0:f003::226, UDP_-_NOEDNS_)
  • hpc.mil/AAAA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (140.32.59.226, UDP_-_NOEDNS_)
  • hpc.mil/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (140.32.59.226, UDP_-_NOEDNS_)
  • hpc.mil/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (140.32.59.226, UDP_-_EDNS0_512_D_KN)
  • hpc.mil/MX: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (140.32.59.226, UDP_-_NOEDNS_)
  • hpc.mil/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (140.32.59.226, UDP_-_EDNS0_512_D_KN)
  • hpc.mil/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (140.32.45.226, 140.32.61.226, 2001:480:a0:f003::226, 2001:480:a1:f003::226, 2001:480:b0:f003::226, UDP_-_NOEDNS_)
  • hpc.mil/NSEC3PARAM: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (140.32.59.226, UDP_-_NOEDNS_)
  • hpc.mil/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (140.32.59.226, TCP_-_EDNS0_4096_D_N)
  • hpc.mil/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (140.32.59.226, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • hpc.mil/TXT: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (140.32.59.226, UDP_-_NOEDNS_)
  • mil to hpc.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.
  • hpc.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • hpc.mil/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • 0287pnehgo.hpc.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
  • hpc.mil/DS (alg 13, id 51716): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • hpc.mil/DS (alg 13, id 51716): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • hpc.mil/DS (alg 13, id 51716): 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.
  • hpc.mil/DS (alg 13, id 51716): 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 to hpc.mil: AAAA glue records exist for auth-west.dren.mil, but there are no corresponding authoritative AAAA records. See RFC 1034, Sec. 4.2.2.
  • mil to hpc.mil: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the mil zone): auth-sandiego.dren.mil, auth-wpafb.dren.mil See RFC 1034, Sec. 4.2.2.
  • mil to hpc.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: auth-east.dren.mil, auth-west.dren.mil See RFC 1034, Sec. 4.2.2.

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