How to filter email addresses by domain

Filter extracted emails by domain, subdomain or suffix such as .edu. Use concrete examples to combine domain, keyword and exclusion settings correctly.

This guide uses Email Extractor to apply domain and keyword filters to extracted page results.

Contents

Decide whether to filter a website or an email domain#

The domain of a source webpage and the domain after an email’s @ are different things. A directory hosted on directory.test may list addresses from dozens of organizations. If you want only addresses ending in studio.test, use an email-domain filter rather than assuming the webpage host determines the result. Conversely, scanning studio.test can still return a supplier address at another domain. Defining which domain matters prevents a common mistake when building a focused list. The examples in this guide concern filtering extracted address values in the page-scanning workflow.

Enter a domain without the @ symbol#

Open the Premium Advanced options and enter the domain as a plain value, such as studio.test. Do not paste a full webpage URL, path or leading @ into that field. The current domain filter accepts both the named domain and its subdomains, so an address at team.studio.test can match a studio.test filter. If your task requires only the exact main domain, inspect the returned domains and separate any subdomain entries during review. The table below gives the expected meaning of several example settings and helps distinguish a domain filter from the other controls.

Example domain and suffix filters
SettingExampleExpected scope
Domainstudio.testAddresses at studio.test and its subdomains
Suffix.eduAddresses ending in .edu
Included wordsteam,salesAn address containing both team and sales
Excluded domainsvendor.testMatching addresses excluded from the reviewed result

Use a suffix when the ending is what matters#

Use the suffix field for a single ending such as .edu or .org. This is useful when the task concerns an email-domain ending rather than one organization. The popup expects one suffix value; a comma-separated list should not be interpreted as a supported OR search. For several independent suffix groups, run separate focused scans or organize the exported result by domain afterward. A suffix match describes the spelling of an address. It does not establish that the address belongs to a current employee, that the organization is relevant, or that the mailbox is deliverable.

Combine included words carefully#

Included words are comma-separated, but the current popup requires every supplied word to occur in the address. For example, team,sales matches a value containing both words, not every team address plus every sales address. This can be useful for a specific naming pattern, but it is easy to make a filter too strict. Begin with one clear requirement and check a known result before adding more conditions. If you want several independent groups, separate them into reviewable runs instead of assuming the input behaves like a search-engine expression.

Exclude unrelated domains and system addresses#

An exclusion list can remove known domains that are not relevant to your list. The system-address option can also hide common automated-mailbox patterns. These controls solve different problems: a company domain may be relevant while its noreply address is not, and a normal-looking address at an unrelated provider may still be unwanted. Review a small sample of the removed or missing entries by temporarily relaxing one setting at a time. The filters are text rules applied to the result list, so unusual naming patterns deserve a source check rather than an automatic conclusion about the owner.

Test with a known email address before a larger run#

Choose a page with one address you can identify, then scan with the simplest relevant settings. Add a domain, suffix or word condition one at a time and confirm that the known value remains when it should. This turns troubleshooting into a comparison rather than guesswork. If a result disappears only after you add a filter, investigate the filter before changing browser permissions or scan modes. If no mode can read the page even without filters, use the missing-results guide. Keep the successful settings with the project so later scans are easier to reproduce.

Export a focused list and preserve useful context#

After filtering, select the addresses required by the task and review their sources. Export TXT for a plain list or CSV and XLSX for spreadsheet work; HTML and JSON are also supported. Do not assume a filter changes every other scan workflow or permanently deletes saved source records. Check the view you are working in and the selection shown by its export dialog. A focused file is easier to review, and retaining a source URL helps explain why an address was included when the list is used later.

Put this workflow into practice

Read the related documentation for the product controls and limits used here. Contact support if you need help with a specific result.

Email Extractor

Download Email Extractor

Find email addresses on webpages and turn your results into a list you can use.

Add to ChromeAdd to EdgeAdd to Firefox