Table of Contents
Greylisting is an anti-spam technique where a receiving mail server temporarily rejects a first delivery attempt from an unknown sender and accepts it only when the sender retries later. It cuts spam because most spam tools never retry. For email verification, greylisting causes temporary unknown results, since the probe is deferred rather than answered. This guide explains what greylisting is, how it works, and how verifiers handle it.
Verify emails free — even past greylisting delays.
Verify an Email Free →Free plan included · No credit card · Smart retry on deferrals
What Is Greylisting?
Greylisting is an anti-spam technique in which a receiving mail server temporarily rejects mail from an unknown sender on the first attempt, asking it to try again later. Legitimate servers retry and get through; most spam tools never retry, so they are filtered out. The method works on sender behavior rather than on content or reputation lists.
- Temporary rejection: Greylisting returns a soft, temporary refusal on first contact instead of accepting or permanently rejecting the message. That deferral signals the sender to come back later, and it is the single behavior that defines the entire technique.
- Retry required: Acceptance depends on the sender attempting delivery a second time after a short delay. Standards-compliant mail servers queue and retry deferred mail automatically, so legitimate senders clear greylisting without any human action at all.
- Spam filter: Most bulk spam software fires once and abandons deferred mail, so a temporary rejection blocks much of it cheaply. Greylisting exploits that behavioral gap rather than inspecting message content or maintaining a sender blocklist.
- Behavior based: Greylisting judges senders on whether they retry, not on message content, keywords, or reputation scores. That behavioral test catches new spam campaigns that signature filters and reputation lists have never seen before.
- Self clearing: A greylisting deferral resolves itself the moment a legitimate sender retries, so no administrator has to whitelist anyone by hand. The filter stays low-maintenance while quietly removing senders that never come back.
Greylisting says try again later. Real senders retry and pass, while most spam never returns, so the delay quietly removes a large share of junk mail.
How Does Greylisting Work?
On a first contact from an unfamiliar sender, the server replies with a temporary 4xx deferral instead of accepting the message. It records the sender address, recipient address, and sending IP, then accepts the message when that same combination retries after a delay. Once trusted, future mail from the sender passes without delay.
- First attempt deferred: The receiving server answers the opening delivery attempt with a temporary 4xx response rather than a final acceptance or rejection. This deferral is the trigger that starts the greylisting clock and forces the sender to queue the message.
- Triplet recorded: The server stores the sender address, recipient address, and source IP as a triplet to recognize the retry. Matching that triplet on a later attempt is how the server distinguishes a returning legitimate sender from a fire-once spam tool.
- Retry accepted: When the same triplet returns after the minimum delay, the server accepts the message and whitelists the sender for a period. Subsequent mail then flows immediately, so greylisting delays only the very first message from a new sender.
- Sender whitelisted: After a successful retry, the server remembers the triplet for a configured window and skips greylisting for that sender. Repeat correspondents therefore experience no delay once the initial deferral has been cleared once.
- Window expires: If a whitelisted sender goes quiet past the retention window, the triplet ages out and the next message faces greylisting again. This expiry keeps the triplet table small without permanently trusting dormant senders.
How Greylisting Defers Then Accepts Mail
A 4xx deferral on first contact and acceptance on retry: that delay is the whole mechanism, and it relies entirely on the sender coming back.
Why Do Servers Use Greylisting?
Servers greylist because it is cheap and effective. Spam-sending software is built for volume and rarely retries deferred mail, so a temporary rejection blocks much of it without maintaining a blocklist or scanning content. Greylisting trades a short delay on first contact for a large cut in inbound spam, using almost no server resources.
- Cheap to run: Greylisting needs only a small table of triplets and a timer, with no content scanning or external reputation feeds. That minimal footprint lets even modest mail servers run it without measurable performance cost.
- Catches non-retrying spam: Bulk spam tools optimize for throughput and discard mail the moment it is deferred, so a single temporary rejection removes them. Greylisting turns that behavioral shortcut into a filter that needs no signature updates to stay effective.
A temporary 4xx defers the verification probe, so the result comes back unknown.
— Hunter, Email Verifier API documentation
Greylisting buys a large spam reduction for the price of a short first-contact delay, which is why so many cautious mail servers keep it switched on.
How Does Greylisting Affect Email Verification?
A verifier’s SMTP probe can be deferred by greylisting just like real mail, so the server returns a temporary 4xx instead of a clear yes or no. The verifier cannot confirm the mailbox on that attempt, which is why greylisted addresses often come back as unknown rather than valid or invalid.
- Probe deferred: The verifier opens an SMTP connection to test the mailbox, and the greylisting server answers with a temporary 4xx exactly as it would to any new sender. The existence question goes unanswered on that single attempt, leaving no definitive result to record.
- Unknown result: Because the server neither confirmed nor denied the mailbox, an honest verifier reports the address as unknown rather than inventing a verdict. That status reflects a deferred probe, not a defective address on the receiving domain.
Greylisting defers the verifier’s probe too, so the honest outcome on that attempt is an unknown rather than a guessed valid or invalid status.
How Do Verifiers Handle Greylisting?
Good verifiers detect a 4xx deferral and retry the probe after a delay, often resolving the address on a later attempt once the sender is trusted. When repeated retries still do not clear, the verifier returns unknown rather than guessing. Retry logic is what separates accurate verifiers on greylisted domains from basic ones.
- Detect and retry: A capable verifier recognizes a 4xx as a deferral rather than a failure and schedules a second probe after the typical greylisting delay. That retry frequently lands after the server has whitelisted the sender, turning an early unknown into a resolved status.
- Label honestly: When retries still meet a deferral, a quality verifier reports unknown instead of forcing a valid or invalid verdict. Honest labeling protects the address from being deleted in error and keeps the result set trustworthy for the sender.
Verifying before a send keeps deferred and unknown statuses from quietly inflating bounce rates.
— Growth Hack Suite, pre-send verification workflow
Quality verifiers retry deferred probes and label the result unknown honestly when greylisting still wins, instead of discarding a likely valid address.
Does Greylisting Mean an Address Is Invalid?
No. Greylisting is a server behavior, not a verdict on the address, and a greylisted mailbox is often perfectly valid. Treating an unknown caused by greylisting as invalid would wrongly discard reachable contacts. Unknown means undetermined on this attempt, not bad, and the distinction protects a real address from deletion.
- Server behavior: Greylisting is a policy the receiving server applies to all new senders, so the deferral describes the server’s caution rather than the recipient. The address itself plays no part in whether the first probe is deferred.
- Often valid: Many greylisted mailboxes belong to active, deliverable accounts on well-run business domains. Discarding them on an unknown status throws away reachable contacts and shrinks a list for no real deliverability reason.
- Unknown not invalid: An unknown status records that the probe was deferred, not that the mailbox failed a check. Conflating the two statuses corrupts list hygiene by deleting addresses that a simple retry would have confirmed as valid.
- Resolvable on retry: A greylisting unknown typically clears once the verifier retries and the sending IP has passed the delay window. The temporary nature of the deferral is precisely why the result should never be hardened into an invalid verdict.
- No bounce signal: A greylisting deferral carries no indication that a real send would bounce, since legitimate retries deliver normally. Reading it as a bounce risk overstates the danger and prunes contacts that remain perfectly reachable.
Greylisting is about the server, not the address, so an unknown here is no reason to delete a contact that may well be valid.
Greylisting vs Blocklisting: What’s the Difference?
Greylisting temporarily defers unknown senders and accepts them on retry; blocklisting permanently refuses senders with a bad reputation. Greylisting is a soft, automatic filter that clears itself; blocklisting is a hard reputation penalty that stays until removed. The table below contrasts the two on the points that matter for verification.
Source: greylisting behavior per Wikipedia, Greylisting (email) and SMTP 4xx deferral per IETF RFC 5321, verified 2026-06-29.
Greylisting is a temporary speed bump that clears on retry; blocklisting is a permanent wall tied to reputation, so the two send very different verification signals.
How Should You Handle Greylisted Results?
Re-verify greylisted unknowns after a delay rather than discarding them, since a retry often resolves the status. For sending, long-standing contacts that greylist can be included cautiously, because legitimate retries deliver. The one rule to hold firmly is that a greylisting unknown should never be treated as an invalid address.
- Re-verify after delay: Queue greylisted unknowns for a second verification pass after a short wait, allowing the sending IP to clear the greylisting window. A later attempt frequently returns a definitive valid status that the first probe could not capture.
- Do not discard: Removing greylisted unknowns from a list deletes contacts that are usually deliverable, since the deferral reflects server caution rather than a dead mailbox. Keeping them, then re-verifying, preserves reach without raising bounce risk.
Verify emails free with smart greylisting retries.
Verify an Email Free →Free plan · No credit card · Deferrals retried automatically
Re-verify greylisted unknowns later rather than deleting them, because a retry usually resolves the status and recovers a contact that was never truly unreachable.
What Tools Handle Greylisting Well?
Verifiers that implement retry logic resolve more greylisted addresses, while basic tools simply return unknown and stop. Hunter retries deferred probes and labels results honestly on a recurring free tier. The table below compares the common tool categories on how each deals with a greylisting deferral during verification.
Source: hunter.io/pricing and hunter.io/api-documentation/v2, verified 2026-06-29 (free plan 50 credits/mo = ~100 verifications). Other rows describe common tool categories; confirm each provider’s behavior before buying.
Retry logic is the real differentiator on greylisting, because it turns a first-attempt unknown into a resolved status that basic single-pass tools simply cannot reach.
How Common Is Greylisting on Real Domains?
Greylisting is widespread on business and security-conscious mail servers, though large consumer providers rarely use it. That means greylisting unknowns tend to cluster on certain B2B domains, which is exactly where retry logic pays off most in a verifier. The pattern shapes where unknown results appear in a typical list.
- Common on B2B and security servers: Self-hosted and security-minded mail systems often enable greylisting as a low-cost spam defense, so corporate and niche domains defer first-contact probes regularly. Verification of B2B lists therefore meets greylisting far more often than consumer lists do.
- Rare on big consumer mail: Large providers such as the major webmail platforms generally rely on reputation and content filtering instead of greylisting, so their mailboxes answer probes immediately. Consumer-heavy lists see fewer greylisting unknowns as a result.
- Tied to mail-server software: Greylisting prevalence tracks the mail-server stack a domain runs, since some open-source agents ship it as a simple add-on. Domains on those stacks defer first probes far more often than managed cloud inboxes do.
- Concentrated unknowns: Because greylisting clusters on specific domain types, the unknown statuses it produces concentrate in those segments rather than spreading evenly. A B2B list can show a noticeable band of greylisting unknowns around a handful of recurring domains.
- Predictable by domain: Once a domain is known to greylist, every fresh sender to it can expect a first-contact deferral until retried. That predictability lets a verifier schedule retries efficiently for the domains most likely to defer.
Greylisting clusters on B2B and security-minded servers, the very domains where a verifier’s retry logic returns the most recovered statuses.
Verdict: Greylisting and Verification
Greylisting is a normal anti-spam delay, not a sign of a bad address. It can make verifiers return unknown, but tools with retry logic resolve most cases, and the rest should be re-verified rather than discarded. Treat greylisting unknowns as undetermined, never invalid, and a clean list keeps its reachable contacts intact.
Verdict: Greylisting is a temporary 4xx deferral, not a verdict on the address. It causes unknown results when a probe is deferred, but a retry resolves most cases. A greylisting unknown means undetermined, never invalid, so re-verify rather than delete.
Greylisting temporarily rejects email from senders the server does not recognize.
— Wikipedia, Greylisting (email)
Verify emails free past greylisting delays.
Verify an Email Free →Free plan · No credit card · Deferrals retried, not guessed
Related Tools in the Hunter Stack
Greylisting is one cause of unknown results, not the whole picture. The Hunter Email Verifier review covers how every status is determined and which checks run, while the finder review covers building the lists worth verifying in the same connected stack on one credit pool. Catch-all domains, the other main source of unknowns, are covered separately.
- Hunter Email Verifier: The validation layer that decides each status, including how it treats deferred greylisting probes — start with what the Hunter Email Verifier is.
- Hunter Email Finder: The list-building half of the bundle that shares the same credit pool — read the Hunter.io email finder review for sourcing costs.
Greylisting: Frequently Asked Questions
The 12 most-asked questions about greylisting.
What is greylisting?
Greylisting is an anti-spam technique where a receiving mail server temporarily rejects mail from an unknown sender on the first attempt and accepts it only when the sender retries later. Legitimate servers retry automatically and get through, while most spam tools never return, so they are filtered out without any content scanning.
How does greylisting work?
On first contact from an unfamiliar sender, the server replies with a temporary 4xx deferral instead of accepting. It records the sender address, recipient address, and source IP as a triplet, then accepts the message when that same triplet retries after a delay. Once trusted, future mail from the sender flows without delay.
Why do servers use greylisting?
Servers greylist because it is cheap and effective. Spam-sending software is built for volume and rarely retries deferred mail, so a temporary rejection blocks much of it without a blocklist or content scanning. Greylisting trades a short delay on first contact for a large cut in inbound spam, using almost no server resources.
How does greylisting affect verification?
A verifier’s SMTP probe can be deferred by greylisting just like real mail, so the server returns a temporary 4xx instead of a clear yes or no. The verifier cannot confirm the mailbox on that attempt, which is why greylisted addresses often come back as unknown rather than valid or invalid.
How do verifiers handle greylisting?
Good verifiers detect a 4xx deferral and retry the probe after a delay, often resolving the address once the sender is trusted. When repeated retries still do not clear, the verifier returns unknown rather than guessing. Retry logic is what separates accurate verifiers on greylisted domains from basic single-attempt tools.
Does greylisting mean an address is invalid?
No. Greylisting is a server behavior, not a verdict on the address, and a greylisted mailbox is often perfectly valid. Treating an unknown caused by greylisting as invalid would wrongly discard reachable contacts. Unknown means undetermined on that attempt, not bad, so the address deserves a retry before any deletion.
Greylisting vs blocklisting?
Greylisting temporarily defers unknown senders and accepts them on retry, while blocklisting permanently refuses senders with a bad reputation. Greylisting is a soft, automatic filter that clears itself once the sender returns; blocklisting is a hard reputation penalty that stays until removed. The two send very different verification signals.
How should I handle greylisted results?
Re-verify greylisted unknowns after a delay rather than discarding them, since a retry often resolves the status. For sending, long-standing contacts that greylist can be included cautiously, because legitimate retries deliver. The firm rule is to never treat a greylisting unknown as an invalid address and delete it.
What tools handle greylisting well?
Verifiers with retry logic resolve more greylisted addresses, while basic tools just return unknown and stop. Hunter retries deferred probes and labels results honestly on a recurring free tier of about 100 verifications a month. Pure-play verifiers usually retry too, but often only on one-time trial credits.
Does greylisting cause unknown status?
Yes. When a verifier’s probe meets a temporary 4xx deferral, the server gives no clear yes or no, so an honest verifier records the result as unknown. The status reflects a deferred probe rather than a defective mailbox, and a later retry often turns that unknown into a definitive valid result.
Should I delete greylisted addresses?
No. Greylisted unknowns are usually deliverable, because the deferral describes server caution rather than a dead mailbox. Deleting them removes reachable contacts for no real deliverability reason. The correct response is to keep the address, re-verify it after a delay, and let retry logic resolve the true status.
How long does greylisting last?
Greylisting delays only the first message from a new sender, typically until a retry arrives after the server’s minimum wait. Once the sender retries and is accepted, the server whitelists that triplet for a period, so later mail passes immediately. The delay is one-time per new sender, not a recurring block on every message.
