Addresses on @shimpsales.com follow
first.last — for example jane.smith@shimpsales.com. We hold this format as independently
confirmed rather than inferred from a sample.
Enter a name below to build every variation on this domain, then verify which one actually accepts mail.
Enter a person’s name to generate every common address format on @shimpsales.com, then verify which one actually exists.
Addresses use first.last — for example jane.smith@shimpsales.com.
This format is held as confirmed independently of our own sampling, so no percentage is quoted for it — a share would imply a measurement that is not what established this.
| Address | Format | |
|---|---|---|
| jane.smith@shimpsales.com | first.last | Verify → |
| j.smith@shimpsales.com | f.last | Verify → |
| jsmith@shimpsales.com | flast | Verify → |
| janesmith@shimpsales.com | firstlast | Verify → |
| jane@shimpsales.com | first | Verify → |
| jane_smith@shimpsales.com | first_last | Verify → |
| jane-smith@shimpsales.com | first-last | Verify → |
| smith@shimpsales.com | last | Verify → |
| smith.jane@shimpsales.com | last.first | Verify → |
| smithj@shimpsales.com | lastf | Verify → |
| s.jane@shimpsales.com | l.first | Verify → |
| janes@shimpsales.com | firstl | Verify → |
| jane.s@shimpsales.com | first.l | Verify → |
Addresses on @shimpsales.com use
first.last — for example jane.smith@shimpsales.com. We hold this as a confirmed format rather
than an inference from our own sample, which is why this page states the convention without
attaching a percentage to it.
first.last, which is the convention this domain
actually uses.
A generated address is a hypothesis, not a fact. Sending to unverified guesses is the fastest way to damage a sending domain: every hard bounce signals to mailbox providers that your list is stale, and that reputation hit applies to your whole audience, not only the addresses that failed. Cold outreach programmes routinely lose inbox placement this way.
Verification avoids that. Our engine performs a real SMTP handshake against the @shimpsales.com mail servers and stops short of delivery, so nothing arrives in anyone’s inbox. Working through a list rather than one prospect? Upload it to the bulk email verifier to clean the whole file at once, or wire the real-time verification API into your signup and CRM flows so unverified addresses never enter your database in the first place. If you are new to this, start with the guide to email verification APIs.
This page carries no company profile, because the measurement is what we actually know. Falcon19 classifies the local part of every address our verification engine confirms as genuinely deliverable, counts it against its domain and its shape, and stores nothing else — no address, no local part, no user. The figures below are that count.
@shimpsales.comfirst.last
first.last — for example jane.smith@shimpsales.com. This one is independently confirmed rather
than inferred from our own sample, so no percentage is attached to it.
Addresses end in @shimpsales.com. That domain
has live MX records, meaning it accepts inbound mail and can be checked directly.
No, and you should be sceptical of any tool that claims otherwise. Knowing a domain’s convention tells you how an address would be built; it does not tell you that a particular person works there or that their mailbox exists. What turns a candidate into a confirmed address is the verification step, which asks the mail server directly.
Yes. Upload a CSV to the bulk email verifier to process thousands of @shimpsales.com addresses in one run, or call the verification API directly from your own systems.
Verification is a standard, non-intrusive SMTP check — the same conversation any mail server has before delivering a message, stopped before anything is sent. No message reaches the recipient and no mailbox is accessed. It is what responsible senders do to keep bounce rates down.
first.last · 96.8% of 62 classified
@kastelladvokatbyra.sefirst.last · 100% of 15 classified
@fylgia.sefirst.last · 88.2% of 17 classified
@wadv.sefirst.last · 93.5% of 31 classified
@cms-wistrand.comfirst.last · 98.9% of 92 classified
@anchor.eufirst.last · 91.7% of 24 classified