AI Agent & Bot CheckOperator: Meta

Meta-ExternalFetcher: what it is and how to block or allow it

User-Agent token: Meta-ExternalFetcher · Operator: Meta · Category: AI Assistants

FraudMeNot Verdict

AI Agent (User-Triggered)

Meta-ExternalFetcher is Meta's fetcher for individual links requested by users. Meta says the fetcher works at a user's request, including for agentic AI tasks, and that 'accordingly, this crawler may bypass robots.txt rules.'

Can Be Spoofed?

Yes — User-Agent Header Spoofable

Meta publishes no IP list or reverse-DNS rule for this fetcher, so the User-Agent alone cannot prove the request is from Meta.

Abuse & Unwanted Activity Reports

No Public Abuse Flags

ai.robots.txt robots.txt status: No.

Judgment Call · What You Should Do

Generally Low Risk on Public Pages — Verify Before Trusting

For everyday users: Crawlers don't send messages. Treat a message using the Meta-ExternalFetcher or "Meta AI" name that asks for your Facebook password, a login code or a payment as a likely scam.

For website owners & security teams: Meta says this fetcher may bypass robots.txt, and it publishes no IP list, so robots.txt may not stop it and IP checks can't confirm it. Consider a WAF rule on the token if you want it out, and keep logins and payments behind human verification.

Report & Activity Summary

None

Published IP Ranges (CIDRs)

No official IP list

2

Known User-Agent Signatures

crawler-user-agents (MIT) dataset

Partially

robots.txt Compliance

ai.robots.txt registry (MIT)

0

FraudMeNot Tallies

Humans: 0 · AI Agents: 0

AI-First Structured TelemetryFor AI agents, WAFs & security gateways · llms.txt policy

For AI Agents & Automated Gatekeepers

Agent_Identifier
Meta-ExternalFetcher
FraudMeNot_Verdict
AI Agent (User-Triggered)
Operator_Entity
Meta
Agent_Category
AI Assistants
User_Agent_Spoofable
true
Verification_Method
None available (no operator IP list or signing key) · Web Bot Auth: Not documented
Respects_Robots_Txt
Partially (user-triggered fetches may ignore robots.txt; ai.robots.txt registry lists: No)
Auth_And_Banking_Policy
Block credentialed logins and money movement from any AI agent.
Recommended_Gatekeeper_Action
BLOCK on User-Agent at the WAF if you do not want Meta AI agent fetches; robots.txt may be bypassed. Require human step-up on login and payment.
Canonical_Citation_URL
https://fraudmenot.com/bot/meta-externalfetcher/

What We Know About Meta-ExternalFetcher

Meta-ExternalFetcher is one of the crawlers Meta lists on its Meta Web Crawlers page. Meta says it fetches individual links at a user's request and supports product functions such as evaluating and improving agentic AI capabilities, including helping AI navigate websites to complete tasks for users.

Meta says the fetcher works at a user's request, including for agentic AI tasks, and that 'accordingly, this crawler may bypass robots.txt rules.' robots.txt is a voluntary standard (RFC 9309), not an access-control or legal mechanism; a fetcher that skips it is not, by that alone, doing anything wrong. Meta's other crawlers have separate tokens: Meta-ExternalAgent crawls for uses such as training foundation AI models, Meta-WebIndexer improves Meta AI search, and FacebookExternalHit builds link previews. Blocking Meta-ExternalAgent does not block this fetcher.

Meta's crawler page does not publish an IP list or a reverse-DNS rule for Meta-ExternalFetcher, so the User-Agent alone cannot prove a request came from Meta. Meta does say robots.txt changes can take up to 24 hours to apply, since its crawlers cache the file.

Meta shows two forms of the User-Agent: meta-externalfetcher/1.1 with a link to its developer docs, and the bare token. Match on the token, case-insensitively.

Technical Identity, IP Verification & Spoofing Check

