Free Verifier Bulk Verifier API Pricing
Tools
SPF/DKIM/DMARC Checker Fake Email Checker Domain Checker Disposable Checker Deliverability Checker
Sign Up Free

Email Bounce Checker — Test Before Sending

Check if an email will bounce before you hit send. Our email bounce checker performs deep SMTP verification, DNS analysis, and mailbox validation to predict delivery outcomes with 99% accuracy. Protect your sender reputation by catching hard bounces, soft bounces, and risky addresses before they damage your deliverability.

✓ Syntax ✓ MX Records ✓ SMTP ✓ Disposable
Domain status:
Mail server:
Mailbox check:
Bounce risk:
Delivery prediction:
Bulk Bounce Check Deliverability Checker

How Our Bounce Checker Tool Works

Our bounce checker performs a multi-layered verification pipeline in real time, simulating the exact journey an email takes from your outbox to the recipient’s mailbox — without ever sending a message. Here is what happens when you enter an address and click “Check Bounce Risk.”

Syntax and format validation. The tool instantly parses the address against RFC 5322 formatting rules. It catches missing @ symbols, illegal characters, consecutive dots, excessively long local parts, and trailing spaces that would cause an immediate rejection at the sending server. This check takes less than one millisecond and eliminates roughly 10–15% of problematic addresses in uncleaned lists before any network calls are made.

Domain and DNS resolution. Next, the tool queries the DNS system to confirm the domain portion of the address is actively registered and resolving. It checks A records, AAAA records, and SOA records to verify the domain is live. If the domain does not exist, has expired, or returns NXDOMAIN, the tool immediately flags the address as a guaranteed hard bounce. It also detects common domain typos — gmial.com, yaho.com, hotmal.com, outlok.com — and surfaces them so you can correct the address rather than discard it.

MX record lookup and mail server discovery. The tool retrieves all MX (Mail Exchanger) records for the domain and ranks them by priority. It tests connectivity to the primary MX server and, if that server is unreachable, falls back to secondary and tertiary servers. Domains without any MX records, or with MX records pointing to unreachable hosts, are flagged as undeliverable. The tool also checks for misconfigured MX records such as loopback addresses (127.0.0.1) or null MX entries (RFC 7505) that explicitly declare the domain does not accept email.

SMTP handshake and mailbox probe. This is the most predictive step. The tool opens a direct SMTP connection to the mail server and initiates a standard mail transaction: it sends EHLO, MAIL FROM, and RCPT TO commands using the target address. The server’s response to the RCPT TO command reveals whether the specific mailbox exists. A 250 response confirms acceptance; a 550 response indicates the mailbox does not exist. The tool interprets these responses in context, accounting for catch-all servers that accept all addresses regardless of mailbox existence, greylisting systems that temporarily reject first attempts, and rate-limiting policies that defer responses under high query volumes. No email content is transmitted during this process.

Reputation and risk analysis. Finally, the tool aggregates data from all preceding checks and cross-references it against proprietary databases of known disposable email providers, spam trap patterns, role-based address conventions (info@, admin@, sales@), and historical bounce data from millions of previous verifications. The combined signals produce a single bounce risk score and delivery prediction that reflects the real-world likelihood of a successful delivery.

Real-time results. The entire pipeline completes in 3–8 seconds depending on the responsiveness of the target mail server. Results appear instantly in the output panel above the form, with each verification step showing its individual pass/fail status alongside the overall delivery prediction. No account registration is required, and you can check unlimited addresses for free.

Bounce Risk Scoring — Understanding Your Results

After each check, the tool assigns a bounce risk level based on the combined results of all verification steps. Here is what each status means and what action you should take.

