Check Email Bounce — Pre-Send Bounce Testing

Test whether an email will bounce before you send it. Our bounce checker validates the recipient address, domain, mail server, and mailbox existence to predict delivery outcomes with 99% accuracy. Catch hard bounces, soft bounces, and risky addresses before they damage your sender reputation.

✓ Syntax ✓ MX Records ✓ SMTP ✓ Disposable

Domain exists:

MX records found:

SMTP check:

Disposable email:

Free email provider:

Overall status:

Check unlimited emails for bounce risk — completely free. For bulk pre-send testing, try our bulk email verifier or deliverability checker.

What Is an Email Bounce?

An email bounce occurs when a message cannot be delivered to the intended recipient and is returned to the sender. Understanding the different types of bounces and their causes is essential for maintaining healthy email operations and protecting your sender reputation.

When you send an email, it travels through multiple systems before reaching the recipient's inbox. At each step, something can go wrong that prevents delivery. The sending server hands the message to the recipient's mail server, which then attempts to deliver it to the specific mailbox. If delivery fails at any point, the recipient's server generates a bounce notification — a non-delivery report (NDR) — that is sent back to the original sender explaining why the message could not be delivered.

Bounces fall into two major categories: hard bounces and soft bounces. Hard bounces are permanent delivery failures that indicate the email address is fundamentally undeliverable. The most common causes of hard bounces include non-existent mailboxes (the user has left the company or deleted their account), invalid domains (the domain does not exist or has expired), and addresses that have been explicitly blocked by the receiving server. Hard bounces should never be retried because the underlying issue will not resolve on its own.

Soft bounces are temporary delivery failures that may resolve if the message is retried. Common soft bounce causes include full mailboxes (the recipient has exceeded their storage quota), temporarily unavailable mail servers (the server is down for maintenance), messages that are too large for the recipient's server to accept, and greylisting (where the server intentionally rejects first delivery attempts from unknown senders and expects a retry). Most email systems automatically retry soft bounces for a period of 24 to 72 hours before converting them to permanent failures.

There is a third, less obvious category: deferred bounces. These occur when the receiving server accepts the message but cannot complete final delivery — for example, when an internal routing rule redirects the message to a disabled account, or when a spam filter quarantines the message after initial acceptance. Deferred bounces may not generate an immediate NDR, making them harder to track and diagnose. Our bounce checker identifies conditions that commonly lead to deferred bounces, such as catch-all domain configurations and known spam-filtering patterns.

The impact of bounces extends far beyond the individual undelivered message. ISPs like Gmail, Outlook, and Yahoo track your bounce rate as a primary signal of sender quality. A bounce rate above 2% triggers reduced deliverability for all your emails, not just those to bouncing addresses. Above 5%, you risk having your sending IP or domain blacklisted, which can take weeks to resolve. Checking emails for bounce risk before sending is the single most effective way to prevent these cascading consequences.

How Pre-Send Bounce Testing Works

Our checker predicts whether an email will bounce by performing the same checks that a mail server does when receiving a message — without actually sending any email. Here is the step-by-step process.

Address Format Validation

Malformed email addresses cause immediate hard bounces at the sending server level, before the message even leaves your system. Our checker validates the address against RFC 5322 standards, catching missing @ symbols, invalid characters, double dots, excessively long local parts, and malformed domain names. Approximately 10-15% of addresses in uncleaned lists contain format errors that guarantee a bounce. Catching these before they enter your send queue prevents unnecessary delivery attempts and keeps your sending infrastructure processing valid addresses efficiently.

Domain and DNS Verification

We query DNS to verify the domain exists and is actively registered. Emails sent to non-existent domains generate hard bounces from your own mail server since there is nowhere to deliver the message. We also check domain registration age and WHOIS data — newly registered domains and domains approaching expiration carry higher bounce risk. Our checker identifies common domain typos (gmial.com, yaho.com, outlok.com) and suggests the correct domain, preventing bounces caused by simple misspellings.

Mail Server Discovery and Testing

