The contact address on your site cannot receive mail
Your site publishes “the published address” as a way to reach you, and the domain it belongs to accepts no mail.
0% · n=31 · as of 15 September 2026 of sites ShipReady scanned had this, counted across sites where this check completed.
Why it matters
Your site publishes “the published address” as a way to reach you, and the domain it belongs to accepts no mail. Anyone who writes to it gets a bounce, and you never find out they tried — there is no copy of the message on your side and nothing to see in any dashboard, so the symptom is simply that nobody ever contacts you. Either configure mail for the domain (an MX record pointing at your mail provider, or a forwarding service if you only need to receive), or change the address on the site to one you actually read. Then send a message to it from an unrelated account and confirm it arrives.
How ShipReady detects it
A contact address published on the site whose domain cannot accept mail. SITE-scoped because the address can be on any crawled page — a footer on every route, or only the contact page — and because the DNS answer is one fact about the domain however many pages published it. Findings are stamped with the page the address was read from, so the report can show the reader where they wrote it. Extraction is the same deterministic pass the Content & UX pillar already uses (scanner/content/claims.py); nothing here interprets the copy.
Detection is deterministic. ShipReady reports this only when it observes the condition directly, and prefers to miss a real problem over inventing one. Rule version 1.0.0.
How to fix it
This is the prompt ShipReady puts in your report — written to be pasted straight into Cursor, Claude Code, or whichever assistant built the app.
The contact address published on your site is at your domain, and that domain cannot accept mail — so every message a customer sends you bounces, and nothing tells you it happened. Decide which you want. To RECEIVE mail at your domain: add the MX records your mail provider gives you (Google Workspace, Microsoft 365, Fastmail, Zoho), or — if you only need to receive and forward — use a forwarding service such as your registrar's built-in email forwarding, Cloudflare Email Routing, or ImprovMX, each of which is a couple of DNS records and free at small volume. If the domain deliberately accepts no mail (it is a marketing-only or API-only domain), keep the null MX and change the address shown on the site to a mailbox you actually read. Either way, finish by sending a test message from an unrelated account — a Gmail address, not one at the same domain — and confirming it arrives. While you are in DNS, make sure the domain still publishes SPF and DMARC even if it receives no mail; a non-sending domain should publish "v=spf1 -all" and a DMARC record at p=reject so it cannot be forged.
Frequently asked questions
- What does "The contact address on your site cannot receive mail" mean?
- Your site publishes “the published address” as a way to reach you, and the domain it belongs to accepts no mail.
- How serious is it?
- ShipReady rates this high. Fix before launch. A real weakness that an attacker can act on.
- How common is this?
- Across the sites ShipReady has scanned where this check completed, 0% · n=31 · as of 15 September 2026.
- How do I fix it?
- Paste the fix prompt on this page into Cursor, Claude Code or your AI editor. It is the same prompt ShipReady puts in your report.
- Can I check my own site?
- Yes — ShipReady scans up to ten pages of any public site for free and reports this alongside every other check. The free report lists every issue it finds and shows full evidence and a fix prompt for the critical and high-severity ones; medium and low findings are counted and unlock on Pro.
Related checks
Run this check on your site
ShipReady checks this and 193 other things across up to ten pages of your site, with an AI-ready fix for each. Free, no signup.