Every domain carries a reputation — a score from 0 to 100 that summarises how the mail you send from it is being received. You will find it on the domain page in the dashboard and in the weekly usage email. A new domain starts at the top of the scale.
The score is recalculated automatically, several times an hour, for verified domains only. There is nothing to trigger by hand.
The score is built from your domain's own delivery history. These are the things that move it, in order of how much they matter:
Only mail that has reached a final state counts — delivered, or permanently failed. Messages still queued or waiting on a retry are not counted either way.
Separately from everything above, DMARC results put a hard ceiling on the score. Once we have collected enough DMARC reports for mail sent from your domain, a poor pass rate caps the score no matter how good your delivery numbers are — and the worse the pass rate, the lower the ceiling.
This is the one part of the score that applies even to low-volume domains that are otherwise not scored. If your reputation is stuck below what your delivery deserves, DMARC alignment is the first thing to check.
If you send very little, there is not enough evidence to judge you and the score stays at the top of the scale. The bar is lower for domains that mostly send transactional mail than for those sending bulk campaigns. The DMARC ceiling above can still apply.
The more you send, the shorter the period we score you over: a busy domain is judged on its recent activity, while a quiet one is judged on weeks of history. A low-volume sender therefore carries a bad patch for much longer than a high-volume one.
The score is slow by design. It is smoothed over the recent past, so a single bad hour will not move it, and it climbs back gradually rather than jumping.
In practice: after you fix the underlying problem, expect a delay of several hours before the score starts moving at all, then a steady climb. If you are a low-volume sender, the bad window itself keeps counting against you for far longer — weeks, not hours.
If the score drops below a healthy level, we email the domain's users. The warning line is stricter on free plans than on paid ones. Nothing else changes — your sending is unaffected.
If the score falls to a critical level, new mail is refused. This is the only point at which reputation stops anything, and the critical level is the same on every plan, including free — the warning above is a warning only, not a sending limit.
Over SMTP the refusal happens at authentication, with the message Bad domain reputation. Over the HTTP API the request is rejected with HTTP 400:
HTTP/1.1 400 Bad Request
Content-Type: application/json
{
"auth": {
"non_field_errors": ["Domain reputation is critical"]
}
}Opens count in your favour, so a domain with no recorded opens cannot reach the top of the scale even with flawless delivery, zero bounces and zero complaints — it settles well short of a perfect score.
Turning open tracking off — or sending to recipients whose mail clients block images — therefore holds your score down, uncomfortably close to the warning line on a free plan. Leaving open tracking enabled is the way to avoid this.
Ordered by how much each one actually moves the number:
Sending a healthy volume of good mail also shortens the measuring window, so recovery gets faster.