An email pattern is the format a company uses for its addresses: first.last@, flast@, first@ and so on. Knowing it tells you which address to try for a new contact, and which addresses on a catch-all domain are worth resolving.
What a pattern result looks like
Each pattern is shown with an example address and, when known, how common it is at the company. For a made-up company it might look like this:
| Pattern | Example | Share |
|---|---|---|
first.last | jane.doe@acme.com | 78% |
flast | jdoe@acme.com | 15% |
A label tells you where the information comes from:
- Based on our data analysis: from filtrat's own data.
- Based on available public market data: from publicly available sources.
- Based on our verification data: real addresses at this domain that were verified before. Then example addresses are shown instead of patterns.
If nothing can be found, you see Email pattern data not available for this domain.
Where to look one up
| Where | How |
|---|---|
| Single check | After a verification, the Email pattern section at the bottom of the domain intelligence panel. Press Search email pattern if none is shown yet. |
| Domain intel | Inspect a domain in Domain intel; the report ends with the Email pattern section. |
| Bulk verification | Find patterns (N) looks up the patterns of all catch-all domains in the job at once. Domains that already have a pattern are skipped. |
| Email finder | Known patterns under every result, and Pattern on the email found. |
What it costs
15 per domain, charged only when a pattern is found. If nothing is found, nothing is charged.
Once a domain's pattern is known, it's kept. Seeing it again later, in any tool, costs nothing. In a bulk job, the confirmation dialog shows how many domains it will search, the total cost and your balance before you confirm.
How to use a pattern
On catch-all domains
A catch-all domain accepts any address, so verification alone can't tell jane.doe@ from jdoe@. With the pattern:
- Look up the pattern for the catch-all domains in your list.
- Resolve the addresses that match the main pattern first. They're the ones most likely to come back deliverable.
- Consider addresses that don't match only if the person is important; they are more often wrong.
See Resolve catch-all addresses.
When writing to someone new
Build the address from the pattern, then verify it before sending. Or let the email finder do both: it uses known patterns and confirms the address with the mail server.
A company can use more than one format, for example older staff on flast@ and newer staff on first.last@. The share next to each pattern shows which is most common, but always verify the address you build.