Article

Typo Spam Trap Examples: 7 Patterns to Catch Before They Hurt Your Sender Reputation

By Unlimited Verifier Team ·

Diagram showing typo spam trap addresses like gmial.com and gnail.com passing through a lookalike domain check and MX verification before removal.

Summary

Typo spam traps are misspelled versions of major email domains, such as gmial.com for gmail.com, that can catch senders mailing unverified lists. The most common families are transposed, dropped, doubled and keyboard-neighbor letters, plus wrong endings like gmail.cm. Catching them requires domain counts, lookalike matching and domain, MX and SMTP checks rather than syntax validation alone.

Typo spam traps are misspelled versions of major email domains, such as gmial.com for gmail.com or hotmial.com for hotmail.com, that can catch senders who mail unverified lists. The seven patterns below cover the typo families most list owners encounter, with a detection method for each.

This guide is for list owners, marketers, agencies and SaaS teams that need email verification compliance and hygiene for large databases. It is part of our guide to spam traps and email blacklists. If the term is new, start with what a spam trap email address is. The tutorial uses Unlimited Verifier, the bulk verifier we recommend for this job.

Quick answer

What are the most common typo spam trap examples?

Most typo spam traps fall into a few families. Each is one keystroke, autocorrect slip or import error away from a real provider, which is why the same mistakes recur across signup forms and imports.

Quick picks

Pattern Example (intended → typo) Caught by syntax check? Caught by domain/MX check? Main risk
Transposed letters gmail.com → gmial.com No Only if unregistered Registered typos can accept mail
Dropped letter gmail.com → gmal.com No Only if unregistered Looks like a plausible abbreviation
Doubled or extra letter gmail.com → gmaill.com No Only if unregistered Easy to miss on review
Keyboard neighbor gmail.com → gnail.com No Only if unregistered Passes a quick visual check
Wrong ending gmail.com → gmail.cm / gmail.con No .con usually fails; .cm can resolve .cm is a real country-code domain
Near-miss business domain examplecorp.com → exmplecorp.com No Only if unregistered Invisible without your own domain counts
Regional ISP typo btinternet.com → btinternt.com No Only if unregistered Few public references to compare against
Punctuation error gmail.com → gmail,com or gmail..com Yes Not reached Not a trap; a syntax failure

Bottom line: the syntax check catches punctuation mistakes. Domain and MX checks catch unregistered typos. Registered typos need a domain-count review.

How did we compare these examples (and what are the limits)?

We reasoned about each pattern from public documentation on how syntax, DNS MX lookups and SMTP checks work, such as RFC 5321. We judged each pattern on four criteria:

  1. How the typo is produced. Each pattern maps to a common keystroke, autocorrect or import error.
  2. What a standard check sees. Syntax, MX and SMTP layers each see different things, and we noted where a pattern passes all three.
  3. False-positive risk. Some real domains sit one edit from major providers. For example, mail.com is one insertion away from gmail.com.
  4. Cost of mailing it. Weekly sending multiplies the damage from any undeliverable or trap address.

Limitations. We did not test these patterns against spam-trap operators or measure detection rates. The examples are constructed for illustration and are not a blocklist. Whether a specific registered domain is a trap can change over time, and no article can confirm it for you. Vendor accuracy figures are their own claims. For tool-level comparisons, see our overview of best email verification tools.

Bottom line: use these patterns as a checklist for your own data, not as a verified list of traps.

Which typo spam trap patterns should you check for?

Each pattern below follows the same breakdown: its signature, why it gets past basic checks, how to catch it, where detection falls short and one practical tip.

1. Transposed letters: gmial.com for gmail.com

Signature: two adjacent characters swap places. Gmial.com for gmail.com and hotmial.com for hotmail.com are the classic cases.

Why it gets through: the string is valid syntax. If someone has registered the typo, a live mail server can accept mail for it, and a syntax check sees nothing wrong.

