Reading SMTP Received hops bottom-to-top
Every mail transfer agent (MTA) that touches an email prepends a new Received: line to the top of the message header. Because each relay adds its stamp on top, the chronological journey of an email always reads from bottom to top: the lowest Received header is the sending origin, and the topmost header is the recipient's final mail server.
Comparing consecutive timestamps across hops immediately exposes where an OTP or password-reset email got stuck. If hop #1 to hop #2 took 1 second, while hop #2 to hop #3 took 45 seconds, the bottleneck lives at the intermediate relay or greylisting filter — not in your application code. You can paste raw headers directly into our browser-local Email Header Analyzer to calculate hop-by-hop delays automatically.
SPF, DKIM, and DMARC in plain English
Modern inbox providers (Google Workspace, Microsoft 365, Apple iCloud) inspect three DNS-backed authentication controls inside the Authentication-Results header before deciding whether to inbox, quarantine, or reject a message:
| Protocol | DNS Record Location | What It Verifies |
|---|---|---|
| SPF | TXT @ domain.com | Whether the connecting sending IP is authorized by the domain's v=spf1 policy. |
| DKIM | TXT selector._domainkey | Cryptographic RSA/Ed25519 signature proving headers and body were not altered in transit. |
| DMARC | TXT _dmarc.domain.com | Domain alignment between From: and SPF/DKIM, plus reject/quarantine instructions on failure. |
How DNS MX records route incoming mail
Before an outbound mail server sends a single byte of SMTP traffic, it queries DNS for the recipient domain's MX (Mail Exchange) records. Each MX entry specifies a target mail host and a numeric priority where lower numbers have higher preference (for instance, priority 1 is tried before priority 5 or 10).
If a domain has zero MX records and no fallback A/AAAA mail listener, emails sent to that domain will permanently bounce. Running a live check in our Email Domain MX Checker queries real DNS records in real time and identifies the underlying provider (Google Workspace, Microsoft 365, Proton Mail, Cloudflare Email Routing, Zoho, or self-hosted MX) alongside live SPF and DMARC TXT records.
Validating email syntax and MX deliverability
Catching malformed or undeliverable addresses at form submission saves bounce reputation. A complete pre-send check combines three layers available in our Email Address Validator and RFC 5322 Format Validator:
- RFC 5322 syntax verification: Checks total length (≤ 254 characters), local-part bounds (≤ 64 characters), consecutive or edge dots, valid hostname labels, and support for
+tagsub-addressing. - Typo & disposable awareness: Catches common user typos (
gamil.com,hotnail.com,outlok.com) and checks domains against our Disposable Email Domain Checker. - Live MX resolution: Confirms the domain actually publishes mail exchange servers capable of receiving SMTP mail.
A 60-second deliverability debug checklist
Whenever verification emails stop landing in user inboxes, walk through these four checks in order:
- Run your sending domain through the MX / SPF / DMARC Checker to verify valid TXT policies.
- Send a real test message to a fresh Tempboxy testing inbox and inspect the extracted OTP, HTML preview, and tracker score.
- Export the message as
.emlor copy raw SMTP headers into the Email Header Analyzer to confirmspf=pass,dkim=pass, anddmarc=pass. - Run the subject and HTML body through the Spam Score Audit to catch missing plain-text fallbacks or unintended tracking pixels.