View on GitHub

DNSViz: A DNS visualization tool

mojavedata.gov

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

RRset statusRRset status

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (8)
  • ./DNSKEY (alg 8, id 18733)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 20826)
  • gov/DNSKEY (alg 8, id 261)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • mojavedata.gov/DS (alg 8, id 17431)
  • mojavedata.gov/DS (alg 8, id 8209)
Non_existent (2)
  • mojavedata.gov/DNSKEY (alg 8, id 17431)
  • mojavedata.gov/DNSKEY (alg 8, id 8209)

Delegation statusDelegation status

Bogus (1)
  • gov to mojavedata.gov
Secure (1)
  • . to gov

NoticesNotices

Errors (5)
  • gov to mojavedata.gov: 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.
  • mojavedata.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (172.99.69.142)
  • mojavedata.gov zone: There was an error resolving the following NS name(s) to address(es): server-03.mojavedata.gov
  • mojavedata.gov/A: The server was not reachable over UDP (EHOSTUNREACH). See RFC 1035, Sec. 4.2. (172.99.69.142, UDP_-_EDNS0_4096_D_KN)
  • mojavedata.gov/NS: The server was not reachable over UDP (EHOSTUNREACH). See RFC 1035, Sec. 4.2. (172.99.69.142, UDP_-_EDNS0_4096_D_KN)
Warnings (8)
  • mojavedata.gov/DS (alg 8, id 17431): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • mojavedata.gov/DS (alg 8, id 17431): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • mojavedata.gov/DS (alg 8, id 17431): 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.
  • mojavedata.gov/DS (alg 8, id 17431): 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.
  • mojavedata.gov/DS (alg 8, id 8209): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • mojavedata.gov/DS (alg 8, id 8209): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • mojavedata.gov/DS (alg 8, id 8209): 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.
  • mojavedata.gov/DS (alg 8, id 8209): 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.

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