Email Privacy
About Email Privacy
Our Email Privacy Checker scans any webpage to detect if email addresses are publicly exposed in the HTML source code. Exposed email addresses are easily harvested by spam bots and lead to increased spam, phishing attempts, and potential security risks.
Enter a URL
Best practice is to encode or obfuscate email addresses on public-facing web pages, or use a contact form instead. Our tool helps you quickly identify which of your pages have exposed emails so you can protect them.
How to Protect Email Addresses Online
- Use a contact form instead of mailto links
- Encode email addresses using HTML entities
- Use JavaScript to display email addresses
- Consider CAPTCHA-protected contact forms
How to Use the Email Privacy Checker
- Enter the URL of the page you want to scan for exposed email addresses.
- Run the scan and let the tool read through the page's HTML source.
- Review any email addresses it finds written in plain text within the markup.
- For each exposed address, decide whether to remove it, replace it with a contact form, or encode it with HTML entities or JavaScript.
- Re-scan the page after making changes to confirm the address no longer appears in plain, harvestable text.
- Repeat across your key contact, about and team pages, since these are the pages spam bots target most often.
- Check back periodically as new pages are published, since freshly added contact or staff bio pages are a common source of newly exposed addresses.
Related Tools
Frequently asked questions
Is the Email Privacy Checker free?
This tool requires an active one-time membership to use - pay once and unlock this tool plus every other gated tool on the site, no subscription, no ads.
Why does exposing raw email addresses matter?
Plain-text email addresses on a public page are easy targets for spam bots that scrape the web for addresses to add to spam lists - obfuscating or protecting them reduces unwanted spam.
What is the best way to protect an email address on my site?
Common approaches include using a contact form instead of a visible address, encoding the address with JavaScript/HTML entities, or using a CSS-based obfuscation technique - each trades off convenience against bot-resistance.