How to catch it: an unregistered transposition fails the domain and MX checks, so it should land in Invalid. Be careful with the distance measure. Plain Levenshtein distance counts a swap as two edits, so gmial.com scores 2 against gmail.com and a distance-1 filter misses it. Use optimal string alignment, as the script below does, which counts an adjacent swap as one.

Where it falls short: a registered transposition can belong to an unrelated owner. The string alone cannot tell you which case you have.

Tip: check the import source before deleting. Dozens of gmial.com addresses arriving in one batch point to an import error. Scattered ones point to individual typing.

Bottom line: transpositions are the most common family, and a counts-based lookalike check finds them fastest.

2. Dropped letters: gmal.com, hotmal.com, yaho.com

Signature: one character is missing from the provider name, most often in the middle of the word.

Why it gets through: the shorter string looks like an abbreviation, and reviewers often accept it. Registered versions can accept mail just like any other domain.

How to catch it: a dropped letter is one edit from the real domain, so a distance-1 lookalike check flags it. Compare the hit's address count with the real domain's count. A typo domain usually holds a small share of the traffic the real provider gets.

Where it falls short: short business names produce many dropped-letter matches by chance. Each hit needs a review step before suppression.

Tip: for business-looking domains, check whether the company has a live website on that domain before treating it as a trap.

Bottom line: dropped letters look plausible, so trust the count comparison over visual review.

3. Doubled or extra letters: gmaill.com, hotmmail.com, yahooo.com

Signature: one character is repeated or inserted, usually from a held or repeated key.

Why it gets through: the domain resolves like any other valid string, and a syntax check has no reason to object.

How to catch it: the same distance-1 lookalike method applies. Doubled and extra letters are one edit from the real domain.

Where it falls short: some legitimate names contain doubled letters, so a company domain with a repeated character may be real. Review B2B hits manually.

Tip: doubled-letter typos cluster heavily in provider domains. Start the review with consumer providers, then move to company domains.

Bottom line: repeated-letter typos are easy to match, but company names need a human check.

4. Keyboard neighbors: gnail.com and hitmail.com

Signature: one letter is replaced by a physically adjacent key. In gnail.com, the m becomes an n. In hitmail.com, the o becomes an i.

Why it gets through: each word still looks almost correct, so it is the pattern most likely to survive a manual glance.

How to catch it: a distance-1 check catches single substitutions, but a generic one flags any domain one letter away from a provider. Restrict substitutions to QWERTY neighbors instead. Real keystroke errors come from adjacent keys, so this cuts false positives sharply.

Where it falls short: keyboard typos are the hardest pattern to separate from genuinely different short domains.

Tip: build a small neighbor map for the letters in your provider names (for example, m neighbors n and j, and o neighbors i and p on a standard layout). Use it as a filter on distance-1 hits.

Bottom line: keyboard typos are the best case for a QWERTY-aware filter, not a generic edit-distance check.

5. Wrong endings: gmail.cm, gmail.con and gmail.co

Signature: the right name with the wrong top-level domain. The three cases behave differently.

Why it gets through: .cm is the country-code domain for Cameroon, so it can exist and resolve. .con is not a top-level domain and usually fails the domain check. .co is the country-code domain for Colombia, but many businesses use it legitimately.

How to catch it: check endings only on consumer provider names. A .cm or .con ending on gmail or yahoo is a strong lookalike signal. A .co ending on a business name is not.

Where it falls short: .co is the largest false-positive risk in this family. Bulk-suppressing every .co address removes real customers.

Tip: apply the ending rule to your top ten consumer providers only. Use your domain counts, not the TLD alone, to judge business addresses.

Bottom line: wrong endings are syntactically valid and sometimes resolve, so treat them as a review category, not an automatic delete.

6. Near-miss business domains: exmplecorp.com for examplecorp.com

Signature: a company domain with one letter missing, added or swapped. It usually comes from a retyped address at a trade show, in a form or during manual data entry.

Why it gets through: provider-based filters never check it, because consumer lists don't contain company domains. Only your own data reveals the pattern.

