facebook.com/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (129.134.30.12, UDP_-_EDNS0_512_D_KN)
Warnings (10)
com/DS (alg 8, id 30909): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (193.0.14.129, UDP_-_EDNS0_4096_D_KN)
com/DS (alg 8, id 30909): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (193.0.14.129, UDP_-_EDNS0_4096_D_KN)
facebook.com/AAAA: 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. (129.134.30.12, UDP_-_EDNS0_4096_D_KN)
facebook.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. See RFC 6891, Sec. 6.2.6. (129.134.30.12, UDP_-_EDNS0_4096_D_KN)
facebook.com/NS: No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (129.134.30.12, UDP_-_EDNS0_4096_D_KN)
facebook.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. See RFC 6891, Sec. 6.2.6. (129.134.30.12, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
u6swagojbc.facebook.com/A has warnings; select the "Denial of existence" DNSSEC option to see them.
facebook.com/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
facebook.com/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
facebook.com/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.