. to tm: 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. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (74.116.178.22, 194.0.1.22, 2001:678:4::16, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
. to tm: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (74.116.178.22, 194.0.1.22, 2001:678:4::16, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
tm/DNSKEY (alg 8, id 35933): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (74.116.178.22, 194.0.1.22, 2001:678:4::16, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
tm/DNSKEY (alg 8, id 36787): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (74.116.178.22, 194.0.1.22, 2001:678:4::16, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
tm/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (74.116.178.22, 194.0.1.22, 2001:678:4::16, UDP_-_EDNS0_4096_D_KN)
tm/NSEC3PARAM (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (74.116.178.22, 194.0.1.22, 2001:678:4::16, UDP_-_EDNS0_4096_D_KN)
tm/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (74.116.178.22, 194.0.1.22, 2001:678:4::16, UDP_-_EDNS0_4096_D_KN)
tm/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
tm/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
0nfp3ebmtj.tm/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (2)
tm/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
0nfp3ebmtj.tm/A has warnings; select the "Denial of existence" DNSSEC option to see them.