RRSIG ucsc.edu/A alg 10, id 5030: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG ucsc.edu/DNSKEY alg 10, id 18264: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG ucsc.edu/DNSKEY alg 10, id 18264: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG ucsc.edu/DNSKEY alg 10, id 18264: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG ucsc.edu/DNSKEY alg 10, id 18264: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG ucsc.edu/DNSKEY alg 10, id 18264: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG ucsc.edu/DNSKEY alg 10, id 183: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG ucsc.edu/DNSKEY alg 10, id 183: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG ucsc.edu/DNSKEY alg 10, id 183: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG ucsc.edu/DNSKEY alg 10, id 183: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG ucsc.edu/DNSKEY alg 10, id 183: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG ucsc.edu/DNSKEY alg 10, id 5030: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG ucsc.edu/DNSKEY alg 10, id 5030: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG ucsc.edu/DNSKEY alg 10, id 5030: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG ucsc.edu/DNSKEY alg 10, id 5030: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG ucsc.edu/DNSKEY alg 10, id 5030: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG ucsc.edu/MX alg 10, id 5030: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG ucsc.edu/NS alg 10, id 5030: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG ucsc.edu/SOA alg 10, id 5030: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG ucsc.edu/TXT alg 10, id 5030: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
edu to ucsc.edu: Authoritative AAAA records exist for adns1.ucsc.edu, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
edu to ucsc.edu: Authoritative AAAA records exist for adns2.ucsc.edu, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
ucsc.edu/DS (alg 10, id 18264): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
ucsc.edu/DS (alg 10, id 18264): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
ucsc.edu/DS (alg 10, id 18264): 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.
ucsc.edu/DS (alg 10, id 18264): 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.
ucsc.edu/DS (alg 10, id 183): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
ucsc.edu/DS (alg 10, id 183): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
ucsc.edu/DS (alg 10, id 183): 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.
ucsc.edu/DS (alg 10, id 183): 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.
ucsc.edu/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
2rlfhgm65w.ucsc.edu/A has warnings; select the "Denial of existence" DNSSEC option to see them.
ucsc.edu/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
ucsc.edu/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
ucsc.edu/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.