Email Pattern Guesser
Guess a company's email format (first.last@, flast@…) and generate a contact's likely address. Free, no sign-up.
At a glance
Likely addresses
Enter a first name, last name and valid domain.
Need the 98% verified address? Run the verification in SoContact.
Open in SoContactPractical guide
Inferring an email pattern
Understand the need
The pattern generator suggests addresses from first name, last name and domain. Results are structural hypotheses, not mailbox verification or permission to send.
Practical example
For Camille Moreau at a company using acme.fr, several combinations may exist. A known example for Jean Dupont can suggest a convention, but a company may use several formats across employees or subsidiaries.
Method and checkpoints
Enter the person’s fields and domain, optionally adding a known address with the corresponding name. Calculation happens in the browser. Results update and can be copied for subsequent verification. Start by defining the question you want to answer and information already available. Use a straightforward case to check your understanding, then add organizational specifics. Compare the result with a known reference where possible. Missing information should be distinguished from a negative result, and an estimate should not be presented as a measurement. Record parameters and limitations so a colleague can reproduce the reasoning without interpreting the outcome differently. If assumptions change, perform a new assessment rather than comparing results produced under incompatible conditions.
Limits and decision criteria
Compound names, accents and namesakes can alter conventions. The displayed percentage estimates pattern plausibility; it is not an SMTP test. Separately verify address existence and status before campaign use. Before using the outcome to decide, verify its scope. Campaign preparation includes independent steps: targeting, contact quality, messaging, technical configuration and follow-up. No isolated indicator guarantees overall success. Relate this page’s information to your team’s actual context. Do not collect additional personal data without a clear purpose. Examples are educational and animations use fictional profiles. For account conditions, offers or available capabilities, always confirm information in the SoContact application before committing. Consider who will act on the result and what checks are required before that action can safely proceed.
Prepare the next step
Continue with the section answering the next need instead of repeating the same test without changing your hypothesis. Suggested links connect preparation, research and comparison. This progression helps interpret outcomes, identify missing checks and choose a concrete action rather than stopping at a score or list. Keep observations available for later review. For “Inferring an email pattern”, also ask which observations would confirm or challenge your initial hypothesis. This connects preparation with a verifiable decision and prevents generalizing results beyond their context. Review findings with the people involved before changing your process, and distinguish measured improvements from assumptions that still require evidence. Keep the evaluation transparent, specific and reproducible for every stakeholder involved. A documented review makes comparisons easier and preserves assumptions when requirements change. Use relevant observations rather than generic promises to support the decision.
Frequently asked questions
Understand the need — What should be understood?
The pattern generator suggests addresses from first name, last name and domain. Results are structural hypotheses, not mailbox verification or permission to send. For Camille Moreau at a company using acme.fr, several combinations may exist. A known example for Jean Dupont can suggest a convention, but a company may use several formats across employees or subsidiaries.
Practical example — What should be understood?
For Camille Moreau at a company using acme.fr, several combinations may exist. A known example for Jean Dupont can suggest a convention, but a company may use several formats across employees or subsidiaries.
Method and checkpoints — What should be understood?
Enter the person’s fields and domain, optionally adding a known address with the corresponding name. Calculation happens in the browser. Results update and can be copied for subsequent verification. Start by defining the question you want to answer and information already available.
Limits and decision criteria — What should be understood?
Compound names, accents and namesakes can alter conventions. The displayed percentage estimates pattern plausibility; it is not an SMTP test. Separately verify address existence and status before campaign use. Before using the outcome to decide, verify its scope. Campaign preparation includes independent steps: targeting, contact quality, messaging, technical configuration and follow-up.
Prepare the next step — What should be understood?
Continue with the section answering the next need instead of repeating the same test without changing your hypothesis. Suggested links connect preparation, research and comparison. This progression helps interpret outcomes, identify missing checks and choose a concrete action rather than stopping at a score or list.
Understand the need — What should be checked?
The pattern generator suggests addresses from first name, last name and domain. Results are structural hypotheses, not mailbox verification or permission to send. For Camille Moreau at a company using acme.fr, several combinations may exist. A known example for Jean Dupont can suggest a convention, but a company may use several formats across employees or subsidiaries.
Practical example — What should be checked?
For Camille Moreau at a company using acme.fr, several combinations may exist. A known example for Jean Dupont can suggest a convention, but a company may use several formats across employees or subsidiaries.