We look up MX records to find the mail servers responsible for the domain and test connectivity to the primary server. Domains without MX records, or with MX records pointing to unreachable servers, will cause hard bounces for every address at that domain. We also check for mail server configuration issues like invalid SSL certificates, SMTP banner mismatches, and connection timeout behaviors that indicate delivery problems. This step catches domain-level issues that affect all addresses at the domain simultaneously.

Mailbox Existence Check

The most predictive check connects to the mail server and queries whether the specific mailbox exists. We initiate an SMTP handshake and issue a RCPT TO command for the email address. The server's response tells us definitively whether the mailbox exists (250), does not exist (550), is full (452), or is temporarily unavailable (451). We interpret these responses in the context of the server's known behavior patterns, accounting for catch-all configurations, greylisting, and rate limiting. No actual email is sent during this process.

Bounce Risk Classification

All check results are combined into a final bounce risk assessment. Addresses receive one of four classifications: Safe (very low bounce risk, proceed with confidence), Risky (moderate bounce risk, consider excluding from high-stakes sends), Invalid (will definitely bounce, remove immediately), or Unknown (bounce risk cannot be determined, typically catch-all domains). Each classification includes specific reasons and recommended actions, giving you the information needed to make informed decisions about your send list.

Types of Email Bounces and Their Causes

Understanding the specific types of bounces helps you diagnose issues and take targeted corrective action. Our checker detects conditions that lead to each of these bounce types.

User Unknown (550)

The most common hard bounce occurs when the mailbox does not exist on the server. SMTP response code 550 (or 551, 553) indicates the recipient address is invalid. This happens when employees leave companies, users delete accounts, or someone provides a fake address. Our SMTP mailbox check detects user-unknown conditions before you send, preventing the most common type of hard bounce. These addresses should be permanently removed from your list.

Domain Not Found (DNS Failure)

When the domain in the email address does not exist in DNS, the email cannot be routed to any mail server. This generates a hard bounce at the sending server level. Causes include misspelled domains, expired domain registrations, and completely fabricated domain names. Our DNS resolution check catches these instantly. Common misspellings we detect include gmial.com, yaho.com, hotmal.com, and outlok.com.

Mailbox Full (452)

A soft bounce occurs when the recipient's mailbox has exceeded its storage quota. SMTP response code 452 indicates a temporary condition that may resolve when the user clears space. However, consistently full mailboxes often belong to abandoned accounts that will never be cleared. Our checker identifies mailbox-full conditions and flags them as risky because they frequently convert to permanent failures. If an address returns mailbox-full on multiple checks over time, consider removing it.

Server Unavailable (421)

SMTP response code 421 indicates the mail server is temporarily unavailable, often due to maintenance, overload, or network issues. This generates a soft bounce that is typically retried automatically. Our checker tests server connectivity and responsiveness to predict this type of bounce. While individual server outages are normal and temporary, persistent connectivity issues may indicate a failing mail server or abandoned domain infrastructure.

Blocked or Blacklisted

Some bounces occur because the receiving server has blocked your sending IP or domain. This can result from previous high bounce rates, spam complaints, or presence on blacklists like Spamhaus, Barracuda, or SpamCop. These bounces may appear as hard bounces (550) or temporary rejections (450) depending on the blocking policy. While our checker cannot predict sender-specific blocks, it identifies addresses at domains with aggressive blocking policies and flags them as higher risk.

Content-Based Rejection

Some bounces occur after the message is accepted but then rejected based on content scanning. Spam filters, malware scanners, and policy engines may reject messages containing suspicious URLs, certain keywords, or prohibited attachment types. While our bounce checker focuses on address-level deliverability, avoiding content-based rejection requires separate attention to email content quality, authentication, and overall deliverability testing.

Why Check Email Bounce Before Sending?

Pre-send bounce checking is the single most cost-effective investment in your email program. Here is what you gain by testing every address before it enters your send queue.

Protect Your Sender Reputation

