Learning Centre

Why Do Emails Bounce Back And What Do Bounce Messages Mean?

Learn why emails bounce back, what bounce messages mean, and how to identify delivery issues linked to mailboxes, servers, DNS records or email authentication.

On this page

    Definition

    Email Bounce Back

    An email bounce back is a delivery failure notification sent when an email cannot reach the recipient. The message usually explains whether the problem is temporary, permanent, caused by the recipient mailbox, or related to the sender’s domain, email server or DNS authentication.

    Bounce messages are also called non-delivery reports, delivery status notifications or NDRs. They can look technical, but the key details usually reveal the cause.

    Key Takeaways

    • Email bounce backs usually fall into two broad groups: hard bounces, which are permanent failures, and soft bounces, which are temporary delivery problems.
    • Common causes include mistyped addresses, full mailboxes, blocked attachments, poor sender reputation, authentication failures and incorrect DNS records.
    • If business emails bounce regularly, the issue should be investigated because it can affect communication, trust, invoicing, enquiries and email deliverability.

    Quick explanation

    Why Emails Bounce Back

    Emails bounce back when the sending mail server tries to deliver a message and the receiving mail server rejects it or cannot accept it. The bounce message is the email system’s way of saying, “delivery failed”, along with a reason. For a business, this matters because email is often tied to quotes, invoices, website enquiries, booking confirmations and client communication. A single bounce may be harmless, especially if an address was typed incorrectly. Repeated bounce backs can point to a deeper problem with DNS, mailbox configuration, email authentication or domain reputation. Most bounce messages include a short explanation and a technical status code. You do not need to understand every line, but you should look for the delivery status, the recipient address and the reason given by the recipient’s mail server.
    Business email delivery depends on mailbox configuration, DNS records and recipient server checks.
    Business email delivery depends on mailbox configuration, DNS records and recipient server checks.

    Bounce types

    Hard Bounces vs Soft Bounces

    A hard bounce is a permanent delivery failure. It usually means the recipient address does not exist, the domain is invalid, or the receiving server has permanently rejected the message. If an address hard bounces, you should not keep sending to it without confirming the address. A soft bounce is a temporary delivery failure. The recipient mailbox may be full, the receiving server may be unavailable, the message may be too large, or the receiving system may temporarily block delivery. In many cases, the sending server will try again for a limited time before giving up. Bounce messages often use SMTP status codes. Codes starting with 5 usually mean a permanent failure, while codes starting with 4 usually mean a temporary failure. For example, a 550 error often means the recipient address was rejected, while a 451 error often points to a temporary server or policy issue.
    Understanding the bounce type helps you decide whether to retry, correct the address or review your email setup.
    Understanding the bounce type helps you decide whether to retry, correct the address or review your email setup.

    Common Bounce Message Meanings

    Bounce wording varies between email providers, but many messages point to similar causes. The exact fix depends on the sender, recipient and domain configuration.

    Bounce message or code What it often means What to check
    550 user unknown or recipient rejected The recipient address may not exist, may have been disabled, or may be blocked by the receiving server. Confirm the spelling of the address, check whether the contact has changed email, and avoid repeated sending until confirmed.
    Mailbox full or quota exceeded The recipient’s mailbox has no available storage, so the server cannot accept more mail. Try again later or contact the recipient through another channel if the message is important.
    SPF, DKIM or DMARC failure The receiving server could not verify that your email was authorised to send from your domain. Review DNS authentication records, sending services, domain alignment and any recent email platform changes.

    Troubleshooting Email Bounce Backs

    Start with the bounce message itself. It usually contains the failed recipient, the server that rejected the email and a status code or explanation.

    Only one recipient bounces

    Likely cause

    The recipient address may be wrong, inactive, full or rejecting messages because of a local policy.

    Solution

    Check the spelling, remove extra spaces, confirm the address with the recipient and try again only after the address is verified.

    Many recipients bounce at once

    Likely cause

    Your email platform, DNS records, domain authentication or sending reputation may have changed or failed.

    Solution

    Check SPF, DKIM, DMARC, MX records, recent DNS changes, email provider alerts and whether a third-party sending tool is properly authorised.

    Website form emails bounce or never arrive

    Likely cause

    The website may be sending from an unauthorised address, the recipient mailbox may reject the message, or domain authentication may be incomplete.

    Solution

    Review the form sender address, mail routing, DNS authentication and website hosting configuration. A form should send in a way that aligns with the domain’s email policy.

    Do Not Ignore Repeated Bounce Backs

    A single bounced email is usually not serious. Repeated bounces from normal business communication can damage sender reputation, interrupt sales conversations and cause invoices, forms or client messages to be missed. If bounce backs increase after a DNS, hosting or email platform change, review the setup before the problem spreads.

    DNS and authentication

    How DNS Records Affect Email Delivery

    DNS does more than connect a domain to a website. It also tells mail servers where email should be delivered and which services are allowed to send email for your domain. MX records tell the internet which mail servers receive email for your domain. SPF records list the servers or platforms authorised to send on your behalf. DKIM adds a signature that helps prove the message has not been changed in transit. DMARC tells receiving servers how to handle messages that fail SPF or DKIM checks. If these records are missing, outdated or misaligned, legitimate emails may bounce or be sent to spam. This is common after moving to Microsoft 365, changing website hosts, adding a CRM, using an invoicing platform, or connecting a marketing email tool. Each sender needs to be configured correctly, otherwise the domain may appear suspicious to receiving servers.
    DNS authentication helps receiving servers decide whether an email is likely to be legitimate.
    DNS authentication helps receiving servers decide whether an email is likely to be legitimate.

    Email Bounce Back Terms

    These terms often appear in bounce messages and email delivery diagnostics.

    NDR
    A non-delivery report is the message sent back to the sender when an email cannot be delivered.
    SMTP status code
    A technical code that explains the delivery result. Codes beginning with 4 usually indicate temporary problems, while codes beginning with 5 usually indicate permanent failures.
    Sender reputation
    A trust signal used by email systems. It can be affected by bounce rates, spam complaints, sending patterns and domain authentication.

    Diagnosis process

    How to Read a Bounce Message

    Bounce messages can be long, but you can usually diagnose the issue by looking at three parts.

    1. Find the failed recipient address

      Check which email address bounced. If only one address is affected, the issue is often with that address or recipient mailbox.

    2. Look for the status code

      A 5xx code usually indicates a permanent failure, while a 4xx code usually indicates a temporary issue. The wording beside the code often gives the clearest clue.

    3. Check whether the message mentions authentication

      References to SPF, DKIM, DMARC, policy rejection or unauthorised sender suggest a domain or email platform configuration issue.

    Common Mistakes That Make Bounce Backs Worse

    Many email problems are made worse by guessing at the fix. A careful review is safer than changing records at random.

    Keeping invalid addresses in a contact list

    Do this instead

    Remove or verify addresses that hard bounce. Repeatedly sending to invalid addresses can harm sender reputation.

    Changing DNS records without documenting the current setup

    Do this instead

    Record existing MX, SPF, DKIM and DMARC settings before making changes. This helps you reverse or compare changes if delivery breaks.

    Assuming email delivery and inbox placement are the same

    Do this instead

    A delivered email can still land in spam. Authentication helps, but content, reputation, recipient behaviour and provider rules also influence placement.

    Email Bounce Review Checklist

    Use this checklist when bounce backs become frequent, affect multiple people, or start after a platform change.

    • Confirm the bounce pattern

      Check whether the issue affects one recipient, one sender, one domain, website forms, or the whole business.

    • Review email authentication

      Check SPF, DKIM and DMARC records, especially if you use Microsoft 365, a website form, CRM, invoicing tool or marketing platform.

    • Check recent changes

      Look for DNS changes, domain transfers, hosting migrations, mailbox changes, new sending tools or security policy updates.

    When to get help

    Can You Fix Email Bounce Backs Yourself?

    Simple bounce backs can often be handled internally. If an address is wrong, correct it. If a mailbox is full, ask the recipient to clear space or provide another address. If the message is too large, reduce the attachment size or use a file-sharing method. Professional help becomes worthwhile when the issue affects multiple users, website forms, invoices, Microsoft 365 mailboxes, DNS authentication, domain reputation, or several connected providers. It is also sensible during migrations, because email, DNS, hosting and website forms can depend on each other. Avoid changing DNS records unless you understand what each record does. Incorrect MX records can stop inbound email. A broken SPF record can cause legitimate outgoing mail to fail authentication. A strict DMARC policy can reject messages from tools that have not been authorised correctly.
    Business email problems are often easier to resolve when domain, DNS, hosting and email systems are reviewed together.
    Business email problems are often easier to resolve when domain, DNS, hosting and email systems are reviewed together.

    Our approach

    How We Approach Business Email Deliverability

    We treat email as part of a business’s digital infrastructure, not as a separate app that can be configured in isolation. A reliable setup often depends on the domain, DNS records, mailbox provider, website forms and any third-party tools that send email on behalf of the business. Where relevant, we review DNS configuration, email authentication records, mailbox setup, sending services and website form behaviour. We also plan email migrations carefully, preparing and testing the new environment before cutover where possible and coordinating DNS changes to reduce disruption. No provider can guarantee email delivery, inbox placement, spam filtering outcomes or uninterrupted third-party email availability. What we can do is configure the technical foundations correctly, reduce avoidable errors and help diagnose issues across the systems we manage or support.
    Email deliverability is strongest when DNS, mailbox settings and connected sending tools are configured with a clear technical plan.
    Email deliverability is strongest when DNS, mailbox settings and connected sending tools are configured with a clear technical plan.

    Email Bounce Back FAQs

    These answers cover common questions businesses ask when emails start bouncing.

    Does a bounced email mean my email account is broken?

    Not always. A single bounce may be caused by an incorrect recipient address or a full mailbox. If many emails bounce, or bounce messages mention SPF, DKIM, DMARC or policy rejection, your email setup should be reviewed.

    Can SPF, DKIM and DMARC stop all bounce backs?

    No. Email authentication improves trust and helps receiving servers verify your messages, but it cannot guarantee delivery or inbox placement. Recipient policies, mailbox issues, reputation and message content still matter.

    Why do emails from my website form bounce?

    Website forms can bounce if they send from an unauthorised address, use incorrect mail settings, or fail domain authentication checks. The website, hosting environment and email DNS records may all need to be reviewed together.

    Need Help Diagnosing Email Bounce Backs?

    If business emails are bouncing, landing in spam or failing after a domain, hosting or Microsoft 365 change, we can review the technical setup and explain what needs attention.

    Discuss Your Email Requirements View Email Hosting

    Keep learning

    Tap to call
    Enquire now

    Ask Dobble

    Ask a question

    Send us your question and the Dobble team will get back to you.

    Prefer to talk to us directly?

    Get in touch

    Contact us

    Tell us about your project and the Dobble team will be in touch shortly.

    Prefer to talk to us directly?