Email Permutator

No. An email permutator generates likely candidates but cannot confirm which inbox exists. Companies use different email patterns — by department, hire date, or internal alias rules no public tool can predict.

• Always pipe results into an email verifier (Hunter, NeverBounce, ZeroBounce) before sending.
• Test the 3-5 most common formats first: first.last, firstinitiallast, first_last, first, firstlast.
• If multiple patterns verify for the same person, prefer the one shown on the company website or press contacts.

The permutator saves discovery time; the verifier protects your sender reputation. Skipping verification can sink a sending domain inside a single sequence.

Yes — mail.company.com works — but root domains hit more often in most prospecting flows.

• Root usually wins: corporate mail typically routes through the root (alex@company.com); subdomains often handle marketing or transactional traffic.
• Subdomains help on large enterprises that split mail by region or unit (alex@eu.company.com, alex@brand.company.com). If you see the pattern on a press or careers page, test it.
• Acquisitions and rebrands: a newly acquired company may keep its legacy domain for a year or more — run permutations against both.

Safe default: try root first, verify winners, fall back to subdomains only when root patterns fail.

Yes, but only with strict list hygiene. Sending unverified email permutations at scale is the fastest way to damage a sending domain.

1. Bulk-generate candidates from your target list.
2. Verify every candidate; keep only "valid" or high-confidence "accept-all".
3. Send accept-all domains in a separate, lower-volume sequence — they hide both real and invalid inboxes.
4. Warm new sending domains or IPs before crossing a few hundred sends per day.
5. Watch bounce, complaint, and reply rates daily for two weeks; pause if bounces exceed 3%.

Verifier-plus-warmup discipline keeps outbound scalable; skipping it pushes you into spam folders.

First name, last name, and domain are all required. Missing any one either turns the output into noise or biases it toward unused patterns.

• First name: drives all first-led variants (alex@, alex.last@, alexl@). Test legal first name and nicknames separately — "Alex" and "Alexander" can both hit.
• Last name: drives last-led, dot, and underscore variants. Test hyphenated last names with and without the hyphen.
• Domain: the root company domain — no full URL or "www." prefix.

If you only have one field, enrich the others first (LinkedIn, About page, press release) before running the email permutator.

Permutator hit rate is pattern intelligence, not luck. Teams prospecting at scale build a compounding feedback loop:

• Log patterns by company type — industry, size, and region all correlate with email convention choices.
• Record which pattern verified for each contact so the next prospect at that company starts with the right guess.
• Watch company-level changes: domain migrations after an acquisition can invalidate an entire log entry.
• Combine signals from HR pages, press contacts, and customer testimonials.
• Share the log across the team so SDRs do not re-discover what AEs validated last quarter.

Over 6-12 months this lifts first-attempt hit rates and cuts verifier spend.