Plus addressing and Gmail dots: how aliases create duplicate accounts
One inbox can hold hundreds of spellings. How Gmail dots and plus addressing create duplicate accounts, and why simple email rules keep breaking.
All you wanted from your users table was a dull number: how many trials started this week. The newest row is patsample@gmail.com. You've seen that name before, so you scroll, and 14 days further down there it is again as pat.sample@gmail.com. Same name, same trial, started the day the other one ended.
You search for "sample" and the page fills up. p.atsample. pat.samp.le. pat.sample+april. pat.sample+may. There are 23 accounts, all with verified emails, all reaching one inbox, and your product has handed that inbox a fresh trial 23 times.
You've just met Gmail dot alias duplicate accounts: one mailbox, many spellings, and a signup form that counts each spelling as a new customer.
Here's a scenario you can rerun with your own numbers. Say each 14-day trial includes 2,000 credits that cost you $7.50 to serve, and your plan is $39 a month.
- 23 trials × 14 days = 322 days of your product, with no gap
- 23 trials × $7.50 = $172.50 out of your pocket
- 322 days is more than 10 months, and 10 × $39 = $390 Pat never paid
You found Pat by accident, so you stop trusting the rest of the table. Two days of reading later, you've got 60 people like Pat, averaging 18 accounts each.
- 60 people × 18 accounts = 1,080 accounts
- 1,080 accounts × $7.50 = $8,100 a year
- If you spend $12,000 a month, that's about 20 days of runway ($8,100 ÷ $12,000 × 30)
Then you look at the number from last month's investor update: 4,000 trials and 200 customers, a 5% trial-to-paid rate. Those 4,000 trials came from 2,980 people (4,000 minus 1,080, plus the 60 people behind them). So the real rate is 200 ÷ 2,980, or 6.7%. A year of decisions about pricing and onboarding rests on a figure that counted Pat 23 times.
That night you write the obvious rule: ignore dots when comparing email addresses. It takes 20 minutes, and Pat's next spelling bounces off it.
Eleven days later, Jo Hansen tries to start a trial with jo.hansen@northwind.example. Erik Johansen, two desks away, signed up last spring as johansen@northwind.example. Those are two people with two mailboxes, because on a company domain a dot can change the address. Your rule says they're one. Jo sees "This email is already in use", assumes someone at work has the account, tries once more and opens a competitor's site in the next tab.
Nobody writes to you. No error gets logged, because the form did what you told it to. That team was going to be 12 seats at $39, which is $468 a month or $5,616 a year. Lose two teams like that in a year ($11,232) and your rule has cost more than the $8,100 it was written to save.
So that's the choice in front of you. Loosen the rule and keep paying for Pat, or tighten it and keep losing Jo, with no report anywhere to tell you how often.
Pat and Jo are made up. The team in this next story isn't.
From our early beta
Scammers created account after account with a stack of email aliases and the same one or two cards. Every one of those accounts shared a payment fingerprint, but nothing was checking it, and the team's payment processor restricted their payment processing.
What Gmail dots and plus addressing actually do
Your database stores an email address as text. A mail provider treats it as directions to a mailbox, and different text can lead to the same place.
Gmail's help pages are plain about dots: add or remove them in a standard Gmail address and the mail still arrives in the same inbox. A nine-letter username has 8 gaps between its letters, and each gap can hold a dot or not, so that's 2 to the power of 8, or 256 spellings of one person's address.
Plus addressing is the other one. Put a plus sign and a word before the @, and mail to pat.sample+news@gmail.com still lands with Pat. Plenty of honest people do this to filter newsletters into a folder or to see who passed their address along. Both are documented behavior. Other providers make their own choices about all this, and they can change them.
Why a unique-email check passes every time
A unique constraint on your email column compares text. patsample and pat.sample are different text, so the database is happy.
Email verification doesn't help here, which surprises a lot of founders. The code goes to the alias, the alias delivers to the real inbox, and the person enters the code. Verification proves someone can open that mailbox, and they can.
So you teach your app which spellings are the same. The right answer depends on who runs the mailbox, and the address doesn't always tell you. A company can run its mail on Gmail under its own domain, and there dots count. Too broad a rule produces Jo. Too narrow a rule misses most of what you wanted to catch. A domain owner can also accept mail for any address at all, and nothing about an alias rule touches a second real mailbox, which takes a few minutes to open. The rule also runs at signup, so it says nothing about the 1,080 accounts you already have.
The basic email checks, and how each one breaks
Each of these catches something real, and each has a price.
| Basic fix | What it catches | What it misses | Who it wrongly blocks | What it costs to keep working |
|---|---|---|---|---|
| Unique emails | The exact same address twice | Every alias | Almost nobody | Very little |
| Email verification | Typos and dead addresses | Any alias of a working inbox | People whose code lands in spam | Deliverability work |
| Ignoring dots and plus signs | One inbox written several ways | A second real mailbox | Colleagues like Jo | Upkeep as mail services change |
| Refusing plus signs outright | Anyone using a plus alias | Dots and second mailboxes | People who filter their mail | Tickets from careful users |
| Disposable-domain blocks | Known throwaway services | New domains, Gmail aliases | People using privacy forwarding | A list someone updates forever |
| CAPTCHA | Simple scripts | A person signing up by hand | Screen reader users | Fees and lost signups |
| Phone requirement | Casual repeat accounts | Anyone with another number | People without a stable mobile number | A charge for every text |
| Card requirement | Casual repeat accounts | Anyone with another card | People who want to try first | Fewer trials started |
| One per IP address | Repeats on one connection | Any other network | Offices, campuses, households | Exceptions and tickets |
| VPN blocks | Listed VPN ranges | Everything else | Staff on company VPNs | Another list to maintain |
| Rate limits and usage caps | One account overrunning | Each new account's fresh limit | Real users in a busy hour | Tuning per endpoint |
| Shorter trials | Some cost per account | More accounts make up the difference | Every honest user | Fewer people reach paying |
| Manual review | What a person can spot | Whatever arrives after you stop | Whoever looks odd on a tired day | 4,000 trials at 1 minute each is about 67 hours |
Stack them and an honest person now has to verify an email, solve a puzzle, type a phone number and hand over a card to try your product, while Pat opens one more mailbox. Each row needs an owner, too, and the domain list goes stale first.
How to handle email aliases without losing real customers
Aliases can't be fixed at the form, but you can make them much less expensive.
Separate the account from the benefit. Let people sign up with the address they use, and decide separately who gets the trial or the credits. Start by writing down what one person is allowed.
Keep plus addresses legal. Only say "already in use" when that exact address is on file. Refusing someone over a dot or a plus sign is how you lose Jo.
Treat an alias as a reason to look, never a verdict. Hold back the free benefit instead of the account, and tell the person how to reach you. Some of them will be returning customers.
Put a ceiling on the cost. A hard cap on free usage means whatever gets past your rules can't take the month's budget with it.
Clean up slowly. Go through old accounts by hand and merge with care. Then correct your conversion numbers.
That gets you fewer false blocks and a limit on the damage. It still can't tell you whether a claim comes from someone who's had this benefit before, because a new address arrives with no history in your table.
Handling aliases without maintaining email rules
You don't have to build your own abuse prevention system, and you certainly don't have to keep a rulebook for other people's mailboxes. AbuseZero is made for the moment a trial or a batch of credits is about to go out. A unique-email rule is one check, and a domain list is one more. Against those, multi-layer AI risk analysis examines 140,000+ signals, detects linked claims and flags abuse that single checks miss, with signals read together, never one at a time. A proprietary algorithm drives it, and AI checks the claim again.
AbuseZero checks mailbox aliases, disposable domains and mail routing. It detects repeated payment fingerprints across users, even when new accounts and emails hide the connection, and it recognizes repeat devices across new accounts, even when email addresses keep changing, and it sees beyond an IP address with VPN, hosting, network reputation, Tor and proxy intelligence. Creating a fresh account isn't enough to erase previous activity.
Your server makes one API call and gets a clear allow or deny, under rules you control. Send the identifiers you already have, then use Observe mode to see what would be denied before anyone is blocked. The quickstart walks you through your first benefit.
Frequently asked questions
Do dots matter in Gmail addresses?
Not in a standard Gmail address, where mail reaches the same inbox with or without them. On a work or school account that uses Gmail, dots do change the address.
Should I block plus addresses at signup?
We wouldn't. Plenty of people use them to sort their mail, and dots and second mailboxes would still get through. Decide who gets the benefit instead, which is the job of an AbuseZero evaluation if you'd rather not build it.
Can email alone tell me two accounts are the same person?
Sometimes it can show that two addresses reach one inbox. It can't tell you that a different address belongs to someone you've already seen. See multi-accounting detection without blocking real users.
Keep your trials for new customers
Start with Builder
Pay as you go. Protect your first benefit today.
See pricing
Builder, Pro, Scale and Enterprise.
Talk to us about Enterprise
Higher volumes and custom terms.