How to catch it: use your own top domains as the reference set. Take the 200 most frequent domains in your list, then flag low-count domains within one edit of any of them. Run the same review on account value, since business typos matter most for high-value contacts.

Where it falls short: two genuinely different companies can have similar names, and a public reference list cannot tell them apart.

Tip: for key accounts, confirm the address with the contact or the company's website before suppressing. Losing a real buyer costs far more than checking one address.

Bottom line: business near-misses need your own domain counts as the reference, because no public provider list will catch them.

7. Regional ISP typos: btinternt.com for btinternet.com

Signature: a typo of a domain belonging to a national or regional internet provider, such as a UK ISP. The dropped letter here removes the e from btinternet.

Why it gets through: regional providers have smaller user bases, so the real domain's count is low. A typo can look like a normal, small domain. Generic provider lists often omit these names.

How to catch it: build the reference set from your audience. For a UK list, include the major UK providers alongside the global ones. For a multi-country list, use the top domains per country.

Where it falls short: smaller markets produce more false positives, because real small domains sit close to other real small domains.

Tip: segment your reference list by country, then run the lookalike check within each segment, not across the whole database.

Bottom line: regional typos are missed by global provider lists, so your reference set must match your audience.

How do you check a list for typo spam traps?

The first pass on a large list is a focused session, and it's the only heavy lift. After that, weekly upkeep is a short upload. The workflow runs the domain-count review first, then verification.

  1. Create an account. Sign up for free. The Free plan handles lists of up to 150 emails each.
  2. Export your list as CSV. Include the email column and, if your ESP stores it, a signup-date or source column. Source data often reveals the batch behind a typo cluster.
  3. Count addresses per domain. Use a pivot table, COUNTIF or the script below. Sort the counts from highest to lowest.
  4. Flag lookalikes. Compare low-count domains against a reference set. For consumer lists, use the major providers. For B2B lists, use your own top domains. Review every hit.
  5. Build an allowlist. Add legitimate look-alikes such as mail.com, regional variants and your customers' real domains.
  6. Split the file if needed. Free lists hold up to 150 emails and Pro lists up to 25,000. Files must also stay under 10MB.
  7. Upload and verify each list. The email column is detected automatically, and every address is sorted into Valid, Risky or Invalid. Standard verification is unlimited on every plan.
  8. Triage the buckets. Suppress Invalid. Review Risky by domain and check whether lookalike domains appear there. Catch-all email verification explains how those results work.
  9. Deep-verify the ambiguous lookalikes. Free includes 750 deep verifications a month and Pro includes 25,000. Spend them on Risky lookalikes, not on addresses already marked Valid. A quick spot-check of a single suspicious address can also use the free email checker.
  10. Export promptly. Free results are kept for 24 hours and Pro results for 30 days. Download CSV or Excel as each run finishes.
  11. Re-import and suppress. Unlimited Verifier has no native ESP integration, so update your suppression list through a CSV re-import. For automation on Pro, the email verification API accepts bulk batches of up to 10,000 emails per request, which is the starting point for email verification API and automation. Our guide on email list maintenance best practices covers the recurring routine.
  12. Fix the source. Add a "did you mean gmail.com?" prompt at signup and consider real-time email validation on the form. For remediation steps, see how to remove spam traps from your email list.

Script: flag lookalike domains (review tool, not a verdict)

from collections import Counter

PROVIDERS = {"gmail.com", "yahoo.com", "hotmail.com", "outlook.com", "icloud.com", "aol.com"}
ALLOW = {"mail.com", "hotmail.co.uk", "yahoo.co.uk"}  # your legitimate look-alikes

def damerau_levenshtein(a, b):
    # Optimal string alignment: an adjacent swap costs 1, not 2
    d = [[0] * (len(b) + 1) for _ in range(len(a) + 1)]
    for i in range(len(a) + 1):
        d[i][0] = i
    for j in range(len(b) + 1):
        d[0][j] = j
    for i in range(1, len(a) + 1):
        for j in range(1, len(b) + 1):
            cost = 0 if a[i-1] == b[j-1] else 1
            d[i][j] = min(d[i-1][j] + 1, d[i][j-1] + 1, d[i-1][j-1] + cost)
            if i > 1 and j > 1 and a[i-1] == b[j-2] and a[i-2] == b[j-1]:
                d[i][j] = min(d[i][j], d[i-2][j-2] + 1)
    return d[-1][-1]