Risk Level Delivery Prediction What It Means Recommended Action
Low Risk Deliverable Valid syntax, active domain, healthy MX records, mailbox confirmed via SMTP. All checks passed with positive signals. Safe to send. This address has a very high probability of successful delivery. Include it in your campaign with confidence.
Medium Risk Risky Address passed basic checks but raised one or more warning flags: catch-all domain detected, role-based address (info@, support@), recently registered domain, or SMTP response was ambiguous (greylisting or rate-limiting encountered). Send with caution. Consider excluding from high-stakes campaigns such as cold outreach or re-engagement sends. Safe for routine newsletters if your overall list health is strong. Recheck before your next campaign.
High Risk Undeliverable One or more critical failures detected: mailbox does not exist (550 response), domain has no MX records, domain does not resolve in DNS, or address matches known disposable email provider patterns. Do not send. Remove this address from your list immediately. Sending to high-risk addresses will generate hard bounces that directly damage your sender reputation. If the address belongs to an important contact, reach out through an alternative channel to obtain a valid address.
Unknown Accept-All / Inconclusive The mail server accepts all addresses regardless of whether the mailbox actually exists (catch-all configuration), or the server blocked our verification query due to rate limiting or firewall rules. Bounce risk cannot be definitively determined. Treat as moderate risk. Send if the address was collected through a confirmed opt-in process. Avoid including in cold outreach. Monitor bounce reports after sending and suppress if a bounce occurs. Consider verifying through an alternative method such as a confirmation email.

Individual check statuses. Beyond the overall risk level, each row in the results panel provides its own status. A green checkmark indicates the check passed cleanly. A yellow warning icon means the check returned an ambiguous or cautionary result. A red X means the check failed outright. Reading the individual statuses helps you understand exactly why an address received its risk classification and whether the issue is correctable (such as a typo) or permanent (such as a deleted mailbox).

Bounce risk vs. deliverability. It is important to understand that bounce risk scoring predicts whether the receiving server will accept your message, not whether the message will reach the inbox. An address that scores “Low Risk” will almost certainly not bounce, but inbox placement also depends on your sender reputation, email authentication (SPF, DKIM, DMARC), and content quality. For a complete deliverability assessment, combine bounce checking with our email deliverability checker and SPF/DKIM/DMARC checker.

Single vs Bulk Bounce Checking

Our platform supports both individual address checks and large-scale list verification. Choosing the right mode depends on your workflow and volume.

Single Email Bounce Check

Best for: Spot-checking individual addresses before adding them to your CRM, verifying a VIP contact before a critical send, testing addresses that previously bounced to see if they have recovered, or validating an address provided over the phone or in person.

How it works: Enter one email address in the tool above, click “Check Bounce Risk,” and receive results in 3–8 seconds. Each check runs the full verification pipeline including SMTP mailbox probing. No account or login required.

Throughput: One address at a time, unlimited checks per day. Ideal when you need an immediate answer for a specific address and do not want to upload a file or wait for batch processing.

Typical use cases: Sales representatives verifying a prospect’s email before adding to an outreach sequence. Customer support agents confirming a customer’s email during a support call. Marketing managers spot-checking addresses flagged by campaign analytics. Developers testing webhook and API integrations against known-good and known-bad addresses.

Bulk Bounce Check

Best for: Pre-campaign list cleaning, quarterly list hygiene, verifying purchased or imported lists, and cleaning dormant subscriber segments before re-engagement campaigns.

How it works: Upload a CSV or TXT file containing your email list to our bulk email verifier. The system processes addresses in parallel, running the same multi-step verification pipeline used for single checks but optimized for high throughput. Results are delivered as a downloadable file segmented into deliverable, risky, and undeliverable categories.

Throughput: Processes thousands of addresses per minute with intelligent rate management that respects mail server limits to ensure accurate results. Lists of any size are supported, from a few hundred addresses to millions.

Typical use cases: Marketing teams cleaning a 50,000-address newsletter list before a product launch. Sales operations verifying a purchased prospect database before importing to Salesforce. E-commerce businesses validating their customer email database quarterly to maintain transactional delivery rates. Agencies processing client lists before onboarding a new email account.

When to use both. The most effective workflow combines both modes. Use bulk verification for regular list cleaning on a monthly or quarterly schedule, and use single checks as a daily operational tool at every point where new addresses enter your system. Sales teams that verify each prospect individually before adding them to sequences and then run a bulk clean of their full CRM quarterly maintain bounce rates consistently below 0.3% — well below the 2% threshold that triggers ISP intervention.

SMTP Response Codes Explained

When our tool probes a mail server, the server responds with standardized SMTP status codes that reveal exactly what will happen if you send a real email. Understanding these codes helps you interpret your bounce check results and diagnose delivery issues.

