Skip to content
search-engine-optimizedby Netsolution
  1. Home
  2. Page analysis
  3. Exposed Email Finder

Exposed Email Finder

Find out which email addresses on your site can be picked up by spam harvesters.

Analysis of the page source, comments and undisplayed attributes included — exactly the method of an automated harvester. No address found is kept.

What this tool is for

Bots crawl the web with no other purpose than extracting email addresses. They read the source, spot the strings in address format, and feed lists resold to bulk senders. An address published in the clear generally receives its first unwanted messages within weeks.

This tool reproduces exactly that behaviour on your page. It does not stop at what is displayed: it examines the comments left in the code, the data attributes, the metadata. That is where the addresses nobody suspects exist are found.

The discovery is often surprising. A developer’s personal address forgotten in a comment, a former employee’s address in a configuration file, or the billing address in a document’s metadata. All are harvestable exactly like the one on your contact page.

The simple rule: if an address is in the source, it will be harvested. Being invisible on screen changes strictly nothing.

How to read the results

Addresses in the clear in the text are the most exposed. They are readable by any harvester with no effort at all. They are the ones to deal with first.

Addresses in mailto links are just as exposed, even when the text displayed says only “write to us”. The address sits in the attribute, so in the code.

Addresses in HTML comments are invisible to the visitor and perfectly readable to a bot. They often come from past development work and have no reason to still be there.

Addresses in attributes and structured data are a particular case: they sometimes have a real use, such as a contact address declared in organisation markup. The risk then has to be weighed against the benefit.

Obfuscated addresses are reported as partially protected. The tool says which ones it nevertheless managed to reconstruct — if it can, a serious harvester can too.

Common mistakes

Believing an image protects lastingly. It stops simple harvesters, but text recognition has become trivial. Above all it makes the address unusable for people browsing with a screen reader, and prevents copy-paste for everyone.

Writing “contact at example dot com”. Harvesters have recognised those variants for a long time. You degrade your visitors’ experience without gaining any real protection.

Protecting only the contact page. Addresses slip in everywhere: team pages, signed articles, legal notices, PDF files published online. Check several pages, not only the one you are thinking of.

Leaving development comments in production. They hold more than addresses: internal paths, server names, sometimes credentials. A cleaning pass before going live should be systematic.

Giving up on a form for fear of losing messages. A well-built form, with a visible confirmation and a copy sent to the sender, loses nothing. It does remove the whole problem.

Going further

Frequently asked questions

Is an email address in the clear really harvested?

Yes, and quickly. Bots crawl the web constantly to extract strings matching the format of an email address. The lists built that way are resold. An address published in the clear on a visible page generally starts receiving spam within weeks.

Does writing “contact at example dot com” protect it?

A little, and less and less. Harvesters have long recognised the common variants: at, [at], (at). It filters out the crudest bots, not the rest. And the cost is real: your visitors can no longer click, and screen readers announce an incomprehensible address.

What is the best protection?

A contact form, with no address in the code at all. It is the only genuinely effective method, and also the most comfortable for the visitor. If you absolutely must display an address, an image stays readable to a human — but becomes inaccessible to screen readers, which is a poor trade.

Does JavaScript obfuscation work?

It stops most harvesters, which do not execute JavaScript. It does not stop the more elaborate ones. Its advantage over an image is that it preserves the click and accessibility. It is a reasonable compromise, not absolute protection.

Does data protection law oblige me to publish an email address?

You have to provide a means of contact allowing rights to be exercised, but nothing requires it to be an email address displayed in the clear. A contact form satisfies the obligation. Legally required notices follow the same logic.

Why does the tool find addresses invisible on the page?

Because they are in the code without being displayed: HTML comments left by a developer, data attributes, exposed configuration files, image metadata. Harvesters read the source, not the rendered page. That is precisely what this tool reproduces.