ca to sandelman.ca: 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. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (97.107.133.15, 2600:3c03::f03c:91ff:fe96:e8ef, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
sandelman.ca/A: The DNSKEY RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (97.107.133.15, 2600:3c03::f03c:91ff:fe96:e8ef, UDP_-_EDNS0_4096_D_KN)
sandelman.ca/A: The DS RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (97.107.133.15, 2600:3c03::f03c:91ff:fe96:e8ef, UDP_-_EDNS0_4096_D_KN)
sandelman.ca/AAAA: The DNSKEY RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (97.107.133.15, 2600:3c03::f03c:91ff:fe96:e8ef, UDP_-_EDNS0_4096_D_KN)
sandelman.ca/AAAA: The DS RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (97.107.133.15, 2600:3c03::f03c:91ff:fe96:e8ef, UDP_-_EDNS0_4096_D_KN)
sandelman.ca/DNSKEY (alg 13, id 35158): The DNSKEY RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (97.107.133.15, 2600:3c03::f03c:91ff:fe96:e8ef, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
sandelman.ca/DNSKEY (alg 13, id 35158): The DS RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (97.107.133.15, 2600:3c03::f03c:91ff:fe96:e8ef, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
sandelman.ca/DNSKEY (alg 5, id 38386): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (97.107.133.15, 2600:3c03::f03c:91ff:fe96:e8ef, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
sandelman.ca/MX: The DNSKEY RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (97.107.133.15, 2600:3c03::f03c:91ff:fe96:e8ef, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
sandelman.ca/MX: The DS RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (97.107.133.15, 2600:3c03::f03c:91ff:fe96:e8ef, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
sandelman.ca/NS: The DNSKEY RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (97.107.133.15, 2600:3c03::f03c:91ff:fe96:e8ef, UDP_-_EDNS0_4096_D_KN)
sandelman.ca/NS: The DS RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (97.107.133.15, 2600:3c03::f03c:91ff:fe96:e8ef, UDP_-_EDNS0_4096_D_KN)
sandelman.ca/SOA: The DNSKEY RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (97.107.133.15, 2600:3c03::f03c:91ff:fe96:e8ef, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
sandelman.ca/SOA: The DS RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (97.107.133.15, 2600:3c03::f03c:91ff:fe96:e8ef, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
sandelman.ca/TXT: The DNSKEY RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (97.107.133.15, 2600:3c03::f03c:91ff:fe96:e8ef, UDP_-_EDNS0_4096_D_KN)
sandelman.ca/TXT: The DS RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (97.107.133.15, 2600:3c03::f03c:91ff:fe96:e8ef, UDP_-_EDNS0_4096_D_KN)
sandelman.ca/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
groe8ip0tc.sandelman.ca/A has errors; select the "Denial of existence" DNSSEC option to see them.
sandelman.ca/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
sandelman.ca/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (16)
RRSIG sandelman.ca/A alg 5, id 38386: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG sandelman.ca/AAAA alg 5, id 38386: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG sandelman.ca/DNSKEY alg 5, id 38386: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG sandelman.ca/DNSKEY alg 5, id 38386: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG sandelman.ca/MX alg 5, id 38386: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG sandelman.ca/NS alg 5, id 38386: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG sandelman.ca/SOA alg 5, id 38386: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG sandelman.ca/TXT alg 5, id 38386: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
sandelman.ca/DS (alg 5, id 38386): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
sandelman.ca/DS (alg 5, id 38386): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
sandelman.ca/DS (alg 5, id 38386): 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.
sandelman.ca/DS (alg 5, id 38386): 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.
sandelman.ca/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
groe8ip0tc.sandelman.ca/A has warnings; select the "Denial of existence" DNSSEC option to see them.
sandelman.ca/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
sandelman.ca/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.