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 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.
-
valid Charged if SMTP requested
The address exists and the receiving server agrees to accept it. When SMTP verification is requested, this status is only returned if the server confirmed the mailbox.
Decision. Accept the address.
-
invalid Charged if SMTP requested
The address cannot receive mail: malformed syntax, a domain with no MX record, a mailbox refused by the server, or an address present in the block list of the organisation.
Decision. Reject the address, it will produce a hard bounce.
-
risky Charged if SMTP requested
The address is technically acceptable but carries a risk signal: disposable domain, malicious domain, typosquatted domain, no-reply address, or an overall score below the degradation threshold.
Decision. Accept under conditions, or discard according to the configured business policy.
-
unknown Never charged
The receiving server gives no definitive answer, for instance on a catch-all domain or during a greylisting delay. The reason is named in the response.
Decision. Decide according to context. No credit is 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.
| Marker | Value | What it means |
|---|---|---|
| Minimum score | 0 | No usable information on this address. |
| Maximum score | 100 | Maximum confidence in the result returned. |
| Degradation threshold | 70 | Below 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.
- Disposable domain. The address exists and works, but it is designed to disappear. The risk is commercial, not technical.
- Malicious domain. The domain appears on a threat list. The address can receive mail, it must not enter a base.
- Typosquatted domain. The domain was registered to look like a well known domain. It often accepts everything sent to it.
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 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.
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".
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.