Your sender reputation is the gatekeeper of email deliverability. ISPs calculate a sender score based on your bounce rate, spam complaints, engagement metrics, and blacklist status. Every hard bounce chips away at this score. When it drops below the threshold, your emails start landing in spam folders — including messages to subscribers who actively want to hear from you. Pre-send bounce checking keeps your bounce rate near zero, preserving the sender reputation you have built over months or years of careful email practices. Rebuilding a damaged reputation takes 4-8 weeks of reduced sending and careful list management.

Avoid ISP Rate Limiting and Blocks

When ISPs detect high bounce rates from your domain, they respond with progressively severe countermeasures. First, they throttle your sending speed, delaying delivery of all your emails. Then, they start routing your messages to spam folders. Finally, they may block your domain or IP entirely, stopping all email delivery until the issue is resolved. Pre-send bounce checking prevents these escalating consequences by ensuring your bounce rate stays well below the 2% threshold that triggers ISP intervention. Prevention is dramatically easier than remediation.

Save Money on Every Campaign

Email service providers charge for every message sent, regardless of whether it is delivered. Sending to addresses that will bounce wastes sending credits, bandwidth, and server resources. For a campaign to 100,000 addresses with a 10% bounce rate, you are paying for 10,000 emails that will never be seen. At typical ESP pricing of $0.001-$0.003 per email, that waste adds up to $10-$30 per campaign or $500-$1,500 annually for weekly sends. Pre-send testing eliminates this waste entirely and pays for itself with the first campaign.

Get Accurate Performance Data

Bounced emails pollute your campaign analytics. Open rates, click rates, and conversion metrics are all calculated as percentages of emails sent. When 10% of your sends bounce, every metric is diluted by addresses that never had a chance of engaging. By removing bounce-prone addresses before sending, your reported metrics accurately reflect actual recipient behavior. This accuracy enables better optimization decisions — you can confidently test subject lines, send times, and content knowing that metric changes reflect real engagement shifts, not data quality artifacts.

How to Reduce Your Email Bounce Rate

Bounce checking is the foundation, but a comprehensive bounce prevention strategy involves multiple practices across your entire email operation. Follow these proven approaches to achieve and maintain a bounce rate below 0.5%.

Verify at the point of entry. The most effective bounce prevention happens before addresses enter your database. Integrate real-time verification into every form that collects email addresses: registration forms, checkout flows, lead magnets, and contact forms. When a user enters an invalid or risky address, show an immediate error message prompting them to correct it. Our verification API responds in under 300 milliseconds, fast enough for inline form validation without noticeable delay. This single practice prevents the majority of bounce-causing addresses from ever entering your system.

Clean your existing list regularly. Even verified addresses degrade over time. People change jobs, abandon email accounts, and domains expire. Industry data suggests that 22-25% of email addresses become invalid within a year through natural decay. Run a bulk verification on your entire list quarterly to catch addresses that have gone bad since your last check. Our bulk verifier processes lists of any size and segments results into clean, risky, and invalid categories for easy action.

Implement double opt-in for marketing lists. Double opt-in requires new subscribers to click a confirmation link in a verification email before being added to your list. This confirms the email address is valid, active, and controlled by the person who submitted it. While double opt-in slightly reduces signup conversion rates, it dramatically improves list quality and engagement rates. The subscribers who complete the double opt-in process are more engaged, more likely to open your emails, and less likely to generate spam complaints.

Process bounces immediately. When bounces do occur, process them in real time. Hard bounces should be permanently removed from your list within one campaign cycle. Soft bounces should be tracked and retried up to three times before being suppressed. Many email service providers handle bounce processing automatically, but verify that your ESP's bounce handling is configured correctly and that suppressed addresses are not accidentally re-added through list imports or CRM syncs.

Segment and monitor by domain. Track bounce rates by recipient domain to identify domain-specific issues. A sudden spike in bounces from a single domain might indicate a server outage (temporary) or a domain change (permanent). Monitoring at the domain level helps you respond quickly to isolated issues before they affect your overall sender reputation. Our domain verification tool can check entire domains for mail server health and configuration issues.

