mesh.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (130.14.252.50, 130.14.252.53, 165.112.6.3)
mesh.gov/MX (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. (165.112.6.3, 2607:f220:41f:1405::3, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
mesh.gov/MX (NODATA): The response was an upward referral. See https://www.dns-oarc.net/oarc/articles/upward-referrals-considered-harmful. (165.112.6.3, 2607:f220:41f:1405::3, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
mesh.gov/NS (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. (165.112.6.3, 2607:f220:41f:1405::3, UDP_-_EDNS0_4096_D_KN)
mesh.gov/NS (NODATA): The response was an upward referral. See https://www.dns-oarc.net/oarc/articles/upward-referrals-considered-harmful. (165.112.6.3, 2607:f220:41f:1405::3, UDP_-_EDNS0_4096_D_KN)
mesh.gov/SOA (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. (165.112.6.3, 2607:f220:41f:1405::3, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
mesh.gov/SOA (NODATA): The response was an upward referral. See https://www.dns-oarc.net/oarc/articles/upward-referrals-considered-harmful. (165.112.6.3, 2607:f220:41f:1405::3, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
mesh.gov/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (130.14.252.50, 130.14.252.53, 165.112.6.3, TCP_-_EDNS0_4096_D_N)
mesh.gov/SOA: No response was received from the server over TCP (tried 7 times). See RFC 1035, Sec. 4.2. (2607:f220:41e:252::50, TCP_-_EDNS0_4096_D_KN)
mesh.gov/TXT (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. (165.112.6.3, 2607:f220:41f:1405::3, UDP_-_EDNS0_4096_D_KN)
mesh.gov/TXT (NODATA): The response was an upward referral. See https://www.dns-oarc.net/oarc/articles/upward-referrals-considered-harmful. (165.112.6.3, 2607:f220:41f:1405::3, UDP_-_EDNS0_4096_D_KN)
mesh.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
3kqc6a9wv2.mesh.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
mesh.gov/A: 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). See RFC 6891, Sec. 6.1.2. (2607:f220:41e:252::53, UDP_-_EDNS0_4096_D_KN)
mesh.gov/TXT: 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. See RFC 6891, Sec. 6.2.6. (2607:f220:41e:252::50, UDP_-_EDNS0_4096_D_KN)
mesh.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
3kqc6a9wv2.mesh.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.