To find email addresses from a domain for free, read the pages where businesses publish them: the contact page, the about page, the footer, the privacy notice and terms, structured data in the page source, and the business's own social profiles. Those methods find the addresses the business chose to publish, which are also the ones it expects to receive mail on. Pattern guessing (firstname.lastname@) is a last step and only safe after an SMTP check, and never on a catch-all domain.
This is the pillar guide for our email finding posts. It ranks every method by reliability, shows what each one finds on a fictional site, and ends with the bulk version for hundreds of domains.
Methods ranked by reliability
Reliability here means two things: the address is real, and the business intended it to be used for the purpose you have in mind.
| Rank | Method | What it usually finds | Reliability | Effort |
|---|---|---|---|---|
| 1 | Contact page | General enquiries, sales, bookings inboxes | High | Low |
| 2 | Footer and header | The main published address, repeated sitewide | High | Low |
| 3 | Legal pages (privacy, terms, imprint) | A data contact and a general business address | High, but often the wrong inbox for sales | Low |
| 4 | Structured data (JSON-LD, microdata) | The address the site declares for search engines | High when present | Medium |
| 5 | Other pages (team, careers, PDFs, blog author boxes) | Named staff, recruitment, press | Medium; check the purpose | Medium |
| 6 | The business's own social profiles | The same address or a different one for social enquiries | Medium; may be out of date | Medium |
| 7 | WHOIS and RDAP | Mostly redacted or a privacy relay | Low | Low |
| 8 | Pattern guessing | A named person's probable address | Low until verified | Medium |
1. The contact page
Most business sites have one, under a URL such as /contact, /contact-us, /get-in-touch or a local language equivalent. Read the visible text and the link targets. A mailto: link is a deliberate statement that the address accepts mail.
Note what the page says each address is for. "For quotes, email quotes@" tells you more than any verification check about whether a sales email belongs there.
Some contact pages carry only a form. That is a choice the business has made, and the form may be the right route. We discuss this in why scrapers miss emails behind Cloudflare protection, which also covers forms-only sites.
2. The footer and header
Small businesses often put one address in the footer on every page. It is the most consistently published contact and the least likely to be stale, because the site owner sees it every time they look at the site.
3. Legal pages
UK legal pages are a reliable place to look for a reason. Regulation 6 of the Electronic Commerce (EC Directive) Regulations 2002 requires an online service provider to make available its name, geographic address and "details of the service provider, including his electronic mail address", so a UK business site that sells or advertises services should show one somewhere. Privacy notices also usually name a contact for data protection requests.
Be careful with what you find here. An address published for data protection requests (privacy@, dpo@, gdpr@) is for data subjects exercising their rights, not for sales pitches. Sending outreach there is a fast way to generate a complaint.
4. Structured data
Many sites describe themselves to search engines with Schema.org markup. The LocalBusiness type inherits an email property from Organization, along with telephone, address and contactPoint. View the page source and search for application/ld+json. A fictional example:
{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"name": "Oakline Joinery",
"url": "https://oakline-joinery.example/",
"email": "[email protected]",
"telephone": "+44 1632 960000",
"sameAs": ["https://www.facebook.com/oaklinejoinery.example"]
}
This is high quality evidence because the site owner (or their developer) wrote it for machines. The sameAs list is also a reliable pointer to the business's own social profiles.
5. Other pages and documents
Team pages, careers pages, press pages, blog author boxes and PDFs (brochures, price lists, menus) often carry addresses that never appear on the contact page. They are real, but check the purpose: jobs@ is for applicants, press@ is for journalists. Named staff addresses are personal data under UK GDPR, which changes your obligations (see the compliance section below).
6. Social profiles
Follow the social links from the site itself rather than searching by name, so you know the profile belongs to the same business. Facebook pages and Instagram business profiles often list an email in the about or contact section. Treat these as slightly less reliable: profiles get set up once and forgotten, so the address may belong to an old domain or a former employee.
7. WHOIS and RDAP
Public domain registration data used to show the registrant's email. Since 2018 most registrars redact personal contact details, and many domains use a privacy service that shows a relay address instead. When an address does appear it is often the web agency or the registrar. WHOIS is useful for checking who controls a domain, not for finding a sales contact.
8. Pattern guessing
If one named address is published, say [email protected], you can infer a pattern (firstname.lastname) and guess others. This is a hypothesis, not a finding. Before using a guessed address:
- Base the pattern on at least one published example on the same domain, not on what is common elsewhere.
- Verify it with an SMTP check, described in how to verify an email without sending.
- If the domain turns out to be catch-all, stop. A catch-all server accepts every guess, so the check proves nothing. See email verification results explained for how to read each verdict.
A guessed named address is personal data, and the person did not choose to publish it. That weighs against you in a legitimate interests balancing test, so prefer a published role address where one reaches the right function, and treat guessing as the exception.
A shortcut: search engines
Before opening pages one by one, ask a search engine what it has already indexed. A query such as:
site:oakline-joinery.example "@oakline-joinery.example"
returns pages on the domain where the address text appears, including PDFs and old pages that are no longer linked from the menu. Add -site: to look for the domain's addresses mentioned elsewhere, for example in a trade directory or a council supplier list:
"@oakline-joinery.example" -site:oakline-joinery.example
Two cautions. Search results lag behind the live site, so an address found this way may have been removed for a reason; always confirm it on a current page. And addresses found on third-party sites tell you the address existed, not that the business wants it used for sales. Record the page you found it on, the same as any other source.
A shortcut: the browser's own tools
On a single page, the quickest check is the browser itself. Press Ctrl+U (or Cmd+Option+U on a Mac) to view the source and search for @ and mailto:. If the source shows [email protected] but the visible page shows an address, the site uses Cloudflare obfuscation, and what you see on screen is the published address. If neither shows anything, open the developer tools, reload the contact page and check whether the address is loaded by a script after the page appears.
What these methods find on one fictional site
Running every method against oakline-joinery.example:
| Address | Found on | Inbox purpose | Use for outreach? |
|---|---|---|---|
[email protected] | Footer, contact page, JSON-LD | General enquiries | Yes |
[email protected] | Contact page ("for quotes") | Sales | Yes, often the best fit |
[email protected] | Privacy notice | Data protection | No |
[email protected] | Careers page | Recruitment | No |
[email protected] | Team page | Named person (director) | Only with a lawful basis and privacy information |
[email protected] | Old Facebook page | Unclear, different domain | Check before use |
[email protected] | Pattern guess | Unknown | Only if verified on a non catch-all domain |
The useful output is not a pile of addresses but a short list with a source and a purpose for each.
Hidden and obfuscated addresses
Some addresses are on the page but not in the raw HTML:
- Cloudflare email obfuscation. Cloudflare's Email Address Obfuscation is enabled automatically for new sites. Visitors see the address; tools that read only the HTML see
[email protected]. A browser-rendered view shows the real address. - Text obfuscation.
hello [at] oakline-joinery [dot] exampleor similar. Readable by people and by any extractor that understands the convention. - JavaScript assembly. The address is built by a script. Needs a rendered page.
- Images. The address is a picture. Readable by people; skip it in automated work rather than try to defeat it.
We cover each in detail in Cloudflare email protection and why scrapers miss emails.
Filtering junk
Any automated search of a domain picks up strings that look like addresses and are not: image files ([email protected]), placeholder text ([email protected], [email protected]), the web developer's address in a credit line, and tracking or error-reporting addresses from third-party scripts. Filter these before verification, and drop free-mail addresses that belong to someone other than the business unless the business clearly uses them.
The bulk version: many domains
Doing this by hand works for ten domains. For five hundred, the same steps become a crawl:
- Clean the domain list: strip paths and tracking parameters, lower-case, remove duplicates and
www.variants. - Fetch each homepage, then the contact, about, footer-linked and policy pages, before anything else.
- Read text,
mailto:links and structured data on each page; decode common obfuscation; render the page in a browser when the HTML is an empty shell. - Filter junk and label inbox purpose.
- Keep one row per business with each address, the page it was found on and the purpose.
- Respect
robots.txt, keep request rates low and stop on blocks.
The full workflow is in extract emails from a list of websites.
The compliance part
Finding a published address is one thing; emailing it is regulated. In the UK, according to the ICO's business-to-business marketing guidance:
- PECR's email marketing rule does not apply to corporate subscribers (companies, LLPs, public bodies), but you must not conceal your identity and must give a valid address to opt out. Keep a do-not-email list and screen new lists against it.
- Sole traders and some partnerships are individual subscribers. You need consent or the soft opt-in. If you are unsure which a business is, treat it as an individual.
- An address that identifies a person, such as
sam.reid@, is personal data under UK GDPR even in a business context. You need a lawful basis (legitimate interests needs the three-part test), you must provide privacy information, and an objection to direct marketing is absolute.
Other countries differ. Germany generally requires prior consent for advertising email, including to businesses, and the US CAN-SPAM Act has its own requirements. Respect each website's terms and robots.txt when collecting, and collect only what you need.
How Map Extract helps
The email extractor does the manual method above across many sites. It is not a separate database lookup: addresses come from the website crawl and from the business's own public social profiles. The crawler prioritises contact, about, footer and policy pages, reads visible text, links and structured markup, and decodes common address obfuscation. Bundled filters remove disposable, adult and junk addresses, and your own blocklists apply on top.
Each address gets an inbox purpose label (general enquiries, sales, bookings, support and so on), and privacy, abuse, unsubscribe and no-reply inboxes are marked as excluded from outreach. Up to ten addresses are kept per business, each with its source, so you can see where it came from. The website data extractor runs the crawl itself, with Fast, Balanced and Deep levels, and records structured data fields such as the JSON-LD email alongside the rest of the business record.
What it does not do: it works from published addresses rather than guessing from name patterns, it cannot find addresses a site does not publish, addresses shown only as images are likely to be missed, and it does not decide whether you may email them. Verification is a separate step with its own email verifier, and coverage depends on what each site makes public.
Public business and social results the app collects are uploaded automatically to Map Extract's servers while it is licensed and running; the privacy notice explains this.
Related guides
- Extract emails from a list of websites: the bulk workflow.
- Cloudflare email protection and scraping: obfuscation and forms-only sites.
- List the likely email addresses for a name at a company
- Email list cleaner
Key takeaways
- The best addresses are the ones the business published on purpose: contact page, footer, structured data.
- Legal pages are reliable but often point to the wrong inbox for sales; never pitch a privacy contact.
- WHOIS is mostly redacted and rarely useful for outreach.
- Pattern guesses need an SMTP check, and catch-all domains make the check meaningless.
- Keep the source page and inbox purpose for every address.
- Finding an address does not give you permission to email it; check PECR and UK GDPR first.
Frequently asked questions
How can I find all email addresses on a domain for free?
Start with the pages a business uses to publish contact details: contact, about, footer, privacy notice and terms. Then check the page source for structured data and mailto links, the company's own social profiles and any PDFs such as brochures or price lists. That finds the addresses the business chose to publish. There is no free, legitimate way to list every mailbox on a domain.
Can I see email addresses through WHOIS?
Rarely. Since 2018 most registrars redact personal registrant contact details from public WHOIS and RDAP results, and many domains use a privacy service whose relay address forwards to the owner. Where an address does appear it is often the web developer or registrar, not the business. Treat WHOIS as a last resort and never as a sales contact.
Is guessing email addresses from a pattern reliable?
Only after verification. A pattern such as firstname.lastname is a hypothesis built from one or two published examples. An SMTP check can confirm it on domains that reject unknown recipients, but on catch-all domains nothing confirms it. Guessed addresses on catch-all domains cause more bounces than any other source, so hold them back or skip them.
Is it legal to collect email addresses from business websites in the UK?
Collecting published business contact details is common, but what you do next is regulated. PECR lets you email corporate subscribers without consent if you identify yourself and offer an opt-out, while sole traders and some partnerships need consent or the soft opt-in. Named addresses are personal data under UK GDPR, so you need a lawful basis and must give privacy information.
Why does a website show [email protected] instead of an address?
That placeholder comes from Cloudflare's email address obfuscation, which replaces addresses in the page HTML and decodes them in the visitor's browser with a short script. A person sees the real address; a tool that only reads raw HTML sees the placeholder. A browser-rendered crawl, or simply opening the page, shows the address the business published.
Sources
Written by the Map Extract editorial team. Found an error? Email [email protected] and we will check and correct it. How we research guides: editorial policy.