RRSIG ru.com/DNSKEY alg 7, id 30236: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG ru.com/DNSKEY alg 7, id 30236: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG ru.com/DNSKEY alg 7, id 30236: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG ru.com/MX alg 7, id 14493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG ru.com/NS alg 7, id 14493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG ru.com/NSEC3PARAM alg 7, id 14493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG ru.com/SOA alg 7, id 14493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG ru.com/TXT alg 7, id 14493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
ru.com/DNSKEY (alg 7, id 14493): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:67c:13cc::1:24, UDP_-_EDNS0_4096_D_KN)
ru.com/DNSKEY (alg 7, id 30236): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:67c:13cc::1:24, UDP_-_EDNS0_4096_D_KN)
ru.com/DNSKEY (alg 7, id 62480): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:67c:13cc::1:24, UDP_-_EDNS0_4096_D_KN)
ru.com/DNSKEY: The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (194.169.218.24, 2001:67c:13cc::1:24, 2a04:2b00:13ee::10, UDP_-_EDNS0_512_D_KN)
ru.com/DS (alg 7, id 30236): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
ru.com/DS (alg 7, id 30236): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
ru.com/DS (alg 7, id 30236): 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.
ru.com/DS (alg 7, id 30236): 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.
ru.com/MX: The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (212.18.248.10, 2001:67c:13cc::1:24, 2a04:2b00:13ee::10, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
ru.com/NSEC3PARAM: The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (212.18.248.10, 2001:67c:13cc::1:24, UDP_-_EDNS0_4096_D_KN)
ru.com/SOA: The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (194.169.218.24, 212.18.248.10, 2a04:2b00:13ee::10, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
ru.com/TXT: The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (194.169.218.24, 212.18.248.10, UDP_-_EDNS0_4096_D_KN)
ru.com/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
ru.com/A has warnings; select the "Denial of existence" DNSSEC option to see them.
kihdx8rm10.ru.com/A has warnings; select the "Denial of existence" DNSSEC option to see them.
ru.com/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
ru.com/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.