def lookalikes(domain_counts, reference, max_edits=1, max_count=500):
    hits = []
    for domain, n in domain_counts.items():
        d = domain.lower().strip()
        if d in reference or d in ALLOW or n > max_count:
            continue
        for ref in reference:
            if damerau_levenshtein(d, ref) <= max_edits:
                hits.append((domain, n, ref))
                break
    return hits

# emails = list of addresses from your CSV
counts = Counter(addr.split("@")[-1].lower() for addr in emails)
suspects = lookalikes(counts, PROVIDERS)                      # consumer lists
top = {d for d, _ in counts.most_common(200)}
business = lookalikes(counts, top, max_count=20)              # B2B lists

Two settings matter. Use max_edits=1 for single-keystroke errors, and raise it to 2 only if you accept more false positives. The max_count cap keeps large legitimate domains out of the review queue.

Worked example 1: reading a domain-count table (illustrative numbers).

Domain Addresses Closest reference (edits) Action
gmail.com 18,400 Reference Keep
gmial.com 37 gmail.com (1) Review, then suppress if confirmed
hotmail.com 9,100 Reference Keep
hotmial.com 22 hotmail.com (1) Review, then suppress if confirmed
mail.com 140 gmail.com (1) Allowlisted
exmplecorp.com 4 examplecorp.com (1, business reference) Manual review

Worked example 2: the cost of leaving them in (illustrative numbers). Suppose a 40,000-address list contains 0.3% typo-pattern addresses, which is 120 addresses. Those 120 addresses bounce on every send. That's 120 ÷ 40,000 = 0.3% of the list per send, a third of the 1% ceiling we recommend and room that other bounces will need. Across a weekly schedule, it's 120 × 52 = 6,240 sends a year to addresses that should have been removed.

Worked example 3: fitting the list to the plan. The same 40,000 addresses on Free: 40,000 ÷ 150 = 267 lists (rounded up). The Free plan allows 25 lists a month, or 25 × 150 = 3,750 emails a month. That's 40,000 ÷ 3,750 ≈ 10.7, so the full pass takes 11 months. On Pro, the same list splits into two files, 25,000 and 15,000, which fits within a single month. Deep verifications for the Risky lookalikes draw from the 25,000 monthly allowance.

Bottom line: count domains first, verify the lookalikes, suppress what's confirmed, then fix the signup form so the typos stop arriving.

Which detection approach should you choose?

Match the approach to where typos enter your database, because that's where the fix belongs.

Your situation Start with Why
Signup form producing typos "Did you mean" prompt at signup, plus real-time email validation Stops new typos at the source
Weekly newsletter Verify each week's signups; full-list pass quarterly Typos arrive continuously
Imported or purchased list Domain-count review, then full verification Batch imports concentrate typos; see whether purchased lists contain spam traps
B2B or client list Business near-miss rule with your own top domains, plus manual review of key accounts Company lookalikes need your own data as the reference
SaaS signups through an API Per-signup checks before the address enters the list Gates bad addresses; see email verification for ecommerce and SaaS
Regional audience Country-segmented reference lists Local ISP typos are invisible to global provider lists

If you're comparing tools for this work, see how to choose an email verifier and our roundup of best tools to detect spam traps in email lists. At weekly volume, per-check costs add up, so review email verification pricing models before committing.

Bottom line: the cheapest fix is at the signup form, and the most complete fix is a domain-count review followed by verification.

What mistakes do teams make with typo spam traps?

Bottom line: most typo-trap damage comes from process gaps, such as unchecked imports and unfixed forms, rather than from one bad address.

Verdict

