Email Obfuscator

Why Obfuscate an Email on the Web?

Spam bots continuously scrape webpages for email addresses. A plain mailto:[email protected] in your HTML becomes mailing-list fodder within hours of being indexed. Obfuscation makes the address difficult for naive scrapers to parse while still being reachable by real visitors.

Methods in This Tool

• HTML entities — Each character becomes &#NN;. Browsers render it normally; many scrapers skip it. Cost: slightly bigger markup.
• Reversed + CSS — The string is stored backwards in the DOM with direction: rtl. Humans see it upright; simple regex scrapers see nonsense.
• Base64 + JS decoder — The address is base64-encoded and decoded by a tiny inline script on page load. Scrapers that don't execute JavaScript never see the plaintext.
• ROT13 — Each letter shifted 13 places. Obvious to humans once they know, invisible to naive matchers.
• [at] / [dot] — Human-readable form: contact [at] example [dot] com. Easy to copy, easy to read, invisible to regex.

Which Method to Pick?

• If you want the address to stay clickable: HTML entities or Base64 + JS.
• If you want it visible but not clickable: Reversed + CSS, or [at]/[dot].
• If you care about JavaScript-disabled visitors: avoid Base64.
• If you care about SEO: all methods are invisible to search engines' email extractors, which is the point.

Limitations

Modern sophisticated scrapers execute JavaScript and recognize entity encoding. Treat obfuscation as a reduction of spam volume, not a full defence. For mission-critical inboxes, pair obfuscation with a contact form and a catch-all filter. Runs entirely in your browser — your email is never logged.