GuidesAgents on the web

What “[email protected]” means, and how to find the real address

Cloudflare swaps each email address on a page for this text until a browser runs its script. How to find the real address, and what AI assistants see instead.

September 28, 2026Updated October 13, 2026The Everpod team
The short answer

“[email protected]” is not an email address. It is the text Cloudflare puts in place of each address on a page when the site has Email Address Obfuscation on, which Cloudflare switches on automatically when a site signs up. A script in the page puts the real address back once a browser runs it, so you only see the placeholder where that script did not run: with JavaScript blocked, in a search result, or in an AI assistant’s answer. To get the address, open the page on the site itself in an ordinary browser. AI assistants reading the page through a fetch tool get the placeholder too, and cannot give you the address.

Where the placeholder shows up

Cloudflare rewrites the page on its way to you. Each address in the text, and each address in an email link, becomes “[email protected]”, and a short script, email-decode.min.js, is added to the page to reverse the swap. In a browser that happens before you can notice, which is why Cloudflare’s documentation says visitors see no change. You see the placeholder wherever the script did not run:

How to get the real address

Open the page itself, on the site, in an ordinary browser with JavaScript on, rather than the search result or the answer that quoted it. If you use a script blocker, allow that site. The address appears where the placeholder was, and the link opens your email app.

If all you have is the page’s source, the address is in it, encoded. Look for data-cfemail="…" beside the placeholder, or a link to /cdn-cgi/l/email-protection# followed by letters and digits. The value is hexadecimal: the first two characters are a key, and each following pair, combined with the key by XOR, is one character of the address. That is all Cloudflare’s decode script does. One line of Python does the same; this example value decodes to hello@example.com:

python3 -c "import sys; h=sys.argv[1]; print(''.join(chr(int(h[i:i+2],16) ^ int(h[:2],16)) for i in range(2, len(h), 2)))" 422a272e2e2d02273a232f322e276c212d2f
Copied

What AI assistants get instead

As of September 2026, Claude with web search and page fetch cannot give a contact address that sits behind this setting: the pages come back with the placeholder, and the assistant may say so, reporting the address as “obfuscated by Cloudflare email protection.”

The fetch tool can also return an address that is not on the page at all, such as the site’s name under a different domain ending, which can be a domain another company owns. That tool hands the assistant a smaller model’s reading of the page rather than the page itself. An assistant can distrust that address and give none, so the person asking is left without one. Where pages serve their addresses as plain text, Claude and OpenAI’s Codex find the address when a question needs it.

The placeholder sits in search indexes as well. A web search for the phrase itself returns ordinary contact pages whose indexed text carries it, and as of September 2026 an assistant’s search summary can take it for a real address, describing “[email protected]” as “a generic email pattern used by various organizations for their general contact inquiries.” If an assistant gives you an address for a site that shows the placeholder, check it on the site before you write to it.

An agent of your own meets the same wall. OpenClaw’s web_fetch tool is documented as a plain HTTP request with readable-text extraction that “does not execute JavaScript”, so on such a page it should read the placeholder, while the agent’s browser runs the page’s scripts like any browser and should see the address, going by the two tools’ documentation. An agent that has the raw HTML can also be given the decoding rule above.

If it’s your site

If your site is on Cloudflare and nobody has switched this off, it is on: Cloudflare enables it automatically at sign-up. The setting is a toggle in the Cloudflare dashboard: Security, then Settings (filter by Client-side abuse), then Email Address Obfuscation. Through the API it is the zone setting email_obfuscation. It rewrites addresses in the page’s text and in links’ href, and by Cloudflare’s documentation leaves these alone:

The cost is that it hides your address from every reader that does not run your page’s scripts: the harvesters it was built to stop, and the assistants people now ask how to reach you. If you want an assistant to be able to answer that, the contact address has to be readable without script. Switch the toggle off for the whole site, switch it off for one hostname or path with a configuration rule, or exempt a single address with Cloudflare’s comment markers:

<!--email_off-->hello@example.com<!--/email_off-->
Copied

Putting the address in a noscript block gets it past Cloudflare and loses it anyway: Mozilla’s Readability, the library behind Firefox’s Reader View and the extractor OpenClaw’s web_fetch runs, deletes noscript content before it reads anything. What else page readers keep and drop is in how to make your website readable by AI agents. To check a page, fetch it the way an assistant does:

curl -sL https://example.com/contact | grep -c email-protection
Copied

Any number above zero means addresses on that page are still hidden.

Give your AI agents a permanent cloud computer.

We set it up and secure it, so all you do is use them. Run Claude Code, Codex or any agent you use, more at once than your laptop can hold, and keep them working when it’s closed. Or have OpenClaw set up and run for you.

See the developer pod

From $24/mo · your own plan or API key

Get your OpenClaw agent

$29/mo, cancel anytime · model usage included