View on GitHub

DNSViz: A DNS visualization tool

ucr.edu

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

RRset statusRRset status

Secure (5)
  • ucr.edu/A
  • ucr.edu/MX
  • ucr.edu/NS
  • ucr.edu/SOA
  • ucr.edu/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (14)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 33853)
  • ./DNSKEY (alg 8, id 48903)
  • edu/DNSKEY (alg 8, id 28065)
  • edu/DNSKEY (alg 8, id 50054)
  • edu/DS (alg 8, id 28065)
  • ucr.edu/DNSKEY (alg 10, id 25263)
  • ucr.edu/DNSKEY (alg 10, id 26666)
  • ucr.edu/DNSKEY (alg 10, id 29547)
  • ucr.edu/DNSKEY (alg 10, id 46082)
  • ucr.edu/DS (alg 10, id 25263)
  • ucr.edu/DS (alg 10, id 25263)
  • ucr.edu/DS (alg 10, id 29547)
  • ucr.edu/DS (alg 10, id 29547)

Delegation statusDelegation status

Secure (2)
  • . to edu
  • edu to ucr.edu

NoticesNotices

Errors (3)
  • zwcq0iv5n1.ucr.edu/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • ucr.edu/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • ucr.edu/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (29)
  • RRSIG ucr.edu/A alg 10, id 26666: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ucr.edu/DNSKEY alg 10, id 25263: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ucr.edu/DNSKEY alg 10, id 25263: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ucr.edu/DNSKEY alg 10, id 25263: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ucr.edu/DNSKEY alg 10, id 25263: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ucr.edu/DNSKEY alg 10, id 26666: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ucr.edu/DNSKEY alg 10, id 26666: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ucr.edu/DNSKEY alg 10, id 26666: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ucr.edu/DNSKEY alg 10, id 26666: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ucr.edu/DNSKEY alg 10, id 29547: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ucr.edu/DNSKEY alg 10, id 29547: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ucr.edu/DNSKEY alg 10, id 29547: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ucr.edu/DNSKEY alg 10, id 29547: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ucr.edu/MX alg 10, id 26666: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ucr.edu/NS alg 10, id 26666: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ucr.edu/SOA alg 10, id 26666: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ucr.edu/TXT alg 10, id 26666: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • ucr.edu/DS (alg 10, id 25263): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ucr.edu/DS (alg 10, id 25263): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ucr.edu/DS (alg 10, id 25263): 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.
  • ucr.edu/DS (alg 10, id 25263): 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.
  • ucr.edu/DS (alg 10, id 29547): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ucr.edu/DS (alg 10, id 29547): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ucr.edu/DS (alg 10, id 29547): 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.
  • ucr.edu/DS (alg 10, id 29547): 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.
  • zwcq0iv5n1.ucr.edu/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ucr.edu/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ucr.edu/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ucr.edu/AAAA 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