SMTP Code Category Meaning Bounce Implication
250 Success The mail server confirms it will accept mail for this address. The RCPT TO command was acknowledged positively, indicating the mailbox exists and is ready to receive messages. No bounce expected. This is the ideal response and maps to a “Low Risk” classification in our tool. The address is confirmed deliverable at the server level.
421 Temporary Failure The mail server is temporarily unavailable. Common during server maintenance, reboot cycles, or when the server is overloaded with incoming connections. The server is asking you to try again later. Soft bounce if you send now. The address is likely valid, but delivery will be delayed. Our tool flags this as “Medium Risk” and recommends rechecking after 30–60 minutes. Persistent 421 responses across multiple checks may indicate a failing or decommissioned mail server.
450 Temporary Failure Requested action not taken — mailbox temporarily unavailable. Often used for greylisting, where the server deliberately rejects the first delivery attempt from an unknown sender and expects a retry within 5–30 minutes. Soft bounce on first attempt, but typically resolves on automatic retry. Our tool distinguishes greylisting from genuine mailbox issues by analyzing server behavior patterns. Greylisting is common on corporate mail servers and is not a cause for concern — your ESP will handle the retry automatically.
550 Permanent Failure The mailbox does not exist, the address is invalid, or the server is permanently refusing delivery. This is the most common hard bounce code. Sub-codes like 550 5.1.1 (bad destination mailbox) and 550 5.1.0 (address rejected) provide additional specificity. Guaranteed hard bounce. Remove this address from your list immediately. Our tool maps any 550 response to “High Risk — Undeliverable.” Continuing to send to 550-coded addresses is the fastest way to damage your sender reputation.
552 Permanent Failure The recipient’s mailbox has exceeded its storage quota, or the message exceeds the server’s maximum message size. Although technically a size-related issue, quota-exceeded responses often indicate abandoned or neglected mailboxes. Hard or soft bounce depending on context. If the issue is message size, reducing your email size resolves it. If the issue is mailbox quota, the address is likely abandoned. Our tool flags quota-exceeded addresses as “High Risk” because they bounce consistently and rarely recover.
554 Permanent Failure Transaction failed — a catch-all rejection code used when the server refuses the connection or message for policy reasons. Often indicates the sending IP or domain is blacklisted, or the server has a blanket reject policy for unknown senders. Hard bounce caused by reputation or policy. Unlike 550 (address-specific), 554 often reflects a problem with your sending infrastructure rather than the recipient address. Our tool notes 554 responses and recommends checking your sender reputation and authentication records if you see this code frequently across different addresses.

Enhanced status codes. Modern mail servers often append enhanced status codes (RFC 3463) to the basic three-digit code. For example, “550 5.1.1 Recipient address rejected” provides a more specific reason than a bare 550. Our tool captures and interprets these enhanced codes when available, providing more precise diagnostics in your results. The first digit indicates the class (5 = permanent, 4 = temporary), the second digit indicates the subject (1 = addressing, 2 = mailbox, 7 = security), and the third digit provides the specific detail.

Catch-all servers and code 250. Some mail servers are configured to return 250 for every RCPT TO command, regardless of whether the mailbox actually exists. These “catch-all” or “accept-all” servers make SMTP-level verification inconclusive because a 250 response does not guarantee the mailbox is real. Our tool detects catch-all configurations by testing a randomly generated address at the same domain. If the random address also receives a 250 response, the domain is flagged as catch-all and the result is classified as “Unknown” rather than “Low Risk.”

Integrate Bounce Checking Into Your Workflow

Manual spot-checking works for small volumes, but scaling bounce prevention across your organization requires integration with your existing tools and processes. Our platform provides multiple integration paths to embed bounce checking wherever email addresses enter or flow through your systems.

REST API Integration

Our verification API exposes the full bounce-checking pipeline as a single HTTP endpoint. Send a GET or POST request with an email address and receive a JSON response containing the risk level, individual check results, SMTP response code, and recommended action. Average response time is 3–5 seconds per address. The API supports both synchronous single-address lookups and asynchronous batch submissions for larger volumes. Rate limits scale with your plan, from 100 requests per hour on the free tier to unlimited on enterprise plans.

Common API use cases: Real-time form validation on registration and checkout pages. Pre-send verification in custom email-sending applications. Automated list cleaning in data pipeline workflows. Lead scoring enrichment in marketing automation platforms.

Webhook Notifications

For bulk and asynchronous verifications, configure webhooks to receive results as they complete. When you submit a batch of addresses via the API, our system processes them in parallel and sends a POST request to your webhook URL with the results for each address as it finishes. This eliminates the need to poll for results and enables real-time processing in event-driven architectures. Webhook payloads include the email address, risk classification, individual check results, and a timestamp. Failed webhook deliveries are retried up to five times with exponential backoff.

