From send button to inbox: the ten-second trip
October 12, 2026 · 3 min read
When a website emails you a code, the message does not fly straight into the page you have open. It passes through a short chain of machines, and each link in that chain can add a few seconds. Knowing the chain makes most "where is my email?" moments easy to explain.
1. The sender looks up the domain
An address has two halves. The part after the @ is the domain, and that is the only part the sending server cares about at first. It asks the Domain Name System (DNS) for the domain's MX record, a short entry that says "mail for this domain goes to that server". No MX record, no delivery.
2. The two servers have a short conversation
The sending server connects to the receiving one and they talk in SMTP, a plain text protocol that is older than the web. The sender says who the message is from, who it is for, and then hands over the message itself. The receiver answers in one of three ways:
- Accepted: the message is now the receiver's job.
- Try again later: a temporary refusal. A well behaved sender queues the message and retries, often after a few minutes.
- Rejected: a permanent no. The sender usually gives up and may send a bounce notice.
3. Every name is already waiting
On MailPingBack you never "create" an address. Our domains accept mail for any name, so [email protected] works the moment someone sends to it. That is why you can type a name and use it straight away.
4. The message is unpacked and stored
An email arrives as one long block of text with headers on top and the body below, sometimes in several parts (plain text, HTML, attachments). We pull out the sender, subject, plain text and HTML, and store those. Attachments are not kept, and very large messages (around 2 MB and up) are turned away.
5. Your page asks for news
The inbox you have open checks for new mail every few seconds while you are using it. If you leave it alone for a while it checks less often, and after a long quiet spell it pauses until you click or press a key. The refresh button checks immediately.
Where the seconds go
Most of the waiting happens before the message reaches us, on the sender's side:
- Queues. Busy sites put outgoing mail in a line and send in batches.
- Retries. If a server somewhere along the way said "try again later", the next attempt may be minutes away.
- The sender's own checks. Some services scan or rate-limit outgoing mail before it leaves.
- A typo. One wrong letter sends the message to a different inbox, or nowhere.
A quick checklist
- Use the Copy button instead of retyping the address.
- Check that the domain in the form matches the one selected on the page.
- Give it a minute, then press refresh.
- Ask for one resend, not ten. Many sites slow down or block repeated requests.