Warm up new sending infrastructure. When switching email service providers, adding new sending IPs, or launching a new sending domain, start with small volumes to reputable addresses and gradually increase over 2-4 weeks. ISPs treat new senders with suspicion, and a high bounce rate during warmup can permanently damage the reputation of your new infrastructure. Pre-send bounce checking is especially critical during warmup, when every bounce has outsized impact on your nascent sender reputation.

Who Needs Pre-Send Bounce Checking?

Any organization that sends email benefits from bounce checking. Here are the specific scenarios where pre-send testing delivers the most value.

Email Marketers

Check your campaign list before every major send to prevent bounces from damaging deliverability. Marketing campaigns with high bounce rates see immediate reductions in inbox placement for subsequent sends. Pre-campaign bounce checking is the most impactful five minutes you can invest in any campaign, often improving overall deliverability by 10-20% compared to sending to an unchecked list.

Cold Outreach Teams

Sales teams sending cold emails are especially vulnerable to bounce damage because ISPs scrutinize unfamiliar sender-recipient relationships. A bounce rate above 3% on cold outreach can trigger blocks within days. Check every prospect email before adding it to your outreach sequence to protect your outbound domain and ensure your messages reach real prospects rather than generating reputation-damaging bounces.

Transactional Email Senders

E-commerce companies, SaaS platforms, and service providers sending transactional emails (receipts, notifications, password resets) need bounce checking at the account creation stage. A customer who cannot receive transactional emails will generate support tickets, abandon carts, and lose trust in your email verification platform. Real-time bounce checking during signup prevents these issues.

List Buyers and Data Teams

If you acquire email lists through partnerships, data providers, or mergers, check every address for bounce risk before importing into your systems. Purchased or inherited lists often contain 20-40% invalid addresses. Sending to these lists without verification can instantly damage a sender reputation that took months to build. Always verify before you import.

Re-Engagement Campaigns

Before reaching out to dormant subscribers or old contacts, check their addresses for current validity. Addresses that were valid a year ago may have been deactivated, deleted, or converted to spam traps. Bounce checking before re-engagement campaigns prevents you from sending to addresses that have degraded since the subscriber last engaged with your emails.

Event and Webinar Organizers

Verify registrant email addresses before sending confirmations, reminders, and follow-up materials. Event registration forms completed on mobile devices have higher typo rates, and undelivered confirmations lead to no-shows. Pre-send checking ensures every registrant receives their event details, improving attendance rates and post-event engagement.

Complete Guide to Email Bounce Types

Email bounces are categorized by their SMTP response codes and the permanence of the failure. Understanding each bounce category helps you diagnose problems and take the right corrective action for each type.

Hard bounces (5xx codes) represent permanent delivery failures where the email address is fundamentally undeliverable. SMTP code 550 ("User not found" or "Mailbox unavailable") is the most common hard bounce, indicating the recipient mailbox does not exist on the server. Code 551 ("User not local") means the address was once valid but the user has been relocated or removed. Code 552 ("Exceeded storage allocation") can appear as either hard or soft depending on the server configuration, but when returned as a permanent 5xx, it means the account has been permanently disabled due to storage violations. Code 553 ("Mailbox name not allowed") indicates the address format is rejected by the server's policy. Code 554 ("Transaction failed") is a catch-all permanent rejection, often used when the server blocks your IP or domain based on reputation. Hard bounces must be removed from your list immediately and permanently — retrying them damages your sender reputation with every attempt.

Soft bounces (4xx codes) indicate temporary failures that may resolve if the message is retried. Code 421 ("Service not available, try again later") means the mail server is temporarily offline for maintenance or overload. Code 450 ("Mailbox busy") indicates the recipient's mailbox is temporarily locked or in use by another process. Code 451 ("Requested action aborted: local error in processing") signals a temporary server-side problem. Code 452 ("Insufficient system storage" or "Mailbox full") means the recipient has exceeded their storage quota — this may resolve if they clear space, but persistently full mailboxes often indicate abandoned accounts. Most email systems retry soft bounces every 15 to 60 minutes for 24 to 72 hours before classifying them as permanent failures.

