facebook.com
Updated:
2021-10-04 21:18:55 UTC (1081 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 (1)
- 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 (2)
- facebook.com zone: There was an error resolving the following NS name(s) to address(es): a.ns.facebook.com
- facebook.com/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (185.89.218.12, UDP_-_NOEDNS_)
Warnings (4)
- com to facebook.com: A glue records exist for b.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/NS: 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. (129.134.31.12, UDP_-_EDNS0_4096_D_KN)
JavaScript is required to make the graph below interactive.
