{
  "id": "crawlers/facebookexternalhit",
  "url": "https://www.proxies.sx/crawlers/facebookexternalhit",
  "license": "CC BY 4.0",
  "reviewed": "2026-09-06",
  "name": "FacebookExternalHit",
  "operator": "Meta",
  "operatorUrl": "https://developers.facebook.com/",
  "docsUrl": "https://developers.facebook.com/docs/sharing/webmasters/web-crawlers",
  "purpose": "Social preview fetcher",
  "userAgentToken": "facebookexternalhit",
  "fullUserAgentExample": "facebookexternalhit/1.1 (+http://www.facebook.com/externalhit_uatext.php)",
  "robotsToken": "facebookexternalhit",
  "robotsTokenIsPolicyOnly": false,
  "honorsRobotsTxt": "partial",
  "verificationMethod": "Meta's current crawler page gives no method beyond \"Add to your allow list either the user agent strings or the IP addresses (more secure) used by the crawler.\" The retired Facebook Crawler page documented: \"To get a current list of IP addresses the crawler uses, run the following command. whois -h whois.radb.net -- '-i origin AS32934' | grep ^route\" and \"These IP addresses change often.\" Meta currently publishes a variant of that command on its WhatsApp webhooks page, described as returning \"the IP addresses of Meta's webhook servers\" rather than crawlers: \"whois -h whois.radb.net -- '-i origin AS32934' | grep '^route' | awk '{print $2}' | sort\", and links a geofeed CSV at https://facebook.com/peering/geofeed (\"download a CSV that lists Meta's IP addresses\"); no reverse-DNS method is documented.",
  "reverseDnsSuffix": null,
  "ipRanges": null,
  "sources": [
    "https://developers.facebook.com/docs/sharing/webmasters/web-crawlers",
    "https://developers.facebook.com/documentation/sharing/webmasters/web-crawlers",
    "https://developers.facebook.com/documentation/business-messaging/whatsapp/webhooks/overview",
    "https://web.archive.org/web/20240101000413id_/https://developers.facebook.com/docs/sharing/webmasters/crawler/"
  ]
}