www.sfcollege.edu
Updated:
2020-06-09 19:59:30 UTC (1426 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (1)
- www.lb.sfcollege.edu/A
Secure (2)
- sfcollege.edu/SOA
- www.sfcollege.edu/CNAME
DNSKEY/DS/NSEC status
Secure (9)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 48903)
- NSEC proving non-existence of lb.sfcollege.edu/DS
- edu/DNSKEY (alg 8, id 28065)
- edu/DNSKEY (alg 8, id 8663)
- edu/DS (alg 8, id 28065)
- sfcollege.edu/DNSKEY (alg 5, id 46738)
- sfcollege.edu/DNSKEY (alg 5, id 60453)
- sfcollege.edu/DS (alg 5, id 46738)
Delegation status
Insecure (1)
- sfcollege.edu to lb.sfcollege.edu
Secure (2)
- . to edu
- edu to sfcollege.edu
Notices
Errors (7)
- edu to sfcollege.edu: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. (64.56.95.36, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
- edu to sfcollege.edu: The DS RRset for the zone included algorithm 5 (RSASHA1), but no DS RR matched a DNSKEY with algorithm 5 that signs the zone's DNSKEY RRset. (64.56.95.36, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
- sfcollege.edu to lb.sfcollege.edu: No NSEC RR(s) were returned to validate the NODATA response. (64.56.95.36, UDP_-_EDNS0_4096_D_K)
- sfcollege.edu/DNSKEY (alg 5, id 46738): No RRSIG covering the RRset was returned in the response. (64.56.95.36, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
- sfcollege.edu/DNSKEY (alg 5, id 60453): No RRSIG covering the RRset was returned in the response. (64.56.95.36, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
- sfcollege.edu/SOA: No RRSIG covering the RRset was returned in the response. (64.56.95.36, UDP_-_EDNS0_4096_D_K)
- www.sfcollege.edu/CNAME: No RRSIG covering the RRset was returned in the response. (64.56.95.36, UDP_-_EDNS0_4096_D_K)
Warnings (10)
- RRSIG NSEC proving non-existence of lb.sfcollege.edu/DS alg 5, id 60453: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
- RRSIG sfcollege.edu/DNSKEY alg 5, id 46738: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
- RRSIG sfcollege.edu/DNSKEY alg 5, id 46738: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
- RRSIG sfcollege.edu/DNSKEY alg 5, id 60453: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
- RRSIG sfcollege.edu/DNSKEY alg 5, id 60453: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
- RRSIG sfcollege.edu/SOA alg 5, id 60453: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
- RRSIG www.sfcollege.edu/CNAME alg 5, id 60453: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
- edu to sfcollege.edu: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the edu zone): ns2.sfcollege.edu
- sfcollege.edu/DS (alg 5, id 46738): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
- sfcollege.edu/DS (alg 5, id 46738): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
JavaScript is required to make the graph below interactive.
