Offex Mail

Understanding email verification flows

Updated for 2026 · 6 min read

"Verify your email" is a sentence most of us tap past without a thought. But the machinery behind it is worth understanding, because it explains almost every oddity you meet during a sign-up: why a link expires, why a code never arrives, and why the same service treats two addresses differently.

Email verification flow: form submitted, email sent, inbox receives, account verified
Every verification flow is the same four beats, however different the branding looks.

Why sites verify at all

An email address is only useful to a service if it reaches a real person. Without a check, anyone could sign up with someone-else@ and the service would have no way to reach the actual account holder, send a receipt, or allow a password reset. Verification proves two things at once: that the address exists, and that the person signing up can read mail sent to it. Everything else — welcome sequences, notifications, recovery — depends on that proof.

The four common patterns

Almost every service uses one of four mechanisms:

Three cards showing verification types: OTP code, magic link and confirm button
Codes, magic links and confirm buttons are the three shapes verification usually takes.
Six digit one-time code shown in boxes
An OTP is the most common modern pattern — short, time-limited and easy to type.

What happens behind the scenes

When you submit a form, the service records your address and generates a token — a long, unguessable string — then emails it to you as part of a link or code. The token is stored server-side with an expiry and a "used" flag. When you present it, the server checks that it matches, has not expired and has not already been consumed, and only then flips your account to verified.

That design explains the behaviour you see. A link that "only works once" is the used-flag doing its job. A code that expires after ten minutes is the timestamp doing its job. And a link that fails the moment you click it, even though you never opened the email, is usually a security scanner at your mail provider or a corporate gateway consuming the token first.

Double opt-in versus single opt-in

You will sometimes see the phrase "double opt-in". That describes a marketing list where the first opt-in (filling the form) is followed by a second, explicit confirmation by email. It is verification applied to consent rather than to identity. It is why a newsletter you signed up for sometimes waits for you to click a link before it starts arriving — and why, if you never click it, you never hear from the sender again.

Why a code sometimes never arrives

When verification mail goes missing, it is almost always one of a few causes:

Working through that list in order resolves nearly every case. Check the address, wait two minutes, request a resend, and only then consider that the service may not accept your chosen domain.

A note on security

Verification is about reachability, not secrecy. The fact that a service verified your address says nothing about how well it protects it. Treat verification as the start of a relationship, not a guarantee of good behaviour, and keep using the habits that protect you: unique passwords, a password manager, and a disposable address for anything you are only trying.

Once you can see verification as four beats — generate a token, send it, present it, mark it used — the whole ritual stops feeling arbitrary and starts being something you can reason about.

If you run a sign-up flow yourself

The same four beats that explain a user's experience are the checklist for building one. Generate tokens that are long and random, give them a short expiry, mark them single-use, and tell the user plainly when a link will stop working. Send a fresh code on request rather than reusing an old one, and make the resend button obvious. Finally, test the unhappy paths — expired token, reused token, wrong code — because those are the states real users hit most often and the ones most easily left broken.

Create a free inbox →

More guides