Delivery lab

Email missing?
Trace the delivery path

Don't keep refreshing or resend blindly. Answer a few questions to find out whether the issue is with the address, sender, delivery process, or email content.

AddressValidity

Verify the basics

Check every character of the address and make sure the current inbox is still valid.

SendingQueue

Estimate the wait

Verification codes usually arrive quickly, but bulk notifications and emails with attachments may take longer to leave the queue.

Short-termLong-term

Choose the right option

Use a temporary email for one-off tasks; switch to a manageable forwarding alias for ongoing conversations.

Interactive troubleshooting

Start with what you see

Results are based only on common delivery patterns. We don't read your emails or ask you to enter verification codes.

Step 1 of 3

Is this address still shown at the top of your current inbox?

Typical wait times

Different emails need different wait thresholds

Email typeTypical arrival windowAfter the window
Login verification codeA few seconds to 2 minutesReturn to the sending page and confirm the address. Resend only once to avoid rate limits.
Registration confirmation link1–5 minutesCheck whether the sender's page clearly confirms that the message was sent.
System notification1–15 minutesCheck whether the service uses a bulk queue or delayed delivery.
Email with attachmentSeveral minutes or rejectedCheck the attachment type and size; don't rely on a temporary inbox for important files.

These ranges are not delivery guarantees. Sender queues, DNS, reputation policies, and network conditions can all affect timing.

Five checks

Complete this checklist before resending

  1. Check the full address. Don't check only the address prefix—the domain and every character must match.
  2. Confirm the validity period. After changing addresses, emails sent to the old address won't automatically appear in the new inbox.
  3. Check the sending status. Clicking a button on a webpage doesn't mean the sender's system has accepted the request.
  4. Wait for a reasonable window. Repeatedly clicking resend may cause the newest code to replace the previous one or trigger a limit.
  5. Reduce content variables. Ask the sender to send a plain-text test email without an attachment first.
Receiving options

Short-term email and ongoing contact take different paths

Temporary inbox

Best for one-time verification, short-term downloads, and trials you don't need to recover. No registration required; the address expires when its validity period ends.

  • Reduce exposure of your primary email
  • Read messages directly on this page
  • Not for account recovery or important files
Generate a temporary address

Permanent forwarding alias

Best for subscriptions, project contacts, and services you may need to reply to later. Incoming messages are forwarded to your real email address.

  • Pause or resume the alias
  • View a 30-day delivery archive
  • Keep your real email address private from websites
Create a forwarding alias
FAQ

Key questions when a verification code doesn't arrive

Can I still receive messages sent to my old address after changing addresses?

There's no guarantee. The sender uses the address submitted at the time, while the new inbox has a different delivery path. Return to the sending page and update the address.

Will clicking “Resend” repeatedly make it arrive faster?

Usually not. The service may impose rate limits, and multiple verification codes may expire one after another. Wait for a reasonable window, then resend only once.

Why do regular notifications arrive while emails with attachments don't?

The attachment size, file type, or sender policy may trigger a rejection. Temporary email isn't suitable for exchanging important attachments; use a controlled long-term mailbox instead.

Can forwarding aliases also be delayed?

Yes. Forwarding adds another step to the delivery path, but the dashboard archive status can help distinguish between “received” and “forwarding failed.”