Email Address Obfuscation: How It Works and How to Read It
Websites hide email addresses with text tricks, scripts and images. Learn how each technique works, what it costs your visitors, and how prospectors find contacts ethically.

TL;DR
- Email address obfuscation is any technique that hides an address from automated scrapers while keeping it usable for people.
- Common methods are text substitutions (
name [at] domain [dot] com), HTML entities, JavaScript assembly, images and contact forms. - No method is perfect. Stronger hiding also makes the address harder for real visitors to use.
- If you are prospecting, a domain search and a verifier are more reliable than decoding pages by hand.
What is email address obfuscation?#
Email address obfuscation means changing how an address appears on a page so that simple bots cannot harvest it. The goal is to cut spam sent to published addresses. The address stays readable for people, either as it is or after a small step such as clicking a button.
Site owners use it for contact pages, team pages and staff directories. Prospectors run into it when an email-extraction attempt returns nothing, or returns a strange string instead of a name.
Common email address obfuscation techniques#
Here are the main methods, from simplest to most involved.
| Technique | Example | Human effort | Bot resistance |
|---|---|---|---|
| Text substitution | name [at] company [dot] com | Retype the address | Low |
| Spaces or dashes | n a m e @ company . com | Retype | Low |
| HTML entities | @ for @ |
None | Low to medium |
| Reversed text with CSS | Text written backward and flipped by CSS | None | Medium |
| JavaScript assembly | Address built in the browser at load | None | Medium |
| Image of the address | A picture instead of text | Retype | Medium to high |
| Contact form | No address shown | Fill a form | High |
Text substitution#
The oldest trick replaces @ with "at" and . with "dot". Almost every reader understands it. Many scrapers do too, because they search for these patterns.
HTML entities#
Characters can be written as codes. The browser shows the correct address, but the source code looks different. Modern scrapers decode entities, so this adds little protection.
JavaScript and server-side rewriting#
Some sites assemble the address with a script, or rewrite it on the server. Cloudflare's email address obfuscation feature does this: it rewrites addresses in the page HTML into an encoded form and loads a small decode script, so browsers reveal the address while scrapers that read raw HTML see only the encoded version. Addresses in some places, such as inside scripts or certain attributes, are not covered.
Images and forms#
An image of the address blocks text scrapers but blocks screen readers too, which is a problem for accessibility. A contact form hides the address completely, but visitors lose the ability to copy it or use their own mail app.
Does obfuscation work?#
It cuts simple harvesting. It does not stop a determined bot. A scraper that runs the page like a browser sees the final address. Every method also costs real people something. Retyping a spaced-out address creates typos. Typos create bounces. A plain-text address is easy to pull from a page with an email extractor.
For site owners, a contact form with spam protection is usually the better trade-off.
How prospectors deal with obfuscated emails#
If you need a business contact, hand-decoding is slow and error-prone. Use faster, cleaner paths instead.
- Search by domain. A domain search returns the addresses known for a company, with their sources.
- Use a name and domain. An email finder works out the likely address from a person's name.
- Learn the pattern. One confirmed address reveals the format for everyone else, so check a company email pattern.
- Verify the result. An email verifier confirms the address can receive mail.
If you do decode an address by hand, verify it. A transcription mistake is easy to make.
Respect privacy and rules#
A hidden address is a signal. The owner prefers not to be contacted by automated means. Laws such as the GDPR in Europe often treat business contact data as personal data. Have a real reason to write. Say who you are. Honour opt-outs. When in doubt, use the contact form.
Tips for site owners#
- Use a contact form with a spam filter for general enquiries.
- Prefer a role address such as
contact@for public pages, not a personal one. - If you must show an address, use server-side rewriting rather than a visible text trick.
- Provide an accessible alternative for screen reader users.
- Monitor the inbox, because any published address will receive spam over time.
A short test you can run#
Open a contact page and view its source. Search for the @ sign. If you find it, the address is plain text. If you do not, look for words like "at" or odd codes. This tells you which method the site uses. Then pick the fast path: a domain search. It is quicker than reading code.
FAQ#
What is the point of email address obfuscation?#
It tries to stop automated harvesters from collecting addresses for spam, while keeping the address usable for visitors.
Is "name [at] domain [dot] com" still effective?#
It stops only the simplest scrapers. Many tools recognise the pattern.
Can I scrape obfuscated emails legally?#
It depends on where you are, what data you collect and how you use it. Take legal advice before collecting contact data at scale.
Do images hurt accessibility?#
Yes. An image of an address is not readable by a screen reader unless it has a text alternative, which defeats the purpose.
What is the best way to find a business email without scraping?#
Use a domain search or an email finder, then verify the result.
Skip the decoding#
Let Tomba do the heavy lifting. Use the email finder to turn a name and a domain into a verified address.
// start free
See who Tomba finds at any company
Type a company's domain to see its people, their roles and verified work emails, each with the pages it was found on. Free account, no card.
Free plan · No credit card required · GDPR & CCPA
// about the author