facebook.com
Updated:
2021-10-04 21:18:33 UTC (1132 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (8)
- facebook.com/A
- facebook.com/AAAA
- facebook.com/MX
- facebook.com/NS
- facebook.com/SOA
- facebook.com/SOA
- facebook.com/SOA
- facebook.com/TXT
Secure (2)
- com/SOA
- com/SOA
DNSKEY/DS/NSEC status
Secure (7)
- ./DNSKEY (alg 8, id 14748)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26838)
- NSEC3 proving non-existence of facebook.com/DS
- com/DNSKEY (alg 8, id 30909)
- com/DNSKEY (alg 8, id 39343)
- com/DS (alg 8, id 30909)
Delegation status
Insecure (1)
- com to facebook.com
Secure (1)
- . to com
Notices
Errors (13)
- facebook.com zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (129.134.31.12)
- facebook.com zone: There was an error resolving the following NS name(s) to address(es): a.ns.facebook.com, b.ns.facebook.com, c.ns.facebook.com
- facebook.com/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (129.134.31.12, 2a03:2880:f1fc:c:face:b00c:0:35, UDP_-_NOEDNS_)
- facebook.com/AAAA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (185.89.218.12, 2a03:2880:f1fc:c:face:b00c:0:35, UDP_-_NOEDNS_)
- facebook.com/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (129.134.30.12, 185.89.218.12, 2a03:2880:f0fd:c:face:b00c:0:35, 2a03:2880:f1fc:c:face:b00c:0:35, UDP_-_EDNS0_512_D_KN)
- facebook.com/MX: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2a03:2880:f0fd:c:face:b00c:0:35, UDP_-_NOEDNS_)
- 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, 185.89.218.12, 2a03:2880:f0fd:c:face:b00c:0:35, 2a03:2880:f1fc:c:face:b00c:0:35, UDP_-_EDNS0_512_D_KN)
- facebook.com/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (129.134.31.12, 185.89.218.12, 2a03:2880:f0fd:c:face:b00c:0:35, UDP_-_NOEDNS_)
- facebook.com/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (2a03:2880:f1fc:c:face:b00c:0:35, TCP_-_EDNS0_4096_D_N)
- facebook.com/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (185.89.218.12, 2a03:2880:f1fc:c:face:b00c:0:35, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
- facebook.com/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- facebook.com/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- facebook.com/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (21)
- com to facebook.com: A glue records exist for d.ns.facebook.com, but there are no corresponding authoritative A records. See RFC 1034, Sec. 4.2.2.
- 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/A: 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. (2a03:2880:f0fc:c:face:b00c:0:35, UDP_-_EDNS0_4096_D_KN)
- facebook.com/A: 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. (2a03:2880:f0fd:c:face:b00c:0:35, UDP_-_EDNS0_4096_D_KN)
- facebook.com/AAAA: No response was received from the server over UDP (tried 10 times) until the DO EDNS flag was cleared (however, this server appeared to respond legitimately to other queries with the DO EDNS flag set). See RFC 6891, Sec. 6.1.4. (2a03:2880:f0fd:c:face:b00c:0:35, UDP_-_EDNS0_4096_D_KN)
- facebook.com/MX: 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). See RFC 6891, Sec. 6.2.6. (185.89.218.12, UDP_-_EDNS0_4096_D_KN)
- facebook.com/MX: 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. (2a03:2880:f1fc:c:face:b00c:0:35, 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. (2a03:2880:f0fc:c:face:b00c:0:35, UDP_-_EDNS0_4096_D_KN)
- facebook.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). See RFC 6891, Sec. 6.2.6. (2a03:2880:f1fc:c:face:b00c:0:35, UDP_-_EDNS0_4096_D_KN)
- facebook.com/SOA: No response was received from the server over UDP (tried 10 times) until the DO EDNS flag was cleared (however, this server appeared to respond legitimately to other queries with the DO EDNS flag set). See RFC 6891, Sec. 6.1.4. (2a03:2880:f0fd:c:face:b00c:0:35, UDP_-_EDNS0_4096_D_KN)
- facebook.com/SOA: 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). See RFC 6891, Sec. 6.2.6. (185.89.218.12, UDP_-_EDNS0_4096_D_KN)
- facebook.com/SOA: 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. (2a03:2880:f1fc:c:face:b00c:0:35, UDP_-_EDNS0_4096_D_KN)
- facebook.com/TXT: No response was received from the server over UDP (tried 10 times) until the DO EDNS flag was cleared (however, this server appeared to respond legitimately to other queries with the DO EDNS flag set). See RFC 6891, Sec. 6.1.4. (2a03:2880:f0fd:c:face:b00c:0:35, UDP_-_EDNS0_4096_D_KN)
- facebook.com/TXT: 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). See RFC 6891, Sec. 6.2.6. (185.89.218.12, UDP_-_EDNS0_4096_D_KN)
- facebook.com/TXT: 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. (2a03:2880:f1fc:c:face:b00c:0:35, UDP_-_EDNS0_4096_D_KN)
- facebook.com/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. (2a03:2880:f0fc:c:face:b00c:0:35, UDP_-_EDNS0_4096_D_KN)
- cvtz1oekry.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.
JavaScript is required to make the graph below interactive.
