berkeley.edu/DNSKEY: No response was received from the server over UDP (tried 2 times). See RFC 1035, Sec. 4.2. (128.32.136.3, 128.32.136.14, 192.107.102.142, 2607:f140:a000:d::abc, 2607:f140:ffff:fffe::3, 2607:f140:ffff:fffe::e, UDP_-_EDNS0_512_D_KN)
berkeley.edu/MX: No response was received from the server over UDP (tried 2 times). See RFC 1035, Sec. 4.2. (128.32.136.3, 128.32.136.14, 192.107.102.142, 2607:f140:a000:d::abc, 2607:f140:ffff:fffe::3, 2607:f140:ffff:fffe::e, UDP_-_EDNS0_512_D_KN)
berkeley.edu/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (29)
RRSIG berkeley.edu/A alg 10, id 26483: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG berkeley.edu/A alg 10, id 33428: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG berkeley.edu/DNSKEY alg 10, id 10359: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG berkeley.edu/DNSKEY alg 10, id 10359: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG berkeley.edu/DNSKEY alg 10, id 10359: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG berkeley.edu/DNSKEY alg 10, id 10359: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG berkeley.edu/DNSKEY alg 10, id 33428: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG berkeley.edu/DNSKEY alg 10, id 33428: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG berkeley.edu/DNSKEY alg 10, id 33428: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG berkeley.edu/DNSKEY alg 10, id 33428: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG berkeley.edu/DNSKEY alg 10, id 59277: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG berkeley.edu/DNSKEY alg 10, id 59277: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG berkeley.edu/DNSKEY alg 10, id 59277: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG berkeley.edu/DNSKEY alg 10, id 59277: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG berkeley.edu/MX alg 10, id 26483: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG berkeley.edu/MX alg 10, id 33428: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG berkeley.edu/NS alg 10, id 26483: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG berkeley.edu/NS alg 10, id 33428: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG berkeley.edu/SOA alg 10, id 33428: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG berkeley.edu/TXT alg 10, id 33428: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
edu to berkeley.edu: Authoritative AAAA records exist for adns1.berkeley.edu, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
edu to berkeley.edu: Authoritative AAAA records exist for adns2.berkeley.edu, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
berkeley.edu/CDS has warnings; select the "Denial of existence" DNSSEC option to see them.
berkeley.edu/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
berkeley.edu/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
berkeley.edu/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
3akzm.d89pt.berkeley.edu/A has warnings; select the "Denial of existence" DNSSEC option to see them.
berkeley.edu/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
berkeley.edu/CDNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.