Statuses and risk score

Every address analysed receives one status among four and a score from zero to one hundred. The status says which course of action to take, the score says with what confidence. Both are independent of the check that produced them: a client can decide on the status alone, or trace it back to the exact signal behind it.

The qualification threshold of the score A score scale from 0 to 100, cut by the degradation threshold at 70. An address whose score rises above the threshold stays valid. A technically valid address whose score falls below the threshold is returned as risky. 0 threshold 70 valid above risky below the threshold 100
Above the threshold, the technical status is returned as it is. Below it, a valid result is returned as risky.

The four statuses

An address is valid when the server agrees to receive it, invalid when it cannot receive a message, risky when it is acceptable but carries a risk signal, and unknown when the server did not make a verdict possible. Only the unknown status is never charged.

The score and its threshold

The score runs from zero to one hundred, where one hundred reflects maximum confidence in the result returned. It aggregates the individual scores of the checks run, capped according to the signals found. Below the degradation threshold, a technically valid result becomes risky: it is the only requalification the score triggers.

The bounds of the score and the degradation threshold.
MarkerValueWhat it means
Minimum score0No usable information on this address.
Maximum score100Maximum confidence in the result returned.
Degradation threshold70Below this score, a technically valid result is returned as risky.

The score measures confidence in the verdict, aggregated from the checks actually run on this address: a simple marker for setting your own acceptance threshold.

What degrades a valid result

Three signals turn a valid result into a risky result, even when the server has confirmed the mailbox. A disposable domain, a malicious domain and a typosquatted domain are perfectly deliverable: they answer favourably, and that is precisely what makes them dangerous for a contact base.

A risk signal degrades

valid the server confirms the mailbox + disposable domain risky result returned

A low score degrades too

valid technical checks in the green + score below 70 risky result returned

Nothing raises a verdict

invalid the server refuses the recipient + high score valid never
Requalification only goes one way: from a valid result to a risky result. An invalid or unknown result is never raised to valid.

Degradation only works in that direction. An invalid or unknown result is never raised to valid, whatever the score: the signal stays readable in the detail of the checks, but the verdict does not improve.

Understand SMTP verification

The status decides the billing

The link between status and billing fits in one sentence. A credit is charged if and only if SMTP verification was requested and the final status is not unknown. You therefore only pay for the answers that genuinely inform you.

A credit is charged if and only if SMTP verification was requested and the final status is not "unknown".

See pricing and credit rules

Frequently asked questions

What does the unknown status mean?
The receiving server did not make a verdict possible: catch-all domain, greylisting delay or unreachable server. This status describes a server, not an address. Rather than guess, YesWeCheck says so clearly, and no credit is charged.
What is the difference between invalid and risky?
An invalid address cannot receive a message: it will produce a hard bounce. A risky address is technically acceptable but carries a risk signal, such as a disposable domain or a typosquatted domain. The first is rejected, the second is decided according to business policy.
What is the score for when the status is enough?
The status says what to do, the score says with what confidence. Two valid addresses can have very different scores, depending on the health of the domain and the number of minor signals found. The score lets you set an acceptance threshold stricter than the status alone.
Can a low score change the status?
Yes, in one direction only. A technically valid result whose score falls below the degradation threshold is returned as risky rather than valid. The reverse does not exist: a high score never turns a refusal by the server into an acceptance.

Going further

The same statuses and the same score are returned in real time and in batch processing: there is a single engine, and an address processed in a file receives exactly the verdict it would have received on its own. The documentation publishes the full response schemas, check by check.