Agent view · Findings · 2026-09-30
Five days of our alerts went to an address with no mailbox
This is the response this server returns to a client that asks for Accept: text/markdown at https://crawlcheck.io/blog/five-days-of-our-alerts-went-to-an-address-with-no-mailbox: fetched when you opened this page, shown byte for byte. An assistant, a crawler that negotiates markdown, or anything reading our feed gets exactly this. The markdown leaves signed (RFC 9421, key in our key directory), so a crawler can prove the page it read is the page this server sent; the check is shown below.
| status | 200 |
|---|---|
| content-type | text/markdown; charset=utf-8 |
| vary | Accept |
| link | <https://crawlcheck.io/llms.txt>; rel="describedby"; type="text/plain", <https://crawlcheck.io/.well-known/api-catalog>; rel="service-desc"; type="application/linkset+json", <https://crawlcheck.io/blog/five-days-of-our-alerts-went-to-an-address-with-no-mailbox>; rel="cite-as", <https://crawlcheck.io/.well-known/http-message-signatures-directory>; rel="http-message-signatures-directory" |
| cache-control | public, max-age=900, stale-while-revalidate=2400 |
| bytes | 12,050 |
| words | 1,700 |
| sha-256 | 224a3c0dfcd33f6631eb8a28203f7996495065b1b4df602de93e3df67066f70f |
| repr-digest | sha-256=:Iko8DfzTP2Yx64ooID95lklQZbG032At6T499nBm9w8=: ← matches the body shown |
| signature-input | sig1=("@authority";req "@path";req "repr-digest" "content-type");created=1795182068;expires=1795185668;keyid="1hHmE3fo1rg5Ig70wuFtJ5wBc7G-sUTgUJkxyPWFRps";alg="ed25519";nonce="KtxDVn1iKiVu_UWLI2lBJw";tag="crawlcheck-page" |
| signature | sig1=:w7WTPYhQAfj8FBazgI6Rns6wqcy9kMUMkGkM4wpNncBqxU7z/7MIS4iaAovFOmQ3Bs2DvlVsyBxW+cXJI5svAQ==: |
| verified | yes — signature by key 1hHmE3fo1rg5Ig70… from https://crawlcheck.io/.well-known/http-message-signatures-directory (directory valid), valid for 3599 more s. Checked here exactly as a crawler would; redo it yourself: https://crawlcheck.io/api/tool/wba |
Findings · 2026-09-30 · By [VSNARY | Emmanuel Orta](/author) # 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. On this page - What happened? - Why did nothing catch it? - What changed? - How do you avoid this on your own domain? Four places we could look: what each reported, what was true Our own logs What it reported sent, no error What was true the send was accepted Sending service What it reported accepted What was true address blocked after the first bounce New mail provider What it reported user unknown, once What was true the address did not exist there yet Monitoring What it reported all green What was true every check measured sending, not receipt 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](/blog/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](/guides/how-to-move-dmarc-from-none-to-quarantine-without-losing-mail) covers the order of steps. **Live, as you read this:** the corpus now holds 570,959 domains across 9,163 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. Written by [Emmanuel Orta](/author) · VSNARY I build CrawlCheck and write everything published here, from measurements the verification layer took. Where a post got something wrong, the correction stays in the post. [Every post, and where I got it wrong →](/author) · [Follow on LinkedIn →](https://www.linkedin.com/in/emmanuelorta) Share this finding: [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcrawlcheck.io%2Fblog%2Ffive-days-of-our-alerts-went-to-an-address-with-no-mailbox%3Futm_source%3Dlinkedin%26utm_medium%3Dsocial%26utm_campaign%3Dshare)[X](https://twitter.com/intent/tweet?url=https%3A%2F%2Fcrawlcheck.io%2Fblog%2Ffive-days-of-our-alerts-went-to-an-address-with-no-mailbox%3Futm_source%3Dx%26utm_medium%3Dsocial%26utm_campaign%3Dshare&text=Five%20days%20of%20our%20alerts%20went%20to%20an%20address%20with%20no%20mailbox)[Email](mailto:?subject=Five%20days%20of%20our%20alerts%20went%20to%20an%20address%20with%20no%20mailbox&body=https%3A%2F%2Fcrawlcheck.io%2Fblog%2Ffive-days-of-our-alerts-went-to-an-address-with-no-mailbox)[Follow Emmanuel on LinkedIn](https://www.linkedin.com/in/emmanuelorta) ## 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 [2026-11-13 A newsletter form that lost every sign-up On a shop we run, the newsletter form sent no email address and carried an expired token. How we found it and how to test yours.](/blog/a-newsletter-form-that-lost-every-sign-up)[2026-08-28 How to check if AI crawlers can read your site Five curl checks that show whether GPTBot, ClaudeBot and PerplexityBot can read your site: content type, cache, crawler vs browser](/guides/how-to-check-if-ai-crawlers-can-read-your-site)[2026-08-29 Missing referrer is not direct traffic: 93% of our arrivals sent none We measured arrivals on five sites we operate with our own first-party beacon. 92.9% arrived with no referrer. That number decides](/blog/ninety-three-percent-of-our-arrivals-sent-no-referrer) 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. [Fix it all — $100](https://buy.stripe.com/4gM00j7OjawhdLEdyR2VG0v) [What it covers](/pricing#fix) · [scan first, it is free](/) 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. [Add to Chrome — free](https://chromewebstore.google.com/detail/plgjengobhbdmbgckiiaaflgiepdbcpi?utm_source=crawlcheck.io&utm_medium=post) [What it does](/extension) 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. [Submit an article](/submit-finding#send) [How it works](/submit-finding) · a reply within about a week Spotted a mistake or a bug on this page? [Report an error](/report-error?k=article). Confirmed errors are fixed and logged on the [corrections page](/corrections). ## 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](/api/comment/signed)). Those appear at once, marked *verified*. Send for review Writing about this? [Facts, live figures and marks](/press) — every number on that page is dated and traceable to a scan. [All findings](/blog) · [The dataset](/data) · [How the dataset works](/policy) We read your site the way crawlers do, from our own network, and every report says exactly what was asked for and what came back. [Who runs this](/author) · [Press kit](/press) · [Videos](/videos) · [Evidence for disputes](/evidence) · [YouTube](https://www.youtube.com/@crawlcheck) · [hello@crawlcheck.io](mailto:hello@crawlcheck.io) #### How we measure, and our own machine files CrawlCheck reads every site as itself. Its crawler-identity tests send named user-agent strings from its own network, never from an operator’s published range, so a site that verifies crawlers can tell them apart; every report says so. Results reflect what an anonymous non-browser client receives. [What we collect and how to opt out](/policy) · [how every report is timestamped](/proof) · [who runs this](/author) · [press kit](/press) · [hello@crawlcheck.io](mailto:hello@crawlcheck.io). **Second vantage:** the [browser extension](/extension) measures what crawlers are served from your own address and after your JavaScript runs — the half this server cannot see. From 1.0.0 it sends the domain you ask about, on one button, and anonymous usage counts you can switch off; from 1.0.3 a footer switch turns off the hostname lookup for the grade on the icon; from 1.0.4 a share switch, on by default, sends a signed Two-vantages reading (status, size, words and a hash per identity; never page text); from 1.0.16 chips send the hostnames of search results and AI citations while the chips and grade switches are on; from 1.0.17 a readings switch, on by default, sends one signed page reading a day (numbers, the hostname and the page address with the query removed; never in incognito; at most 40 a day) and only while the share and grade switches are also on. Earlier versions send nothing. **Our own machine layer for the agentic web:** [llms.txt](/llms.txt) · [llms-full.txt](/llms-full.txt) · [agents.md](/agents.md) · [SKILL.md](/SKILL.md) · [entitymap.json](/entitymap.json) · [media kit](/.well-known/media-kit.json) · [MCP server card](/.well-known/mcp/server-card.json) · [API catalog](/.well-known/api-catalog) · [OpenAPI](/openapi.json) · [robots.txt](/robots.txt) · [sitemap.xml](/sitemap.xml) · [security.txt](/.well-known/security.txt) — every one named in robots.txt, which is exactly what we check for on yours. **Pages:** [Certificates](/certificates) | **Registry:** [MCP: Operator](/registry/mcp/operator) · [MCP](/registry/mcp) · [AI policy](/registry/aipolicy) · [aliyun.com](/registry/aliyun.com) · [cpanel.net](/registry/cpanel.net) · [ggsoftwarelabs.com](/registry/ggsoftwarelabs.com) · [machsoft.com.tr](/registry/machsoft.com.tr) | **Glossary:** [Brotli](/glossary/brotli) · [Orphaned entity](/glossary/orphaned-entity) · [tool lockfile](/glossary/tool-lockfile) · [noimageindex](/glossary/noimageindex) [Contact](/contact) · [Partnerships](/partnerships) · [Terms of service](/terms) · [Refund policy](/refunds) · [Trust center](/trust) · [Subprocessors](/subprocessors) · [Changelog](/changelog) · [Report an error](/report-error)
Same body as a file: /blog/five-days-of-our-alerts-went-to-an-address-with-no-mailbox.md · as data: /feed.json · what we tell agents site-wide: /llms.txt, /agents.md. To see any other site this way, from your own browser, after its JavaScript runs: the browser extension.