Common webhook use cases: Updating CRM records automatically as verification results arrive. Triggering downstream workflows in Zapier, Make, or n8n based on bounce risk levels. Populating suppression lists in your ESP in real time. Feeding verification results into data warehouses for analytics and reporting.

CRM and ESP Integration

Connect bounce checking directly to your customer relationship management system or email service provider. Our platform integrates with major CRMs including Salesforce, HubSpot, and Pipedrive, and with ESPs including Mailchimp, SendGrid, Postmark, and Amazon SES. Integration options include native connectors, Zapier workflows, and direct API connections. Once connected, new contacts are automatically verified as they enter your CRM, and existing contacts can be bulk-verified on a schedule you define.

Automation examples: Automatically suppress high-risk addresses in Mailchimp before campaign sends. Tag HubSpot contacts with their bounce risk level for segmentation. Trigger a Salesforce alert when a key account’s email address becomes undeliverable. Route undeliverable addresses to a re-validation queue in your support ticketing system.

Form-Level Verification

Embed bounce checking directly into your web forms using our JavaScript widget or API. When a visitor enters an email address and moves to the next field, the widget checks the address in real time and displays an inline error if the address is undeliverable. This prevents invalid addresses from entering your database at the earliest possible point, eliminating bounce risk before it starts. The widget is lightweight (under 5 KB gzipped), works with any form framework, and requires no server-side code. Response time is under 500 milliseconds for cached domains, ensuring a seamless user experience.

Implementation options: Drop-in JavaScript snippet for static HTML forms. React, Vue, and Angular components for modern web applications. Server-side middleware for Node.js, Python, PHP, and Ruby backends. WordPress and Shopify plugins for no-code integration.

Building a bounce prevention pipeline. The most robust approach combines multiple integration points into a layered pipeline. Verify at the point of entry with form-level validation. Re-verify with the API when addresses move between systems (CRM to ESP, for example). Run bulk verification on your full database monthly. Set up webhooks to keep all systems synchronized with the latest verification status. This layered approach catches addresses that degrade between verification cycles, maintaining bounce rates consistently below 0.5% even with high-volume sending programs. Explore our API documentation to get started with integration.

Email Bounce Checker FAQ

Yes. Our email 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 zero risk to your sender reputation from the checking process itself.

A hard bounce is a permanent delivery failure — the mailbox does not exist, the domain is invalid, or the server permanently rejects your message. Remove hard bounces immediately. A soft bounce is a temporary failure — mailbox full, server temporarily down, or message too large. Retry soft bounces 2-3 times, then remove if they persist across multiple campaigns.

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% risk IP or domain blacklisting. Our pre-send bounce checking helps maintain rates well below 1% by identifying and removing problematic addresses before sending.

High bounce rates signal poor list hygiene to ISPs like Gmail, Outlook, and Yahoo. Consequences escalate progressively: first, your emails are throttled (delivered slowly); then they are routed to spam folders; and ultimately your IP or domain may be blacklisted, blocking all email delivery. Recovery takes 4-8 weeks of careful sending behavior.

Our bounce checker works for addresses at virtually all email providers including Gmail, Outlook, Yahoo, corporate mail servers, government domains, and custom domains worldwide. Some servers with catch-all configurations or aggressive greylisting may produce inconclusive results, which are classified as "Risky" or "Unknown" with an explanation.

Check your entire list before every major campaign and at minimum quarterly. Email addresses become invalid at a rate of 2-3% per month through natural decay — people change jobs, abandon accounts, and domains expire. For real-time protection, implement our verification API at signup to prevent bounce-prone addresses from entering your list.

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 categorized as Valid, Invalid, Risky, and Unknown with specific bounce risk reasons. Processing speed is 100,000+ emails per hour.

Risky emails have factors that increase bounce probability but are not definitively invalid. Consider sending to them in a separate, lower-priority campaign, monitoring their bounce rates closely, excluding them from high-stakes sends, or re-checking periodically. Common risk factors include catch-all domains, role-based addresses, and recently created domains.

Stop Bounces Before They Happen

Check any email address for bounce risk above, or verify your entire list in bulk. Protect your sender reputation with 99% accurate bounce prediction.

Try Our Email Verifier Email Verification Service