RRSIG sourceware.org/A alg 5, id 96: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG sourceware.org/A alg 5, id 96: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG sourceware.org/AAAA alg 5, id 96: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG sourceware.org/AAAA alg 5, id 96: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG sourceware.org/DNSKEY alg 5, id 1828: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG sourceware.org/DNSKEY alg 5, id 1828: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG sourceware.org/DNSKEY alg 5, id 96: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG sourceware.org/DNSKEY alg 5, id 96: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG sourceware.org/MX alg 5, id 96: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG sourceware.org/MX alg 5, id 96: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG sourceware.org/NS alg 5, id 96: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG sourceware.org/NS alg 5, id 96: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG sourceware.org/SOA alg 5, id 96: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG sourceware.org/SOA alg 5, id 96: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG sourceware.org/TXT alg 5, id 96: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
org to sourceware.org: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the org zone): ns1.linode.com, ns5.linode.com, ns2.linode.com, ns3.linode.com, ns4.linode.com See RFC 1034, Sec. 4.2.2.
sourceware.org/DNSKEY: The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (162.159.24.25, UDP_-_EDNS0_512_D_KN)
sourceware.org/MX: The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (162.159.24.25, UDP_-_EDNS0_512_D_KN)
sourceware.org/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
sourceware.org/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
sourceware.org/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
64jcsezdm2.sourceware.org/A has warnings; select the "Denial of existence" DNSSEC option to see them.