Transient bounces occur when the receiving server intentionally delays delivery as part of its anti-spam measures. Greylisting is the most common transient mechanism: the server rejects the first delivery attempt from an unknown sender with a 450 or 451 code, expecting legitimate senders to retry after a configured delay (typically 5 to 30 minutes) while spammers move on. SMTP rate limiting produces similar codes when you exceed the server's per-sender or per-IP message threshold. These bounces resolve automatically through retry logic, but they can inflate your bounce counts if your email system does not handle them correctly.

Policy bounces result from the receiving server's administrative rules rather than address validity. Code 550 with a policy-related message indicates the server rejects your mail based on content filtering rules, sender authentication failures (missing or failed SPF, DKIM, or DMARC), or organizational policies blocking external senders. Code 571 ("Message refused") is used by some servers to indicate explicit policy rejection. These bounces require changes to your sending configuration, authentication setup, or content rather than changes to your recipient list. Verify your authentication records with our SPF, DKIM, DMARC checker to resolve authentication-based policy bounces.

Technical bounces arise from infrastructure problems unrelated to the recipient address. DNS resolution failures produce bounces when the recipient domain's MX records cannot be resolved, either because the domain does not exist or DNS is temporarily unavailable. TLS handshake failures occur when the sending and receiving servers cannot negotiate a secure connection. Message size rejections happen when the email exceeds the recipient server's maximum message size (typically 10 to 50 MB including attachments). Connection timeouts result from network issues or overloaded servers that do not respond within the configured timeout period. These bounces require investigating the specific infrastructure component that failed.

How to Analyze Bounce Reports

Bounce reports contain valuable diagnostic information. Learning to read and categorize them correctly enables you to take targeted action that improves deliverability without unnecessarily removing valid addresses.

Reading bounce logs. Every bounce generates a non-delivery report (NDR) containing the SMTP response code, the diagnostic message from the receiving server, and the timestamp. The response code tells you the category (4xx for temporary, 5xx for permanent), while the diagnostic message provides the specific reason. For example, 550 5.1.1 The email account that you tried to reach does not exist is a clear hard bounce, while 452 4.2.2 The email account that you tried to reach is over quota is a soft bounce due to a full mailbox. Always read the full diagnostic string — many servers return a generic 550 code but include specific details in the text that reveal the true cause.

Categorizing bounces for action. Sort your bounces into four action categories. Immediate removal: all hard bounces with 550, 551, or 553 codes where the mailbox does not exist. Monitor and retry: soft bounces with 421, 450, or 451 codes that indicate temporary server issues — retry up to three times over 72 hours. Investigate and fix: policy bounces related to authentication failures, blacklisting, or content rejection — these require changes to your sending infrastructure, not your recipient list. Suppress after threshold: recurring soft bounces (same address returning 452 or similar codes across three or more campaigns) should be suppressed since they likely represent abandoned accounts.

Domain-level analysis. Group bounces by recipient domain to identify systemic issues. If all bounces come from a single domain, the problem is likely server-specific (outage, policy change, or blocking) rather than a list quality issue. A sudden spike in bounces from Gmail or Outlook often indicates a reputation problem with your sending IP or domain. Monitor domain-level bounce patterns over time — a gradual increase at a specific domain may signal that your addresses at that domain are aging out. Use our domain verification tool to check whether a domain's mail infrastructure is functioning correctly.

Action items per bounce type. For hard bounces: remove the address permanently and add it to a suppression list to prevent re-import through CRM syncs or list uploads. For soft bounces: allow automatic retries, but suppress addresses that soft-bounce three consecutive times. For policy bounces: check your email deliverability configuration, verify authentication records, and review content for spam triggers. For technical bounces: investigate the DNS, TLS, or network issue and resolve at the infrastructure level. For all bounces: log the bounce reason, date, and campaign for trend analysis that helps you anticipate and prevent future deliverability issues.

Email Bounce Check FAQ

Can you check if an email will bounce before sending?

Yes. Our pre-send bounce checker verifies the email address through syntax validation, DNS resolution, MX record lookup, and SMTP mailbox verification to predict with 99% accuracy whether an email will bounce. All checks are performed without sending any actual email, so there is no risk to your sender reputation from the checking process.

