Email Obfuscator

What this tool does

Email Obfuscator converts a plain email address into several scraper-resistant HTML forms, numeric HTML entities, a JavaScript document.write snippet, and CSS-reversed text with direction override, each of which renders normally to human visitors while defeating the simple regex-based scraping that drives most automated email harvesting.

Publishing a plain "name@domain.com" anywhere on a public web page is an open invitation to the simple regex-based scrapers that make up the vast majority of automated email-harvesting traffic, feeding directly into spam lists.

This tool converts a plain address into several forms that still display and work correctly for a human visitor (and in most cases, still function as a clickable mailto: link) while defeating naive text-scanning scrapers: numeric HTML entities, a JavaScript document.write snippet that only renders after JS executes, and CSS-reversed text that looks correct visually but is reversed in the raw HTML source.

How to use Email Obfuscator

1. Enter the Email address to protect.
2. Review the several generated obfuscated forms.
3. Copy whichever version fits your page (plain HTML entity encoding is the simplest, broadly compatible option).
4. Paste it into your page’s HTML in place of the plain address.

Tips for better results

• HTML entity encoding is the simplest and most broadly compatible option, it works even with JavaScript disabled, since the browser decodes the entities automatically when rendering.
• The JavaScript document.write version is the most resistant to simple scrapers, since most basic address-harvesting bots only fetch and scan raw HTML without executing JavaScript at all, but it requires JS to be enabled to display.
• None of these methods is foolproof against a sophisticated, determined scraper; they specifically raise the cost of harvesting enough to deter the simple bots responsible for most spam collection.
• For the strongest protection, consider using a contact form instead of publishing a raw address anywhere at all, removing the target completely rather than just obscuring it.

Common use cases

• Publishing a contact email on a website’s "About" or "Contact" page without feeding spam-harvesting bots.
• Protecting an email address in a forum post, comment, or public document.
• Understanding the different common techniques used to obfuscate emails from scrapers.
• Adding a lightweight layer of spam protection without building a full contact form.

Common mistakes to avoid

• Treating obfuscation as complete, guaranteed protection; it raises the cost of automated harvesting but doesn’t stop a determined, sophisticated scraper specifically targeting your page.
• Relying solely on the JavaScript-based method for a page where JS might be disabled or blocked; pair it with a fallback (like HTML entity encoding) if broad compatibility matters.
• Forgetting that even an obfuscated address is still technically visible to a human who inspects the page source carefully; this deters automated bots, not a manually curious human reader.