Findings · 2026-09-30 · By VSNARY | Emmanuel Orta
Five days of our alerts went to an address with no mailbox
After a mail migration, the address our alerts were sent to had no mailbox behind it. Every message was marked sent and none arrived, for five days.
From 19 to 24 September 2026, alerts that crawlcheck.io sends to its own operator were marked sent and never arrived. The domain's mail had moved to a new provider, the address the alerts went to had not yet been set up there, and after the first message bounced the sending service quietly stopped delivering to it. Every check measured sending, none measured receipt. Alerts now go to a mailbox confirmed to receive. The check that catches this is a daily test message whose arrival is confirmed by reading the inbox.
For five days in September every alert this site sends to its own operator was marked as sent and read by nobody. Nothing errored. No leads were lost, because lead records are saved before any notification goes out. What was lost was five days of knowing about them promptly.
What happened? #
On 18 September the domain's mail moved to Google Workspace. The address the alerts were sent to was going to be set up on the new provider, and that step had not been done yet. The next message bounced as "user unknown". A sending service treats that as a permanent failure and stops delivering to the address, which is the right behaviour. From then on, every alert was accepted, marked sent, and dropped.
| What we could see | What it reported | What was true |
|---|---|---|
| our own logs | sent, no error | the send was accepted |
| sending service | accepted | address blocked after the first bounce |
| new mail provider | user unknown, once | the address did not exist there yet |
| monitoring | all green | every check measured sending, not receipt |
Why did nothing catch it? #
Every check measured the act of sending. None measured arrival, and arrival is the only thing that matters for an alert. It was found on 24 September by asking a plain question: did today's message actually arrive? It had not, for five days. Our earlier case study on one character of undeliverable email showed the same thing from the sending side.
What changed? #
The same day, alerts were pointed at a mailbox confirmed to receive, the block on the old address was cleared, and a test message was confirmed by reading it in the inbox rather than by reading a send log. The migration checklist now has a step it lacked: list every address the site sends to, and confirm each one receives before the mail records move.
How do you avoid this on your own domain? #
Before moving a domain's mail, list every address your website, forms and tools send to, create each one on the new provider, and send a test to each. After the move, run a daily test message to the alert address and alert on its absence, not on a send failure, because the send never fails. If you are tightening mail authentication at the same time, our guide to moving DMARC to quarantine without losing mail covers the order of steps.
Live, as you read this: the corpus now holds 570,959 domains across 9,162 scans. The figures in this piece were measured on the date above; this line is not.
CrawlCheck’s dataset when this page loaded: 570,959 sites measured.
Share this finding:LinkedInXEmailFollow Emmanuel on LinkedIn
Questions this post answers
What happened to the alerts?
The address they were sent to had not been set up on the domain's new mail provider. The first message bounced, the sending service stopped delivering to that address, and every later alert was accepted and dropped for five days.
Why did the logs say sent?
The sending service accepted every message. Refusing to deliver to an address after a hard bounce is a delivery decision, not a send error, so nothing failed from the sender's point of view.
Were any leads lost?
No. Lead records are saved before any notification is sent, so they were all intact. The delay was in knowing about them.
What check catches this kind of failure?
A daily test message to the alert address, with something that reads the inbox and raises an alarm when the message does not arrive.
What should I check before moving my domain's email?
List every address your site and tools send to, create each one on the new provider, and confirm each receives a test message before switching the mail records.
Related findings
The main product
Found this on your own site? We fix it for $100.
Scan free to see where you stand. The fix is one site, every finding implemented and re-measured, with a sealed before and after.
Free browser extension
Check this on any site you open, without leaving the page.
CrawlCheck for Chrome grades every site you visit A–F and shows, from your own browser, what search engines and AI assistants are actually served. Free, no account.
Write for the library
Measured something yourself? Submit an article.
Send your finding, the data and the method. A person reads every submission and replies by email; accepted articles are published under your name with a link to your study. Free to submit. Articles are accepted on merit; no one can pay to have one published.
How it works · a reply within about a week
Spotted a mistake or a bug on this page? Report an error. Confirmed errors are fixed and logged on the corrections page.
Comments
Comments are read before they appear. Nothing is published automatically, and no account is needed. An AI agent with a published signing key can post without the queue: it signs the request and the signature is checked against its own domain (how). Those appear at once, marked verified.
Writing about this? Facts, live figures and marks — every number on that page is dated and traceable to a scan.