Enter your name, pick a host, and the tool builds a shortlist of address ideas instantly, right in your browser. Nothing is uploaded or stored. Unlike most email generators, this one also checks whether your domain already has mail configured (a live MX lookup) before you commit to an address.
ada.lovelace@adastudio.com · lovelace.ada@adastudio.com
alovelace@adastudio.com · a.lovelace@adastudio.com
ada@adastudio.com
hello@adastudio.com
Picking your own address is the easy part
Finding and verifying other people's B2B email addresses at scale is a different problem. Overloop checks names and domains against a 450M-contact database and hands your team verified addresses, not guesses, so outbound lists stop bouncing.
Try for free →How to choose a professional email address
A professional email address has one job: it needs to be trusted and typed correctly, over and over, by people who have never met you. That is a narrower goal than "sounds cool" or "is available," and it rules out a lot of the addresses people default to. Four rules cover almost every case.
- Keep it short. Every extra character is a chance for someone to mistype it into a bounce. If your name generates a 28-character local part, look at the shorter patterns in the tool above before you settle.
- Make it spellable out loud. If you have to say "that's Katherine with a K, no H, then underscore" on a phone call, the address is working against you. Say the candidate address out loud before picking it.
- Keep it consistent with your team, if you have one. A one-off, cleverly personalized address is a liability the moment a colleague needs to guess it, or a client needs to remember whether it was dot or underscore. Consistency beats personality here.
- Avoid numbers and nicknames. ada.lovelace1987@ or crazyada99@ both read as either already-taken leftovers or a personal account that wandered into business use. If your first choice is taken, there are better fixes than tacking on a birth year, covered below.
One more thing worth deciding upfront: what you optimize for changes depending on who you are. A solo consultant benefits from an address that signals what they do (a brand-forward pattern). Someone joining an existing team should match whatever convention that team already uses, even if it is not their personal favorite. The tool above groups ideas by exactly this distinction so you are not choosing blind.
Naming conventions compared
Different patterns carry different tradeoffs once more than one person needs an address at the same domain. The table below is written for that decision: not "which looks nicest" but "which one still works when your team has grown."
| Pattern | Example (Ada Lovelace) | When it wins | Collision risk at scale |
|---|---|---|---|
| first.last | ada.lovelace@ | Default choice for most teams past a handful of people; reads as established and is easy to guess correctly | Low. Only collides if two people share both first and last name |
| flast (first initial + last) | alovelace@ | Larger organizations that want shorter addresses without losing clarity | Medium. Collides whenever two people share an initial and a surname |
| first | ada@ | Solo operators, very small teams, or a personal brand where informality is the point | High past 10 to 15 people; first-name collisions become common fast |
| first_last or first-last | ada_lovelace@ | Teams with an existing style guide that specifies a separator; mostly a stylistic choice | Low, same collision profile as first.last |
| f.last | a.lovelace@ | A middle ground when flast alone looks too compressed | Medium, same profile as flast |
| Brand-forward (first.brand) | ada.studio@ | Freelancers and consultants who want the address to double as light branding | Not applicable at scale; this pattern does not extend cleanly past one or two people |
| Role-based (info, hello, sales) | info@ | A shared team inbox for support or general inquiries, never a personal identity | None, by design there is exactly one owner: the inbox, not a person |
The pattern that "wins" changes as headcount grows, and it moves in one direction: toward more structure, not less. A two-person shop can get away with first@ for everyone. The moment a company hires its second Ada, or its third person whose last name starts with L, that pattern breaks and someone has to retrofit an exception, which is exactly the kind of inconsistency that makes an email address look unprofessional in hindsight.
What to do when your name is taken
On a shared domain like gmail.com or outlook.com, a common first and last name combination is very likely already claimed by someone else. On your own company domain, the more common version of this problem is two employees who happen to share a first name, or a first initial and surname. Either way, resist the urge to just append a number. Here is the order worth trying instead.
- Add a middle name or initial. ada.g.lovelace@ or adag.lovelace@ solves most collisions without looking like an account created after the good ones were gone. It also happens to be the pattern most large enterprises fall back to automatically for exactly this reason.
- Switch separator or order. If ada.lovelace@ is taken, lovelace.ada@ or ada-lovelace@ is a legitimate second attempt. This only works cleanly for one collision; do not stack this with the tie-breaker below for a third person, since the resulting address stops being guessable by anyone outside the two of you.
- Use a hyphenated or full middle name. This trades a slightly longer address for one that still reads as a name rather than a workaround. It is usually the better trade versus a number.
- Only add a number as a last resort, and keep it meaningful. A join year (ada.lovelace2 for the second Ada hired) at least communicates something. A random digit does not, and it is the detail that makes an otherwise solid address look like an afterthought.
- On free hosts, check before you build anything around it. If you are choosing between gmail.com and outlook.com, the two are equally taken for common names, so testing availability directly (attempting to sign up) is faster than guessing which provider has fewer Adas.
Custom domain vs. free email for business
ada@gmail.com and ada@adalovelace.com generate the exact same first impression problem in opposite directions: one looks like a personal account doing business, the other looks like a business that has not gotten around to setting up email properly if the domain is not configured yet. For anything beyond a very early side project, a domain you control is worth the setup cost, for two concrete reasons rather than a vague sense of polish.
Trust. A recipient who has never met you reads gmail.com or outlook.com as "this could be anyone," where a company domain at least confirms you are who you claim to work for. That matters more in cold outreach than in a reply to someone who already knows you.
Deliverability. A custom domain you control lets you configure your own sending authentication, SPF, DKIM, and DMARC, which mailbox providers use to decide whether your mail is legitimate. Free webmail providers manage that infrastructure for you, which is convenient but means you have no way to fix a reputation problem if one appears, and no way to warm up a dedicated sending identity. If you are setting up a domain for outbound at any real volume, our guides to SPF, DKIM, and DMARC setup and email warmup cover both pieces in detail.
None of this means gmail.com or outlook.com is wrong for a personal address, a student project, or a very early one-person operation. It means the trade should be a conscious one: free and instant now, versus owned and configurable later. If you already know you are building something that will send outbound at volume, set up the domain first; retrofitting deliverability onto an address people already have saved is far more disruptive than doing it upfront.
Team-wide conventions at scale
The single biggest failure mode for company email addresses is not picking a bad pattern, it is picking a good one and then not writing it down. Someone in HR sets up the first ten hires as first.last@, a new manager onboards the eleventh as flast@ because nobody told them otherwise, and eighteen months later half the company has to guess which format a given colleague uses.
The fix is a one-paragraph rule, decided once and applied without exception: pick a pattern from the comparison table above, document the collision-handling order (middle initial, then hyphen, then a meaningful number), and put both in whatever onboarding checklist creates new accounts. Two details make this durable rather than theoretical:
- Decide the collision rule before you have a collision. Retrofitting a rule after the second Ada joins means someone has to choose whether the first or second Ada gets the "clean" address, which is an awkward conversation that a documented rule avoids entirely.
- Apply the rule to role-based addresses separately. info@, sales@, and support@ are shared team inboxes, not personal identities, and should follow their own short, fixed list rather than being improvised per department.
Once the convention exists, it should outlive any single person who set it up. That is the actual test of whether a naming convention was any good: not whether it looked clean at ten employees, but whether anyone at two hundred employees can still guess a colleague's address correctly on the first try.
This tool vs. finding someone else's email
It is worth being precise about what this page does and does not do, because the two problems look similar and are not. This generator helps you create ideas for a new address you are about to start using yourself, from your own name and, optionally, a brand word. It has no idea who already owns any given address at a domain; it is a naming tool, not a lookup tool.
If your actual problem is the opposite, you already know a person's name and their company, and you need to guess their existing email address so you can reach them, that is a different tool with a different job: the email permutator. It runs the same kind of pattern logic but for someone else's mailbox, and it pairs with a verification step so you are not sending to guesses. If instead you have an address in hand and want to know who owns it, a reverse email lookup answers that third question. Three related problems, three different tools: pick the one that matches what you actually know and what you are trying to find out.
Frequently asked questions
What is the most professional email format?
first.last@domain (for example ada.lovelace@company.com) is the most widely accepted professional format. It is unambiguous, easy to guess correctly, and scales cleanly as a team grows, which is why most mid-size and large companies standardize on it. Shorter patterns like flast@ are also considered professional, especially at larger organizations; what reads as unprofessional is nicknames, numbers, or inconsistent formats within the same team.
Should I use Gmail or Outlook for a business email address?
For a very early project, a student, or a personal address, either is fine and instant. For anything representing an established business or sent at outbound volume, a domain you control is a better long-term choice: it builds trust with recipients who have never met you and lets you configure your own email authentication (SPF, DKIM, DMARC) instead of relying entirely on a free provider's shared infrastructure.
What should I do if my name is already taken as an email address?
Try a middle initial or middle name first (ada.g.lovelace@), then a different separator or word order (lovelace.ada@), then a full hyphenated middle name if needed. Only add a number as a last resort, and make it meaningful, such as a join year, rather than a random digit, since arbitrary numbers are what make an address look like an afterthought.
Is this the same as an email permutator?
No, they solve opposite problems. This tool generates ideas for a new address you are about to start using yourself, based on your own name. An email permutator generates guesses for someone else's existing email address, based on their name and company domain, so you can try to reach them. If you need to find or guess someone else's address, use the email permutator instead.
Do I need my own domain to look professional?
Not always, but it helps as soon as you are representing an established business rather than yourself personally. A custom domain signals legitimacy to people who have never met you and gives you control over deliverability settings that free webmail providers manage on your behalf. A solo project or personal use case can reasonably start on gmail.com or outlook.com and move to a custom domain later.
Does this tool store, upload, or send my information anywhere?
No. Every address idea is generated locally in your browser using JavaScript; your name and any brand word you type never leave your device. The one exception is the optional domain check: if you enter your own domain and the tool checks its DNS records, that single lookup (the domain name only, never your name) is sent to Google's public DNS resolver to tell you whether mail is already configured there.