View on GitHub

DNSViz: A DNS visualization tool

norad.mil

Updated: 2024-04-21 17:17:37 UTC (244 days ago) Update now
« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Bogus (2)
  • norad.mil/NS
  • norad.mil/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (2)
  • norad.mil/DNSKEY (alg 8, id 47095)
  • norad.mil/DNSKEY (alg 8, id 6543)
Secure (7)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 5613)
  • mil/DNSKEY (alg 8, id 16801)
  • mil/DNSKEY (alg 8, id 25501)
  • mil/DNSKEY (alg 8, id 45154)
  • mil/DS (alg 8, id 16801)
  • norad.mil/DS (alg 8, id 62866)
Non_existent (1)
  • norad.mil/DNSKEY (alg 8, id 62866)

Delegation statusDelegation status

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

NoticesNotices

Errors (11)
  • mil to norad.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 norad.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)
  • mil zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2608:120:c:162::234, 2608:140:c:157::234, 2608:4163:1:143::234, 2608:c144:1:155::234, 2608:c184:1:180::234)
  • norad.mil/NSEC3PARAM: No response was received from the server over UDP (tried 13 times). See RFC 1035, Sec. 4.2. (164.236.160.19, UDP_-_NOEDNS_)
  • norad.mil/NSEC3PARAM: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (164.236.0.19, 164.236.0.20, 164.236.160.20, UDP_-_NOEDNS_)
  • norad.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • norad.mil/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • norad.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • norad.mil/TXT has errors; select the "Denial of existence" DNSSEC option to see them.
  • norad.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • xufekmqag3.norad.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (10)
  • norad.mil/DS (alg 8, id 62866): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • norad.mil/DS (alg 8, id 62866): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • norad.mil/DS (alg 8, id 62866): 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.
  • norad.mil/DS (alg 8, id 62866): 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.
  • norad.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • norad.mil/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • norad.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • norad.mil/TXT has warnings; select the "Denial of existence" DNSSEC option to see them.
  • norad.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • xufekmqag3.norad.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
Warning JavaScript is required to make the graph below interactive.
DNSSEC authentication graph