Bounces come back
Bounces and complaints are recorded within seconds. A dead address leaves the list before the next campaign.
← All features
Enter your domain, we tell you what's missing
Writing a good letter is worthless if it lands in spam. It's the invisible half of the job.
Recognition
14documented DNS providers
Verification
3checks, including DMARC
Test your domain Free, no sign-up
What's at stake before sending
Inboxes decide in a fraction of a second
Inboxes decide in a fraction of a second whether your letter gets in. They look at who you are — is your domain authenticated? — and how you have behaved so far. Both things must be prepared; neither can be fixed after the fact.
One-click unsubscribe
The headers required by Gmail and Yahoo since 2024 are placed on every send. Without them, deliverability degrades no matter what.
Postal address in the footer
Required by anti-spam laws, and a pre-send check warns you if it is missing.
The circuit breaker
A campaign that starts badly stops itself
While sending, Mailcheer re-reads what's happening to messages already sent. If bounces spike, what remains in the queue is abandoned rather than sent, and the campaign goes back to draft: you fix the list, and your sender reputation is intact.
What you need to add
Six records, three roles
Six records to add with whoever manages your DNS, for three distinct roles. None replaces the other two.
Who is allowed to send
The record that declares the servers authorized to send on your behalf. A domain can only carry one: two SPF records equal zero SPF.
The message signature
Three records that let the inbox verify that the message really comes from you and hasn't been modified in transit.
What to do with impostors
The instruction you give inboxes for messages that claim to be from you without authorization. The only one of the three that Amazon doesn't follow: Mailcheer queries your domain directly.
Under the hood
What happens when you click 'Send'
Four checks before a single message leaves, three during sending.
- Reputation, firstThe sending infrastructure is shared: a campaign from a workspace that damaged its reputation would put everyone else at risk.
- Sender and subjectWithout a chosen sender, without a subject or without content, the campaign doesn't go out.
- The suppression listRe-read at the last moment, not at preparation time. An address removed this morning doesn't receive the noon send.
- The monthly quotaChecked before filling the queue: better to refuse now than stop in the middle of a list.
- Departure, message by messageEach one carries the identifier that will link its returns to the right person and the right campaign.
- A failure goes back in the queueA network cut or a rate limit doesn't lose the message: it goes out in the next batch.
- The circuit breaker watchesReturns already received are re-read throughout the send.
The safeguard
A two-tier suppression list
Someone who unsubscribes from one of your brands hasn't asked to disappear from the others: their exit stays in the workspace where it happened. Above it, a platform-level list applies everywhere at once.
You add an address manually, with its reason — and export the whole list whenever you want.
At your provider, specifically
The exact path, provider by provider
You buy a domain with one provider and its DNS is managed by another: that's the leading cause of authentication failures. Choose yours.
Cloudflare
- Open your domain in the Cloudflare dashboard
- "DNS" tab → "Records"
- "Add record" for each line below
Heads upThe three CNAMEs must remain set to "DNS only" (gray cloud). If the cloud is orange, Cloudflare hides the value and verification will fail.
Open Cloudflare DNS settings →In the product
A sending domain, its status, its senders
The status of each domain is readable at a glance, without going elsewhere.
Open the product without an account →
A verified sending domain, in the sending domains list.
Authenticate your domain
3,000 sends a month free, no credit card. Enough to add the six records and verify everything is green.