Hide your email address from spam bots without hiding it from people. Enter the address, optional link text and subject, and choose a technique — HTML entities, ROT13 with JavaScript, assemble-on-click or reversed CSS text — then copy the snippet into your page. Each method's trade-offs for accessibility and JavaScript are explained. It's free, runs in your browser, and the address isn't sent anywhere.
| Method | Needs JS | Clickable | Screen reader |
|---|---|---|---|
| HTML entities | No | Yes | Yes |
| ROT13 + JS | Yes | Yes | Yes |
| Assemble on click | Yes | Yes | Partly |
| CSS reversed | No | No | Reads reversed |
HTML entities for the best accessibility with no JavaScript; ROT13 or assemble-on-click for stronger protection on pages that already use JavaScript.
No. Scrapers that run a real browser can read any address a visitor can see. It cuts the bulk of automated harvesting.
Not fully — copying gives reversed text and it can't be a clickable link. It's included for completeness.
Yes, it's added to the mailto: link.
No. The snippet is generated in your browser.
Spam harvesters mostly scan page source for text that looks like an email address. Four techniques keep the address out of that source in different ways. HTML entity encoding writes every character as a numeric reference, alternating decimal and hexadecimal so a single pattern doesn't catch it; browsers and screen readers decode it normally and it needs no JavaScript. ROT13 stores the mailto link rotated by 13 letters and a tiny inline script decodes it into the link after the page loads. Click-to-assemble keeps the user and domain reversed in data attributes and only builds the mailto: link when it's clicked. CSS reversal stores the address backwards and displays it forwards with bidi override, which defeats scrapers but makes copied text come out reversed and can't be a link. The page explains each trade-off for accessibility and no-JavaScript visitors. None stop a scraper running a full browser, which is stated rather than overpromised.