Email Privacy
Verify that the email providers you use are in charge of your privacy by using Our Email security checker. Copy the address of your email service provider into the program and then click the "Submit" button to determine.
- 100% Free
- Files stay private
- Works in your browser
Page URL
Enter a page and we'll scan its HTML for email addresses that scrapers could harvest.
We fetch the page's HTML on our server and scan it for mailto: links and plaintext addresses. It only sees the page's initial source (addresses injected later by JavaScript, or living on other pages, aren't counted), so a “safe” result covers this page only.
How it works
Enter a page URL
Type the address of the page you want to scan, for example a contact page, into the URL to scan field.
Press Scan page
Press Scan page and our server fetches the page and looks for mailto: links and plaintext email addresses in its source.
Read the risk verdict
See a risk level from Safe to High risk. If addresses are found, copy each one, or use Copy all when more than one is listed.
Enter a page URL and this tool reads its HTML the way an automated scraper would, then reports every email address sitting in the open. Spam bots crawl the web for exactly these addresses, so seeing what they'd collect from your contact or about page tells you whether you've handed them a mailing list. Email Privacy runs that scan in a couple of seconds and shows a plain risk verdict plus the actual addresses it found.
What Is Email Privacy?
Email Privacy is a free tool that fetches a single page from our server and inspects its source for exposed email addresses. It looks in two places: mailto: links in the markup, and plain-text addresses anywhere in the raw HTML matched by an email pattern. It also checks the visible body text for the common "name at domain dot com" obfuscation people use to dodge harvesters. Each unique address is counted once, and the result splits the total into how many came from mailto links versus how many appeared as plain text.
The risk verdict is a simple count-based heuristic: zero addresses returns a safe state, one or two is low, three to five is medium, and more than five is high. A page leaking more addresses is a bigger prize to a scraper. A contact page with fifteen staff emails matters more than one with a single support address.
Who Benefits from This Tool
- Site owners: check whether your contact, team, or about page is quietly serving addresses that will end up on spam lists.
- Web developers: confirm a contact form or obfuscation method actually kept raw addresses out of the shipped HTML.
- Marketing and comms teams: audit a staff directory or press page before it starts drawing junk mail.
- Privacy reviewers: flag pages that expose personal or internal addresses during a hygiene pass.
- Agencies and freelancers: run a quick check on a client site and show them what's leaking.
Key Features
- Server-side scan: our server fetches the page, so you see the same source a crawler downloads, not a browser-rendered view.
- Mailto and plain-text detection: it catches both clickable mailto: links and bare addresses written into the text.
- Obfuscation check: it notes when a page uses the "at ... dot ..." trick, so you know a light defense is present.
- Deduplicated count: an address repeated across the page counts once, so the exposed number reflects distinct addresses.
- Clear risk verdict: a color-coded safe, low, medium, or high rating shows how exposed the page is.
- Copyable address list: the addresses found appear in a monospace list you can copy for follow-up.
How to Use
- Paste the full URL of the page you want to check, including the https:// prefix.
- Press Enter or run the scan and give our server a moment to fetch and parse the page.
- Read the risk verdict at the top: safe, low, medium, or high.
- Check the counts for exposed addresses, mailto links, and plain-text matches.
- Review the list of addresses the scan pulled out and copy any you need to fix, then follow the advice line.
Common Use Cases
- Auditing a contact or support page before launch to confirm it isn't publishing raw addresses.
- Checking a team or staff directory that lists many people by name and email.
- Investigating why a specific published address suddenly started getting spam.
- Verifying that an obfuscation or form swap actually removed addresses from the HTML.
- Spot-checking a client's pages during a privacy or SEO review.
Tips and Best Practices
- Scan the pages most likely to leak (contact, about, team, and footer-heavy pages) rather than a random URL.
- If addresses must stay public, prefer a contact form or a mailto behind a click, which keeps raw text out of the source.
- Obfuscation like "name [at] domain [dot] com" slows simple bots but won't stop a determined one; treat it as a speed bump.
- Re-scan after a redesign or CMS migration, since templates often reintroduce addresses that were cleaned up before.
- Remember the risk tier reflects how many addresses leak, not whether they should be public.
Limitations and Notes
This scan covers one page at a time (the exact URL you enter), not your whole site, so run it against each page you care about. It reads the HTML our server receives, which means addresses injected by JavaScript after load may not appear, and pages behind a login return a block page instead of real content. The plain-text pattern can occasionally flag something that looks like an address but isn't, or miss addresses split across HTML tags or assembled in script. The obfuscation check only recognizes the written "at / dot" style, not addresses hidden inside images or built in code. And the risk rating is a straight count. It reflects how many addresses the page exposes, not whether any of them is sensitive.
FAQs
It fetches the page from our server and inspects the raw HTML. It reads mailto: links directly, scans the rest of the source with an email pattern for plain-text addresses, and removes duplicates so each counts once. It also checks the visible text for the "at ... dot ..." obfuscation style.
It's based purely on how many distinct addresses the page exposes: zero is safe, one or two is low, three to five is medium, and more than five is high. It measures exposure volume, not whether any particular address was meant to be private.
It means the scan found no addresses in the source it downloaded. Addresses built by JavaScript after load, hidden in an image, or placed behind a login can still be missed, so a safe result is strong evidence rather than an absolute guarantee.
It helps against basic scrapers, and this tool will note when a page uses it. But it's a light defense that more capable harvesters can reassemble. For anything you truly want off spam lists, a contact form or a form-protected address is more reliable.
Not usefully. The request comes from our server without your session, so a protected page typically returns a login or block page rather than the real content. This tool works best on publicly reachable URLs.
The plain-text scan matches anything shaped like an address in the source, so a sample address in example text, a third-party widget, or an embedded script can appear. Open the page source and search for the address to see where it came from before treating it as a leak.