delivered_recently
Your own delivery report confirmed this mailbox
Not a probe result: your account reported the address as delivered within the last 90 days, and a real delivery is better evidence than any handshake.
- appears in
- smtp_reason
- credits
- 1 credit as a deliverable answer; the handshake itself is skipped.
What it means
When you send delivery outcomes through the feedback endpoint or an ESP webhook, a delivered report for an address turns later lookups of it into confirmed mailboxes. The probe is skipped, mailbox_exists is true, smtp_checked_at is the delivery time, and the sources list delivery-feedback instead of the SMTP handshake.
Only your own account's reports count. Other customers' outcomes are never used for your verdicts.
What to do
Nothing. Keep reporting outcomes and the share of lookups that needs a paid probe keeps falling.
Example response
{
"deliverable": "deliverable",
"mailbox_exists": true,
"smtp_checked": true,
"smtp_reason": "delivered_recently"
}Abbreviated: a real answer carries all 27 fields, listed in the verify-email reference.
Related
- mailbox_full · the mailbox is over its storage quota
- no_mailbox · the server answered that the mailbox does not exist
- disabled · the server reported the mailbox as disabled or suspended
- greylisted · the server deferred the handshake and asked the sender to come back later
- timeout · the mail server did not answer within the probe's time limit
- no_connect · no mail server accepted a connection on port 25
- mx_unreachable · the mail exchangers could not be reached from the verification network
- provider_unavailable · the verification provider itself could not answer
- All verdict reasons
- Verdicts and the risk score
- API reference
markdown version: /docs/reasons/delivered_recently.md