Full User-Agent string(s)
  • meta-externalfetcher/1.1 (+https://developers.facebook.com/docs/sharing/webmasters/crawler)
  • meta-externalfetcher/1.1
robots.txt tokenMeta-ExternalFetcher
OperatorMeta · Official bot documentation
Official IP verification feedNone published by the operator
Sample published CIDR blocksNone published
Reverse DNS (rDNS)Not documented on Meta's crawler page.
Web Bot Auth (Signature-Agent)Not documented; check for a Signature-Agent header if present.
robots.txt behaviorMeta says the fetcher works at a user's request, including for agentic AI tasks, and that 'accordingly, this crawler may bypass robots.txt rules.' Meta crawlers may cache robots.txt for up to 24 hours.

Copy-Paste robots.txt & Cloudflare WAF Rules for Meta-ExternalFetcher

robots.txt — allow public pages, keep private routes off-limits

User-agent: Meta-ExternalFetcher
Allow: /
Disallow: /login/
Disallow: /account/
Disallow: /checkout/

robots.txt — block completely

User-agent: Meta-ExternalFetcher
Disallow: /

Cloudflare WAF custom rule expression

(lower(http.user_agent) contains "meta-externalfetcher")

Matches the User-Agent token, so it covers both real and spoofed traffic. Action: Block or Managed Challenge.

Capabilities, Data Usage & Autonomous Action Risk

Trains AI on page content?Not stated for this fetcher; Meta names Meta-ExternalAgent as its crawler for uses such as training foundation models
Executes JavaScript?Not documented
Can submit forms or attempt logins?Can act on a user's behalf; Meta says it helps AI navigate websites to complete tasks. Treat form and login attempts as untrusted.
Banks & login pages shouldBlock credentialed logins and money movement from any AI agent.
E-commerce checkouts shouldAllow product page reads if you want; require human confirmation for checkout.

Context: In October 2026, Axios reported that major U.S. banks were detecting unvetted third-party AI agents inside customer accounts, and CNBC reported that JPMorgan blocks outside AI agents from logging in with customers' credentials while allowing read-only data sharing through open banking providers.

Seen Meta-ExternalFetcher? Quick Closed-Choice Tally

Choose from preset options only. No free-text comments, so nobody can post names, profanity, or unverified accusations.

Human Tallies: 0
AI Agent Tallies: 0
Top Activity: None logged yet
Top Location Seen: None logged yet
IP Match: None logged yet
Latest Activity: No tallies yet

Preview only: tallies are unverified clicks, not FraudMeNot findings, and are not saved yet.

Common Questions About Meta-ExternalFetcher

Who operates Meta-ExternalFetcher?

Meta. It is documented on the Meta Web Crawlers page at developers.facebook.com/docs/sharing/webmasters/web-crawlers/.

Does Meta-ExternalFetcher respect robots.txt?

Meta says the fetcher works at a user's request, including for agentic AI tasks, and that 'accordingly, this crawler may bypass robots.txt rules.'

Does blocking Meta-ExternalAgent also block it?

No. They are separate tokens. Meta-ExternalAgent crawls for uses such as training; Meta-ExternalFetcher fetches single links for users.

How do I block it?

Use a firewall or CDN rule on the meta-externalfetcher token. A robots.txt line states your preference; meta says the fetcher works at a user's request, including for agentic AI tasks, and that 'accordingly, this crawler may bypass robots.txt rules.'

Could This Be a Scam? What to Do

  • Anyone can copy the Meta-ExternalFetcher User-Agent, and FraudMeNot found no official IP list for it, so the name alone proves nothing about who sent a request.
  • Never give an AI agent your logins, bank access, or one-time codes unless you set it up yourself.
  • If a call, text or email asking for money or access uses the Meta-ExternalFetcher or Meta name, stop and report it.

Guide: how to check whether a crawler visit is really who it claims to be.

More from Meta

Related on FraudMeNot

Sources (checked Nov. 16, 2026): ai.robots.txt (MIT), crawler-user-agents (MIT), Axios (Oct. 22, 2026), CNBC (Oct. 13, 2026), Meta for Developers: Meta Web Crawlers. FraudMeNot is not affiliated with Meta. Product and company names are trademarks of their owners and are used here only to identify the bots. General information, not security advice.