progressive.com zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. (170.218.228.11)
progressive.com/DNSKEY: No response was received from the server over TCP (tried 10 times). (170.218.218.11, TCP_-_EDNS0_4096_D_K)
progressive.com/DNSKEY: No response was received from the server over UDP (tried 4 times). (170.218.228.10, 170.218.228.11, UDP_-_EDNS0_512_D_K)
progressive.com/MX: No response was received from the server over TCP (tried 12 times). (170.218.218.11, TCP_-_EDNS0_4096_D_K)
progressive.com/MX: No response was received from the server over UDP (tried 4 times). (170.218.218.10, 170.218.228.11, UDP_-_EDNS0_512_D_K)
progressive.com/SOA: No response was received from the server over TCP (tried 3 times). (170.218.218.10, 170.218.228.11, TCP_-_EDNS0_4096_D)
progressive.com/SOA: No response was received from the server over UDP (tried 12 times). (170.218.228.10, UDP_-_NOEDNS_)
Warnings (4)
progressive.com/MX: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. (170.218.218.10, UDP_-_EDNS0_4096_D_K)
progressive.com/NS: No response was received from the server over UDP (tried 11 times) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). (170.218.228.11, UDP_-_EDNS0_4096_D_K)
progressive.com/SOA: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). (170.218.218.10, UDP_-_EDNS0_4096_D_K)
progressive.com/SOA: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. (170.218.228.11, UDP_-_EDNS0_4096_D_K)