no_reply
A no-reply address: mail to it is discarded by design
The username is a no-reply shape — noreply, no-reply, donotreply, do-not-reply, mailer-daemon, bounces and their spellings. Such an address sends and never reads; whatever you send there goes to nobody.
- appears in
- reason
- verdict
- risky
- risk weight
- +20
- credits
- 1 credit, like every deliverable or risky answer. Repeats of the same address are free for 7 days.
What it means
A no-reply address is the sender of automated mail, not a mailbox anybody opens: the provider either discards inbound mail to it or lets it pile up unread. It is recognised by pattern rather than by the role list alone, so a spelling the list lacks is still caught, and it forces role true with role_type no_reply.
The mailbox is still probed and often exists, which is exactly the trap: mailbox_exists true and nobody reading. The verdict is risky with reason no_reply, and the weight is added on top of the role weight — 30 for the role and 20 for the no-reply, 50 in all, the medium band.
What to do
Never send to it. On a signup form ask for another address; on a list, drop it, since no person signed up with it and no reply will ever come from it.
Example response
{
"email": "[email protected]",
"deliverable": "risky",
"reason": "no_reply",
"role": true,
"role_type": "no_reply",
"risk_score": 50
}Abbreviated: a real answer carries all 46 fields, listed in the verify-email reference.
Related
- likely_typo · the domain is a known misspelling of a real mail provider
- parked_domain · the domain is parked or for sale, and still accepts mail
- disposable · the domain belongs to a disposable, temporary email provider
- mx_blocklisted · the domain's mail is served from a network on the threat blocklists
- implicit_mx · the domain has no MX record and relies on the address-record fallback
- mailbox_full · the mailbox is over its storage quota
- role · a shared role inbox such as info@ or support@ rather than a person
- recycled_mailbox · the mailbox exists now, but once answered that it did not
- catch_all · the server accepts every address at the domain, so the mailbox cannot be confirmed
- unverified · the mailbox could not be confirmed
- role · signal · the username is a role account rather than a person (+30)
- no_reply · signal · the address is a no-reply sender (+20)
- All verdict reasons
- Verdicts and the risk score
- API reference
markdown version: /docs/reasons/no_reply.md