Яндекс.Метрика

Plaintext email checker

Find plaintext email addresses exposed in a webpage source.

0 of 0 ratings

Last submissions

What this checker does

The plaintext email checker scans the HTML source of a webpage and lists every email address that appears in readable text. It helps you see which addresses are visible to anyone who views the page source, including automated bots that harvest addresses for spam.

When you enter a URL, the tool fetches the page and extracts email-like patterns from the raw HTML. The result shows the addresses found, so you can judge whether your contact details are too exposed.

Why plaintext email addresses are a problem

Email addresses written directly into HTML are easy to collect. Spammers and scrapers routinely crawl websites looking for patterns like name@example.com. Once an address ends up on a list, it tends to receive unwanted mail for years, and filtering it out becomes difficult.

Beyond spam, exposed addresses can be used for phishing. An attacker who knows your support or sales address can craft messages that look more convincing. The same information can feed targeted attacks against your team.

Plaintext addresses also affect professionalism. Visitors who see an unprotected address may assume the site is not actively maintained or that security was not considered during development.

How email addresses end up in page source

There are several common ways addresses become visible in HTML:

  • Contact pages: an address typed directly into a paragraph or list.
  • Footer links: a mailto link with the address in plain text.
  • Structured data: JSON-LD or microdata containing an email field.
  • Comments and hidden blocks: addresses left in HTML comments or hidden elements that still ship to the browser.
  • Forms: placeholder text or default values that include an address.

Some of these are intentional, but others are leftovers from templates or editing. The checker reveals all of them so you can decide what to keep.

Reading the results

The tool lists the addresses it finds. It does not tell you whether an address is valid, whether it belongs to a real person, or whether it is already on spam lists. It simply shows what is present in the source.

If the list is empty, the page likely uses an obfuscation technique, an image, or a contact form instead of plain text. If the list contains unexpected addresses, check whether they come from templates, test content, or third-party embeds.

Practical ways to reduce exposure

You do not always have to remove every address. A public support address may be deliberate. The goal is to make exposure a conscious decision rather than an accident.

  • Use a contact form instead of displaying an address directly. The form can route messages without revealing the destination.
  • Obfuscate addresses with character encoding, JavaScript rendering, or a CAPTCHA-protected reveal. These methods are not perfect but raise the cost for simple scrapers.
  • Use role-based addresses such as support@ or sales@ and keep personal addresses out of public pages.
  • Review hidden content and remove addresses from comments, unused blocks, and development leftovers before publishing.
  • Separate public and private contacts so that the address you publish is not the one tied to critical accounts.

Limitations to keep in mind

The checker looks at the HTML returned for the URL you provide. It does not execute JavaScript, so addresses injected at runtime by scripts may not appear. It also does not crawl linked pages or check other parts of your site.

Detection depends on pattern matching. Addresses split across HTML elements or written in unusual formats may be missed. Conversely, strings that look like addresses but are not real contacts may be reported.

Use the results as a starting point for review, not as a complete audit of your site’s exposure.

When to run this check

Run it after publishing a contact page, after changing templates, or whenever you review site security. It is also useful when onboarding a site you did not build, because it quickly shows whether addresses were left in the source.

Combine the result with other checks, such as reviewing form endpoints and ensuring HTTPS is used, to build a fuller picture of how your site handles visitor contact data.

Similar tools

Website text extractor

Extract the visible text content of a webpage from its source code in one click.

286
Safe URL checker

Check whether Google flags a URL as safe or potentially unsafe for visitors.

12
SPF record checker

Find and validate the SPF record of a domain.

0

Popular tools