RRSIG berkeley.edu/DNSKEY alg 10, id 25055: The Signature Expiration field of the RRSIG RR (2023-11-11 05:05:44+00:00) is 13 days in the past. See RFC 4035, Sec. 5.3.1.
RRSIG berkeley.edu/DNSKEY alg 10, id 25055: The Signature Expiration field of the RRSIG RR (2023-11-11 05:05:44+00:00) is 13 days in the past. See RFC 4035, Sec. 5.3.1.
RRSIG berkeley.edu/DNSKEY alg 10, id 25055: The Signature Expiration field of the RRSIG RR (2023-11-11 05:05:44+00:00) is 13 days in the past. See RFC 4035, Sec. 5.3.1.
RRSIG berkeley.edu/DNSKEY alg 10, id 25055: The Signature Expiration field of the RRSIG RR (2023-11-11 05:05:44+00:00) is 13 days in the past. See RFC 4035, Sec. 5.3.1.
berkeley.edu/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (28)
RRSIG berkeley.edu/A alg 10, id 21896: 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 21896: 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 21896: 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 21896: 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 21896: 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 25055: 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 25055: 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 25055: 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 25055: 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 38028: 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 38028: 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 38028: 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 38028: 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 21896: 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 21896: 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 21896: 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 21896: 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/CNAME 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.
berkeley.edu/NSEC3PARAM 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.
kdc9nbejqf.berkeley.edu/A has warnings; select the "Denial of existence" DNSSEC option to see them.