What is the difference between a hard bounce and a soft bounce?

A hard bounce is a permanent delivery failure where the email address is fundamentally invalid (mailbox does not exist, domain is invalid, or server permanently rejects). A soft bounce is a temporary failure (mailbox full, server temporarily unavailable, message too large). Hard bounces should be removed immediately; soft bounces can be retried 2-3 times before removal.

What bounce rate is considered safe?

Industry best practice is to keep your bounce rate below 2% for marketing emails and below 0.5% for transactional emails. Rates between 2-5% trigger ISP warnings and reduced deliverability. Rates above 5% can result in sending throttling, spam folder placement, or IP/domain blacklisting. Pre-send bounce checking helps maintain rates well below 1%.

How does a high bounce rate affect my email delivery?

High bounce rates damage your sender reputation with ISPs like Gmail, Outlook, and Yahoo. ISPs interpret bounces as a sign of poor list hygiene. Consequences escalate progressively: first, emails are throttled (delivered slowly); then routed to spam folders; and ultimately your IP or domain may be blacklisted, blocking all email delivery until resolved.

Does bounce checking work for all email providers?

Our bounce checker works for addresses at virtually all email providers including Gmail, Outlook, Yahoo, corporate mail servers, and custom domains. Some servers implement catch-all configurations or greylisting that can make individual mailbox verification inconclusive. These addresses are classified as Unknown or Risky with an explanation of the limitation.

How often should I check my email list for bounces?

Check your entire list quarterly at minimum, as approximately 22-25% of email addresses become invalid each year through natural decay. Also check before every major campaign, after importing new contacts, and when re-engaging dormant subscribers. Real-time checking at the point of signup prevents bounce-prone addresses from entering your list in the first place.

Can I check a whole list for bounce risk at once?

Yes. Our bulk email verifier accepts CSV, Excel, or TXT files with up to 1 million email addresses and checks each one for bounce risk. Results are segmented into Valid, Invalid, Risky, and Unknown categories with specific bounce risk reasons for each address. Processing speed is 100,000+ emails per hour.

What should I do with emails marked as Risky?

Risky emails have factors that increase bounce probability but are not definitively invalid. Options include: sending to them with a separate, lower-priority campaign; monitoring bounce rates closely for the first send; excluding them from high-stakes campaigns where deliverability is critical; or re-checking them periodically to see if their status changes to valid or invalid.

What SMTP bounce code 550 5.1.1 means?

SMTP code 550 5.1.1 means "User unknown" or "Mailbox not found." It is the most common hard bounce code indicating the specific email address does not exist on the receiving mail server. The mailbox may have been deleted, the user may have left the organization, or the address was never valid. Remove these addresses from your list immediately and permanently — retrying them will damage your sender reputation.

What is the difference between a bounce and a block?

A bounce occurs when the receiving server rejects a specific email due to address-level issues (invalid mailbox, full quota). A block occurs when the receiving server rejects all email from your IP or domain based on reputation, blacklisting, or policy. Bounces require removing the specific address; blocks require fixing your sender reputation, delisting from blacklists, or resolving authentication issues that affect all your outgoing email.

Can greylisting cause false bounces?

Yes. Greylisting temporarily rejects the first delivery attempt from unknown senders with a 450 or 451 code, expecting legitimate servers to retry. If your email system does not retry automatically, greylisting appears as a bounce. Most properly configured mail servers retry after 5-30 minutes, at which point the greylisting server accepts the message. Our bounce checker accounts for greylisting behavior when classifying addresses.

How do I read a bounce notification email?

Bounce notification emails (NDRs) contain three key pieces of information: the SMTP response code (e.g., 550, 452), the diagnostic message from the receiving server explaining the rejection reason, and the original message headers. Focus on the response code to determine the bounce category (5xx = permanent, 4xx = temporary) and read the diagnostic text for the specific cause. Common messages include "User unknown," "Mailbox full," "Message rejected," and "Connection refused."