berkeley.edu
Updated:
2021-06-02 20:49:59 UTC (1301 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- berkeley.edu/A
- berkeley.edu/MX
- berkeley.edu/NS
- berkeley.edu/SOA
- berkeley.edu/TXT
DNSKEY/DS/NSEC status
Secure (9)
- ./DNSKEY (alg 8, id 14631)
- ./DNSKEY (alg 8, id 20326)
- berkeley.edu/DNSKEY (alg 10, id 16914)
- berkeley.edu/DNSKEY (alg 10, id 26315)
- berkeley.edu/DNSKEY (alg 10, id 37778)
- berkeley.edu/DS (alg 10, id 16914)
- edu/DNSKEY (alg 8, id 28065)
- edu/DNSKEY (alg 8, id 63587)
- edu/DS (alg 8, id 28065)
Delegation status
Secure (2)
- . to edu
- edu to berkeley.edu
Notices
Warnings (19)
- RRSIG berkeley.edu/A alg 10, id 26315: 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 16914: 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 16914: 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 16914: 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 26315: 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 26315: 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 26315: 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 26315: 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 26315: 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 26315: 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 26315: 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.
- edu/DS (alg 8, id 28065): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (192.203.230.10, UDP_-_EDNS0_4096_D_KN)
- edu/DS (alg 8, id 28065): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (192.203.230.10, UDP_-_EDNS0_4096_D_KN)
- xar2gdwukz.berkeley.edu/A 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/DNSKEY 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.
JavaScript is required to make the graph below interactive.
