Unknown status and greylisting

The unknown status describes a server, not an address. It is returned when the recipient server did not allow a conclusion: a domain that accepts everything, a delay or an unreachable server. Rather than a guessed verdict, you get a clear answer, never billed, that does not lower the address score.

What the status means

The unknown status describes a server, not an address. It is returned when the recipient server did not allow a conclusion on the mailbox: a domain that accepts everything, a delay or an unreachable server. It is neither an acceptance nor a refusal.

The distinction matters more than it seems. An invalid result is a measurement: the server answered, and it refused. An unknown result is an absence of measurement: the question was asked, and the answer settled nothing. Confusing the two means treating an absence of evidence as evidence of absence.

Do not decide on this result alone. An unknown address is neither good nor bad: it is unmeasured, and the right course of action depends on what the rest of the record says about the domain and the contact.

The three causes

They do not call for the same course of action, and the engine tells them apart. Two come from a real answer from the server, which spoke without concluding. The third comes from a server that is unreachable or gives no usable answer. In all three cases, the cause is the server, never the address analysed.

The 3 causes of an unknown status and how each is handled.
CauseWhat happens next
The domain answers for every address.The unknown status is returned with the accept-all reason, with no credit charged.
The server delays and asks to come back later: this is greylisting.In batch processing, the address is probed again during a second pass, which most often obtains a firm answer.
The server stays unreachable or gives no usable answer.The result does not penalise the address score: the cause is the server, not the mailbox.

Greylisting, explained

Greylisting is a defence against unwanted mail. The first time an unknown sender shows up, the server answers with a temporary refusal and asks it to come back. A real sending server tries again and gets through; a bulk sending robot does not try again.

A verification probe meets this defence by design: it presents itself once, and it does not try again within the second. A server that delays therefore says nothing about the mailbox; it only says that it does not talk to strangers the first time.

That is why batch processing goes back a second time, later, over the addresses that remained unknown. The server that had asked to come back then accepts the dialogue, and the address receives a firm verdict.

See how batch processing goes back over unknown addresses

Every outcome of a probe

The table below lists what SMTP verification can produce, from the firmest verdict to the least conclusive. Three outcomes out of six return an unknown status, and none of the three is billed: the billing rule follows directly from this classification.

The 6 outcomes of an SMTP verification and their effect.
SituationStatusBilling
The server accepts the recipient and the domain does not accept everything.validOne credit charged.
The server permanently refuses the recipient.invalidOne credit charged.
The domain accepts every address: it is a catch-all domain.unknownNo credit charged.
The server answers with a delay, greylisting or equivalent.unknownNo credit charged.
The server stays unreachable or gives no usable answer.unknownNo credit charged.
The mailbox exists but it is full.riskyOne credit charged.

What it costs

An unknown status is never billed: you only pay for answers that tell you something. In batch processing, these addresses are credited back automatically when the file closes.

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

In batch processing, the rule applies automatically: the credits for addresses that remained unknown are returned to you when the file closes. The final balance only counts the addresses on which a conclusion was returned.

See the pricing and the credit rules

Why the score does not drop

An unknown status does not lower the address score. When the verification delivered no information about the mailbox, it stays neutral: it does not cap the score, because the address analysed has nothing to do with it.

So a perfectly good address whose server delays keeps a fair score: the score speaks about the address, never about the whims of the recipient server. The free checks, for their part, did answer: their result is what carries the score.

Frequently asked questions

Why is an email address unknown?
The unknown status describes a server, not an address. It is returned when the recipient server did not allow a conclusion on the mailbox: a domain that accepts everything, a delay or an unreachable server. It is neither an acceptance nor a refusal.
What is greylisting?
Greylisting is a defence against unwanted mail. The first time an unknown sender shows up, the server answers with a temporary refusal and asks it to come back. A real sending server tries again and gets through; a bulk sending robot does not try again.
Is the unknown status billed?
An unknown status is never billed: you only pay for answers that tell you something. In batch processing, these addresses are credited back automatically when the file closes.
Does an unknown status lower the address score?
An unknown status does not lower the address score. When the verification delivered no information about the mailbox, it stays neutral: it does not cap the score, because the address analysed has nothing to do with it.

Going further

The most frequent cause of an unknown status is a domain that accepts every address. YesWeCheck spots it and flags it in the response: the dedicated page explains how detection works and which course of action to take for your use case.

Content updated on 7 September 2026.