Agent view · Findings · 2026-08-13
Email bounce case study: one typo, every address dead
This is the response this server returns to a client that asks for Accept: text/markdown at https://crawlcheck.io/blog/one-character-of-undeliverable-email: 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/one-character-of-undeliverable-email>; 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 | 14,728 |
| words | 2,180 |
| sha-256 | 2d66f96e48d34fcfa3a58b28a96ae7a508e9b1bef1741f10a327250ff1b9670e |
| repr-digest | sha-256=:LWb5bkjTT8+jpYsoqWrnpQjpsb7xdB8QoyclD/G5Zw4=: ← matches the body shown |
| signature-input | sig1=("@authority";req "@path";req "repr-digest" "content-type");created=1795182066;expires=1795185666;keyid="1hHmE3fo1rg5Ig70wuFtJ5wBc7G-sUTgUJkxyPWFRps";alg="ed25519";nonce="RQj27qviNOeDMN0kB7yvjw";tag="crawlcheck-page" |
| signature | sig1=:0Gx3IGBea+ftrsOp3YGOw2fItk4vrZbLUVTsQPBN6Aj3pAjR+H9rTbTm1VY3ZD4q0tFj2jM21WkK90dzPtxDDg==: |
| verified | yes — signature by key 1hHmE3fo1rg5Ig70… from https://crawlcheck.io/.well-known/http-message-signatures-directory (directory valid), valid for 3600 more s. Checked here exactly as a crawler would; redo it yourself: https://crawlcheck.io/api/tool/wba |
Findings · 2026-08-13 · By [VSNARY | Emmanuel Orta](/author) # Email bounce case study: one typo, every address dead A contractor site linked the same misspelled address on every page. Two DNS lookups proved which spelling could receive mail, and the fix took one line. A single typo in the domain of a contact address makes a business unreachable by email, and nothing on the page looks wrong. On the site we measured, the misspelled domain returned NXDOMAIN, so every message bounced at the sender, while the real domain had working mail exchangers. A mailto is not a link crawlers or link checkers follow, so no tool flagged it. Look up the MX record for every published address and send a real test message from outside: validate the mailbox, not the string. On this page - How did two DNS lookups prove it? - Why did nobody notice? - What does each DNS answer mean for mail? - How do you check your own contact addresses? - Where does the misspelling live? - Would a scan have caught it? - What is the general lesson? Two DNS lookups, one answer **The real domain**MX records present, mail accepted **The linked domain**no MX record — every message bounced A Denver contracting site we operate linked the same `mailto:` address on its homepage, contact page, quote page and every service page. It was the only email address on the site, and its domain was misspelled by a single typo. The page rendered normally, every link checker passed it, and every message a visitor sent bounced. ## How did two DNS lookups prove it? # We did not decide what the address should be. We asked DNS which spelling could receive mail at all. | Domain in the mailto: link | DNS answer | Result | | --- | --- | --- | | The linked domain, misspelled | NXDOMAIN: no address record, no mail exchanger | every message bounced | | The company’s real domain | live address record and Google Workspace mail exchangers | mail accepted | Only one spelling exists, and it receives. That is the difference between a correction and a guess. ## Why did nobody notice? # A bounce goes to the sender, not to the business. The owner sees fewer enquiries and nothing in any dashboard says why. A `mailto:` is not a link a crawler or link checker follows, so no tool reports it either. It is the same class of failure as [a machine file that answers 200 and cannot be read](/blog/a-file-that-answered-200-and-could-not-be-read): every layer did its own job and reported success. The only party that learned anything was a stranger, who got a bounce from a domain they had never heard of and moved on to the next contractor. ## What does each DNS answer mean for mail? # The lookup on the domain after the @ returns one of four states. Reading them loosely produces a false accusation, which is worse than no check. | DNS answer | What it means for mail | What to do | | --- | --- | --- | | **NXDOMAIN**: the name does not exist | Nothing can deliver. Every message bounces at the sender’s own mail server. | The address is wrong. Find the spelling that resolves. | | **MX records present** | Someone accepts mail for the domain. Whether the mailbox exists is a separate question. | Send a test message from outside and wait for a human reply. | | **No MX, but an A or AAAA record** | Mail falls back to the web host. It may deliver, bounce, or land on a server nobody reads. | Treat as unverified. Ask where mail actually lands. | | **A single MX of .** (null MX, RFC 7505) | The domain declares it never accepts mail. | The address is deliberately dead. Remove it. | Only the first and last rows are proof. An MX record shows a door exists, not that anyone is behind it, and a bare A record shows nothing about mail at all. This case sat in the first row, which is why it could be stated plainly. ## How do you check your own contact addresses? # For every address published on the site, take the domain after the @ and ask DNS the question a sender’s mail server will ask: ``` dig +short MX example.com dig example.com | grep status ``` The first line lists the mail exchangers; empty output means none. The second shows `status: NXDOMAIN` when the name does not exist at all. Then send a real message to each address from an account outside your own mail system and confirm a person receives it. Checking that the text looks right is not a check. ## Where does the misspelling live? # On this site all three copies came from one string, so all three carried the typo and one edit fixed all three. When the copies drift apart instead, each needs checking separately. A contact address sits in at least three places that drift independently: the `mailto:` link, the `email` property in the [structured data](/glossary/structured-data), and the visible text. Here all three carried the typo because all three were pasted from the same source at launch, which is also why the fix was one line. The worse case is when they disagree: a machine and a human are told different things, and neither can tell. [The NAP consistency guide](/guides/nap-consistency-audit-phone-address-and-coordinates) covers checking that every copy of a contact fact matches. ## Would a scan have caught it? # Not at the time. CrawlCheck compares the contact details a site declares, in its structured data and on its page, against each other, and in this case they agreed perfectly, typo included. The two lookups above were run by hand and the correction made by hand; no automated finding fired. A mail check is only worth adding if it reports all four states above rather than collapsing them into working and broken, and never marks a domain down for the two that prove nothing, the same rule that keeps [unverifiable claims out of the score](/blog/the-two-facts-almost-nobody-publishes). ## What is the general lesson? # Contact details are the part of a site a machine reads out loud and the part nobody re-reads after launch. Check that every address, phone number and profile link resolves to something that answers, by asking the network the same question a stranger’s mail server will ask. 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%2Fone-character-of-undeliverable-email%3Futm_source%3Dlinkedin%26utm_medium%3Dsocial%26utm_campaign%3Dshare)[X](https://twitter.com/intent/tweet?url=https%3A%2F%2Fcrawlcheck.io%2Fblog%2Fone-character-of-undeliverable-email%3Futm_source%3Dx%26utm_medium%3Dsocial%26utm_campaign%3Dshare&text=Email%20bounce%20case%20study%3A%20one%20typo%2C%20every%20address%20dead)[Email](mailto:?subject=Email%20bounce%20case%20study%3A%20one%20typo%2C%20every%20address%20dead&body=https%3A%2F%2Fcrawlcheck.io%2Fblog%2Fone-character-of-undeliverable-email)[Follow Emmanuel on LinkedIn](https://www.linkedin.com/in/emmanuelorta) ## Questions this post answers ### How do I check whether my contact email address works? Look up the MX record for the domain after the @ and confirm the name exists, then send a real message from an account outside your own mail system and confirm a person receives it. Checking that the address looks right proves nothing. ### What does NXDOMAIN mean for an email address? The domain does not exist, so no mail server can deliver to it. Every message bounces at the sender's own server, and the business never learns that anyone tried. ### Does an MX record prove an email address works? No. It shows that some server accepts mail for the domain, not that the particular mailbox exists or that anyone reads it. Only a delivered test message answered by a person proves that. ### Why do link checkers miss a broken mailto link? A mailto link is not fetched like a web link. Crawlers and link checkers do not follow it, so a misspelled domain inside it passes every check that only tests whether links load. ### Does a broken contact address affect search? Not directly as a ranking factor. It affects whether a business can be contacted from a result, and a wrong address copied into directory listings breaks the consistency engines use when deciding which facts about a business to trust. ### What is a null MX record? A single MX record pointing at a dot, defined in RFC 7505. It declares that the domain never accepts mail, so any address on it is deliberately dead and should be removed from the site. ## Related findings [2026-10-29 Google's Googlebot check passes 198 of 200 rented servers Google's three-domain Googlebot rule accepts any Google Cloud server: 198 of 200 sampled addresses passed. Two tools tested, the f](/blog/googles-googlebot-verification-rule-passes-any-google-cloud-server)[2026-11-18 "20 years of experience": the site's own records said 13 A contractor site claimed 20 years of experience; its Google profile opening date made it 13. The claim was on 6 pages in 3 differ](/blog/a-site-said-20-years-of-experience-its-own-records-said-13)[2026-08-21 Why word count cannot spot a parked domain: 783 words A domain parking page with 783 words passed every thin-content check. How to tell a parked page from a real site: check who serves](/blog/a-783-word-parking-page-defeats-every-thin-content-check) 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:** [Keys](/keys) · [/](/) · [Listing check](/listing-check) · [SDK](/sdk) · [Conduct: ClaudeBot](/agents/conduct/claudebot) | **Datasets:** [Technologies: Linkedin insight](/datasets/technologies/linkedin-insight) · [Technologies: Adobe fonts](/datasets/technologies/adobe-fonts) | **Blog:** [AI crawlers on Wix, Shopify, Squarespace, Webflow: 980 sites](/blog/what-ai-crawlers-get-from-wix-shopify-squarespace-webflow-sites) | **Glossary:** [entity map parity](/glossary/entity-map-parity) · [Metadata filtering](/glossary/metadata-filtering) · [Content type](/glossary/content-type) · [Referring domain](/glossary/referring-domain) [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/one-character-of-undeliverable-email.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.