Verification Email Not Arriving? 10 Things to Check, in Order

By the MailboxTemp Editorial Team · Published · Updated

Verification codesEmail tips

A verification email not arriving almost always has one of ten explanations, and they are not equally likely. Most of them are inside your own mailbox or in the address you typed; only the last few are the sender's fault. Checking in order takes five minutes and avoids the one thing that makes the problem worse.

In rough order: it is in your mailbox but not the inbox, the address you typed is not the address you own, the account already exists so the site sent something else, the mail is still in a retry queue, the code arrived and expired, a filter or forwarding rule moved it, you are on the sender's suppression list, the sender's authentication is failing, or the site quietly refuses the kind of address you used.

The one thing that makes it worse is the resend button. On most systems a new code invalidates every earlier one, so pressing resend four times while the first email is still in transit leaves four messages of which only the last works — and the code from the first one to land then fails, which looks exactly like the site being broken. Many senders also rate-limit resends. Press it once, then stop and read on.

The first three checks: ninety seconds

1. Search the whole mailbox, not just the inbox

Scanning the inbox alone is the most common mistake, because the message may never have been shown there. Search instead of looking, across all folders: the sender's domain, then verify, confirm and code separately.

If you find it in spam, do not just open it — mark it as not spam, which teaches the filter. Otherwise the next code from that sender lands in the same place.

2. Re-read the address you actually submitted

Domain typos are the ones that survive scrutiny, because the local part looks right: gmial.com, outlok.com, yaho.com. Two more to rule out: a browser autofill that quietly used an old address, and a plus address such as you+shop@example.com whose filter has already filed the mail out of sight.

3. Check whether the account already exists

Sites avoid telling you an address is already registered, because that would let anyone test whether you have an account. Signing up again with an existing address therefore often sends a password reset, or a "someone tried to register" notice, instead of a verification link. Try the login and password reset flows before assuming delivery failed.

When is it probably still on its way?

4. Greylisting and ordinary queue delay

Mail delivery is allowed to be slow. If the receiving server does not recognise the sender, it can reply with a temporary failure — a 4xx code — telling the sender to try again later rather than to give up. This is greylisting, and it exists because much spam software never retries. Legitimate senders do, but the gap is typically several minutes and can be fifteen or more, so the message only reaches you on the second attempt.

Large senders are usually exempt because receiving servers already know them; a small site running its own mail server is where greylisting bites. Give it ten to fifteen minutes. If the mail arrives late, the Received headers carry a timestamp at every hop, and reading those headers in order shows where the delay was.

5. The code may have arrived and already expired

Verification codes are short-lived by design, often five to fifteen minutes, and reset links rarely last beyond an hour. If you requested a code, got distracted, and came back to an email the site now rejects, the clock is the problem, not the delivery. Request one more and use it immediately — the newest code is the only live one.

One caution: a code you did not request is not a delivery glitch. It means someone else is trying the first half of this process with your address, and the common ways codes get intercepted rely on you treating it as routine.

What we see on our side when a code is sent

It helps to know what "delivered" looks like from the receiving end. While writing this update we sent a labelled test message to a fresh MailboxTemp inbox through our own mail server and timed every step. The sender's conversation with the server, verbatim:

220 mail.mailboxtemp.com ESMTP Haraka/3.2.1 ready
250 sender <verify@mailboxtemp.com> OK
250 recipient <wrl4u9a@fakhita.xyz> OK
354 go ahead, make my day
250 Message Queued (242A6D5B-415C-496C-8ADC-3F2F6EEAC9A2.1)

From opening the connection to that final 250 took 133 milliseconds, 9 of them between the end of the message and the acceptance. The message was then parsed, stored, and visible in the inbox's API listing 333 milliseconds after acceptance: a first poll a quarter of a second after the handshake came back empty, the second one contained the message, with the server's own received_at stamp 639 milliseconds after the sender's Date header.

The same session produced two refusals worth recognising. A message whose envelope sender was at a domain with no mail (MX) record was refused before any content was sent: 550 No valid MX for your FROM address. A message to an address whose inbox had expired got 550 Mailbox not found or expired. Both are permanent failures that the sender sees as a bounce and the recipient never sees at all.

Symptom to cause: a quick decision table

What you observeMost likely causeWhat to try first
Nothing after 2 minutes; other mail arrives fineFiled in spam, a tab or a folderSearch in:anywhere for the sender's domain
Nothing after 15 minutes from a small siteGreylisting retry, or the sender's domain fails checksWait, then request one code to a different provider
Code arrives but the site rejects itExpired, or an older code after a resendUse only the newest message, immediately
Arrives late, then arrives fine every time afterGreylisting on the first contactNothing; it is working as designed
Nothing, ever, from this one sender onlySuppression list or failing SPF/DKIM/DMARCAsk their support to check the suppression list
Form says "sent", nothing at any address typeSilent rejection of disposable, role or new-TLD addressesTry a mainstream address once as a diagnostic
Password reset arrives instead of a codeThe account already existsUse the reset; you are already registered