Typo spam traps follow predictable patterns: transposed, dropped, doubled and substituted letters, wrong endings, near-miss business domains and regional ISP typos. A syntax check catches punctuation mistakes, but registered typos can pass basic checks. The reliable approach is a domain-count review against the right reference set, followed by a verifier that checks domain/MX, SMTP mailbox and catch-all status.

Unlimited Verifier fits that workflow. Standard verification is unlimited on every plan, results sort into Valid, Risky and Invalid, and Pro adds deep verifications for ambiguous cases and an API for bulk batches. It doesn't replace your own domain review, and it can't tell you whether a specific registered domain is a trap. Industry guidance from M3AAWG and Spamhaus is a useful companion for how trap and listing categories are defined.

Bottom line: count your domains, verify the lookalikes, suppress what's confirmed, and fix the signup form so the typos stop arriving.

Typo pattern quick reference

Pattern Intended → Typo Action
Transposed gmail.com → gmial.com Flag and verify
Dropped letter gmail.com → gmal.com Flag and verify
Doubled letter gmail.com → gmaill.com Flag and verify
Keyboard neighbor gmail.com → gnail.com Flag and verify
Wrong ending gmail.com → gmail.cm Flag and verify

Frequently asked questions

What is a typo spam trap?

A typo spam trap is a misspelled version of a major email domain, such as gmial.com for gmail.com, that an operator registers or monitors to catch senders who mail unverified addresses. Mail sent to these addresses can signal poor list hygiene to blocklists and inbox providers.

Why doesn't a syntax check catch typo spam traps?

Syntax checks only confirm the address follows valid formatting rules. A misspelled domain like gmial.com is formatted correctly, so it passes. Catching it requires comparing the domain against known providers and checking whether it has mail servers.

Are typo spam traps the same as pristine spam traps?

Not exactly. Pristine traps are addresses never used by a real person, often created to catch scrapers. Typo traps are often registered misspellings of popular domains, so they catch senders who make entry errors or buy poorly sourced lists.

How do I find typo domains in my list?

Group addresses by domain and count them. Then compare low-volume domains against a reference list of major providers using edit distance or keyboard-neighbor rules. Flag close matches for review or verification before your next send.

Can a typo domain be registered and still be dangerous?

Yes. A registered typo domain can accept mail, so a domain or MX check alone may pass it. That is why registered typos need an SMTP or catch-all check and a review of the domain's history.

What bounce rate is safe for typo spam traps?

Most ESPs treat around 2% hard bounces as a warning level. For weekly senders, keeping hard bounces under 1% per send is a stricter and safer target used by many email teams.

Should I delete every address with a typo domain?

Usually yes for consumer lists where the intended provider is obvious, since the address is unlikely to belong to the subscriber. For B2B lists, confirm first, because some near-miss company domains may be real.

How often should I check my list for typo traps?

Check at every import and before major sends. Typos enter through signup forms and imports continuously, so a one-time cleanup quickly goes stale. Recurring checks keep hard bounce and complaint rates stable.

Cut Bounces and Protect Your Sender Reputation With Unlimited Email Verification

Every invalid address you send to hurts your sender reputation and your inbox placement. Verifying your list before each send means fewer bounces, healthier deliverability, and a predictable cost. With Unlimited Verifier, standard verification is unlimited on every plan, with no per-email fees.

Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox. It also detects catch-all domains and flags disposable and role-based addresses. Export a CSV from your email platform or CRM, upload and verify the list, then re-import the clean results. You can also automate checks with the email verification API.

Free Pro
Price $0 $29/month ($25/month billed annually)
Lists 25 a month, up to 150 emails each Unlimited, up to 25,000 emails each
Deep verifications 750 a month 25,000 a month
API access No Yes (100,000 emails a month)
Result retention 24 hours 30 days

Why teams choose Unlimited Verifier

Unlimited Verifier states 99.5% accuracy for deep verification.

Create a free account and verify your next list before you hit send.

Want to test a single address first? Try the free email checker.