Meta

Operator

See operator's docs

Verification

Meta-ExternalFetcher

robots.txt token

No

Honours robots.txt

What Meta-ExternalFetcher is

Meta fetching a link a user shared with Meta AI or another Meta product.

Its robots.txt token is Meta-ExternalFetcher , but it is not listed as honouring robots.txt. Operator documentation: Meta .

Verifying it yourself

WebDecoy has no published IP list or reverse DNS hostname on file for Meta-ExternalFetcher. Check Meta's documentation for one, such as a list of addresses or signed requests. Until you can check the source address, the User-Agent is only a claim, and copying a User-Agent costs nothing.

Blocking it

You can ask in robots.txt, but it is not listed as honouring it:

User-agent: Meta-ExternalFetcher
Disallow: /

robots.txt only works on a client willing to obey it, which rules out every request that was already lying about who it is. Stopping those takes enforcement at the network or application layer, keyed on something the client cannot simply retype. That is the problem WebDecoy exists to solve.

Frequently Asked Questions

What is Meta-ExternalFetcher? +

Meta-ExternalFetcher is an ai assistant operated by Meta. Meta fetching a link a user shared with Meta AI or another Meta product.

How do I verify Meta-ExternalFetcher? +

WebDecoy has no published IP list or reverse DNS hostname on file for Meta-ExternalFetcher. Check Meta's documentation for one; until you can check the source address, the User-Agent is only a claim.

How do I block Meta-ExternalFetcher? +

It is not listed as honouring robots.txt, so a Disallow rule for Meta-ExternalFetcher may be ignored. Block it at your firewall, CDN or application instead, after verifying which requests really come from Meta.

See which Meta-ExternalFetcher requests are real

WebDecoy verifies declared crawlers against what their operators publish and identifies the ones that fail, as persistent actors rather than disposable IPs.

Start Free Trial