Checks inside your own mailbox

6. Filters, rules and forwarding you set up and forgot

A rule written years ago to tidy up newsletters can match a verification email by accident — anything filtering on "offer", "account" or a sender domain you once muted. Open your provider's filter list and read it. Two things matter: rules that archive or delete silently, and any forwarding rule or recovery address you do not recognise. An unexplained forwarding rule is the most serious thing on this page — remove it, then change your password.

7. A full or dormant mailbox

Mailboxes at quota reject new mail outright, and some free providers deactivate accounts left unopened for months. Both produce a hard bounce the sender sees and you do not. If you are waiting at an address you rarely use, send yourself a test message from another account first.

8. You are on the sender's suppression list

This is the invisible one. If mail to your address bounced before, or you once clicked "report spam" on something from that sender, their platform may have added you to a suppression list and now refuses to send to you at all — no bounce, no error, nothing visible at either end. Marking an old message "not spam" does not undo it. Ask the site's support to clear the suppression, or register a different address.

Checks on the sender's side

9. The sender's authentication is failing

Receiving providers check that a message really comes from the domain it claims, using three records the sending domain publishes. When a site has just changed email providers, or sends through a third party it never authorised properly, those checks fail and the mail is filed as spam or rejected silently. You cannot fix someone else's DNS, but you can recognise the pattern — nothing from this one sender ever arrives while everyone else's mail is fine — and a read of what SPF, DKIM and DMARC verify tells you what to put in the support ticket.

10. The site refuses the kind of address you used

Some signup forms accept an address, show a success message, then never send anything, because the address failed a check behind the scenes. Three categories trigger it:

The form rarely says which. If you used any of the three, try a mainstream address once as a diagnostic.

What to do if nothing has arrived after twenty minutes?

Escalate in this order.

  1. Request one code at a different address on a different provider — that separates a sender problem from a mailbox problem in a single step.
  2. Look for an alternative route: many services verify by SMS, through an existing social login, or via an in-app prompt, and any of those gets you in today.
  3. Contact support with details they can look up: the address, the exact time you requested the code, and your time zone.

"I did not get the email" earns a reply telling you to check your spam folder. "I requested a code at 14:12 UTC today for this address, and your logs should show whether it was sent, bounced or suppressed" gets it read by someone who can act.

Reducing the odds next time

Two habits remove most repeat occurrences. Keep the address you use for real accounts out of newsletter and competition forms, so a verification email never competes with marketing for the same folder. And when a site wants an address only as a turnstile — a gated download, a one-off code — send it somewhere disposable, where the only message in the inbox is the one you are waiting for and the inbox refreshes while you watch it.

Sources

Frequently asked questions

How long should I wait before deciding the email is not coming?

Give it fifteen to twenty minutes before escalating. Most verification mail from large senders arrives within seconds, but greylisting means a legitimate message can sit in a retry queue for ten minutes or more before a second delivery attempt succeeds. Waiting costs you nothing; pressing resend repeatedly during that window invalidates earlier codes and can trigger rate limits, which does cost you something.

Does pressing resend several times make the email arrive faster?

No, and it usually makes things worse. Each new request typically invalidates all previous codes, so if several messages eventually land, only the newest one works — typing the code from an earlier email then fails for a reason that has nothing to do with delivery. Many senders also cap resends per address per hour. Request once, wait, and if you do request again, use only the most recent code.

How fast should a verification email arrive when everything is working?

Under a second between the sending server handing the message over and it appearing in the mailbox. In a timed test on our own server, acceptance took 133 milliseconds and the message was readable through the inbox API 333 milliseconds later. Anything beyond a minute means a queue, a retry or a filter is involved, not normal delivery.

Why do verification emails from one specific site always go to spam?

Consistent spam filing for a single sender usually points at that sender's configuration rather than at your filter — most often failing authentication checks, or sending through a third party their domain has not authorised. Marking the message as not spam helps your own future mail from them. Reporting it to their support, mentioning that messages are being filed as spam, is what gets the underlying record fixed.

Can a site accept my address at signup and then never send anything?

Yes, and it is common. Validation that happens after the success message, a blocklist entry for the address type, a role address such as info@, or a suppression list from an earlier bounce or spam complaint all produce silence rather than an error. Trying one code at a mainstream provider address distinguishes this case from every other cause in a single test.

Get a free temporary inbox →