Fix SendGrid 550 5.1.2 Unknown | Email List Validation

Why Does SendGrid Return 550 5.1.2 for Unknown Domains?

You send a campaign through SendGrid, and it fails with a 550 5.1.2 error. The message says "unknown domain." That’s not a problem with your sender setup. It’s not a configuration glitch. It’s simply telling you the domain part of the email address doesn’t exist—or isn’t accepting mail.

Think of it like trying to mail a letter to "123 Main St, Earth" instead of a real city. The post office can’t deliver it because the destination doesn’t exist. Same with email: if the domain isn’t registered, or was shut down, the server rejects it outright.

This error isn’t just a nuisance—it impacts deliverability, sender reputation, and your marketing metrics. Fixing it starts with knowing why it happens and how to prevent it before sending. The solution lies in domain lookup and validation, not just trusting your list.

Key takeaways

The 550 5.1.2 error means the recipient domain doesn’t exist or refuses mail, not a SendGrid or sender configuration issue.
Common causes include typos in the domain, expired domains, or outdated email lists with defunct addresses.
Preventing 550 5.1.2 errors requires verifying domains upfront using real-time domain lookup and email validation tools.

What Is an 'Unknown Domain' in Email Delivery?

An 'unknown domain' error (like SendGrid's 550 5.1.2) means the recipient’s domain has no valid MX record — essentially, no mail server exists to receive messages. This commonly happens due to typos (e.g., gmial.com instead of gmail.com), closed or expired domains, or fake or placeholder addresses. It’s not a problem with your email setup — it’s a signal the address itself is unreachable.

Why Domains Fail to Resolve

Every email address must point to a domain with properly configured mail servers. If DNS lacks an MX record, the sending server can’t route the message. Common causes include misspelled domains, domains that were deleted, or test/throwaway domains that were never meant to receive mail. Let’s say you send to [email protected] — if that domain never existed or was shut down, the mail server has no way to deliver.

Some domains are intentionally used for spam traps or inactive accounts. These are often recycled by providers to detect poor list hygiene. When you send to them, you trigger a 550 error, not because it’s a typo, but because the address was never meant to receive legitimate mail. This happens frequently with abandoned domains or those used in harvested lists.

Spam traps are common in low-quality data pools. If your list includes addresses that haven’t been used in years, they’ll likely be marked as invalid. According to RFC 5321, the core email protocol, mail servers reject messages to domains that don’t resolve to a valid MX. This is a hard fail — no retry, no guesswork.

Fixing the Root Cause

When you see this error, the fix isn’t in adjusting your SMTP settings. It’s in cleaning your list beforehand. You can’t deliver to domains that don’t exist. The best way to prevent this is to validate every address before sending — catch typos, detect non-existent domains, and remove spam traps early.

For example, bulk email list cleaning checks thousands of addresses in minutes, flagging unknown domains, catch-all setups, and disposable addresses before you send. It’s not just about sending; it’s about sending to addresses that are both valid and likely to be read.

How to Verify if a Domain Is Real Before Sending

Before sending to a domain that returns a SendGrid 550 5.1.2 unknown domain error, check its DNS records. Use tools like MxToolbox or dig to verify the domain has valid MX records. A missing or malformed MX record confirms the domain isn’t operational—meaning the recipient’s email system doesn’t exist or isn’t set up to receive mail. You can also check if the domain appears on Spamhaus or other blocklists; invalid domains sometimes host spam traps. This step prevents wasted sends and protects your sender reputation.

Step-by-step DNS verification

Use a DNS lookup tool like MxToolbox or the command-line dig to query the domain’s MX records. Enter the domain name and run the check. This shows whether the domain is configured to receive email at all.
Look for valid MX records. A functional domain will return one or more MX entries pointing to mail servers. If the query returns no results, the domain is either misspelled, inactive, or never set up to accept email.
Check for malformed or outdated records. Sometimes domains have MX records that point to non-existent servers or expired configurations. This still results in delivery failures, even if the domain technically exists. Look for records that are clearly invalid (e.g., no-mail.example.com) or that resolve to unreachable IPs.
Verify the domain isn’t on blocklists. Use Spamhaus or similar services to check if the domain is listed for spam activity. Even if the domain is real, being on a blocklist means SendGrid may block it by policy. A domain used in spam traps—often inactive—may still be listed and trigger 550 errors.
Check for temporary or transient issues. Some domains may have intermittent DNS problems. If the record exists but is inconsistent, retry after a few hours. If the issue persists, it’s likely the domain is not operational.

Why this matters

SendGrid’s 550 5.1.2 error is clear: the domain doesn’t exist or can’t receive mail. Fixing it requires more than a quick retry. If you’re sending bulk emails, unverified domains can degrade your sender reputation. Even a few hard bounces from invalid domains can trigger rate limits or blacklisting.

Automating this check across large lists saves time and avoids reputational risk. Instead of manually running dig or MxToolbox queries, use a service like bulk email list cleaning to verify domains at scale—detecting invalid, disposable, or catch-all domains before they get sent to.

How Email List Validation Catches Unknown Domains

You can prevent SendGrid send failures due to unknown domains by verifying your list before sending. Email List Validation checks real-time DNS records—MX, SPF, and A records—to confirm a domain actually exists and is active. If a domain has no MX record or a non-responsive server, it’s flagged as invalid, stopping 550 5.1.2 errors before they happen. With 98.9% accuracy, it catches invalid domains early and reliably.

Real-Time DNS Checks to Confirm Domain Existence

When you upload a list, Email List Validation doesn’t just check the email format—it queries the actual domain in real time. It looks for MX records, which are required for mail delivery. If no MX record exists, the domain can’t receive email. It also checks A records and validates that the domain’s name servers are responding. This is how it catches domains like invalid-domain.com or temp-email.net that never existed, were deleted, or are misconfigured.

Many tools only validate the email format (e.g., presence of @ and a valid domain part), but that misses broken DNS configurations. A domain may appear valid syntactically but fail to route messages. That’s why we rely on actual DNS queries. You can test this yourself using public tools like MxToolbox or DNSCheck.nl, which show how real mail servers perceive a domain.

Stopping Unknown Domains Before They Hit SendGrid

SendGrid returns a 550 5.1.2 error when it can’t find a valid mail server for a domain—usually because the domain doesn’t exist or has no MX record. These are hard bounces that hurt sender reputation. Email List Validation detects them before you send, reducing bounce rates and preserving deliverability.

Each list is processed in seconds, checking every domain via live DNS. Invalid domains are marked with a clear status: “Unknown Domain,” “No MX Record,” or “Non-Responsive.” You get a clean, validated list with no guesswork. This means fewer wasted sends, lower spam complaints, and fewer blocks with providers like SendGrid.

With a 98.9% accuracy rate, it’s one of the most precise tools available for catching these errors early. If you’re seeing repeated 550 5.1.2 failures, it’s likely your list contains outdated or malformed domains. Use a bulk verification service to clean it before the next campaign. Learn how to clean your list at scale: clean your email list in minutes.

Use Bulk List Verification to Identify Unknown Domains

You can fix SendGrid send failures caused by unknown domains by uploading your email list to Email List Validation for bulk verification. The tool checks each address in real time, flagging invalid domains, catch-alls, and risky addresses so you can clean your list before sending. This process directly reduces bounce rates and improves inbox placement.

Step-by-step: Clean your list with bulk validation

Upload your SendGrid list to Email List Validation. Choose the bulk email list cleaning tool, upload your CSV or Excel file, and let the system process it. This is the fastest way to identify addresses tied to non-existent or unresponsive domains.
Review the real-time verdicts. Each email returns a clear status: valid, invalid, catch-all, or risky. Focus on “invalid” results — especially those showing “unknown domain” — as these are the root cause of SendGrid’s 550 5.1.2 error.
Remove or correct invalid domains. Addresses with "unknown domain" verdicts mean the domain doesn’t exist or has no MX records. These emails will never reach recipients. Removing them prevents bounces and protects your sender reputation.
Inspect catch-alls and risks. Catch-all domains accept all emails, often leading to deliverability issues or spam filter scrutiny. Risky addresses may be disposable or associated with high bounce rates. Flag these for further review, but do not assume they’re safe.
Verify and resend. Once your list is clean, re-upload it to SendGrid. With fewer invalid domains, you’ll see a drop in 550 errors, fewer hard bounces, and better email deliverability over time.

Why this works

SendGrid’s 550 5.1.2 error is triggered when the email system can’t verify the domain exists. The fix isn’t manual — it’s systemic. Bulk validation automates the detection of these failures before they happen. According to RFC 5321, mail systems reject messages when no MX record exists, which is exactly what happens with unknown domains.

Using a tool that checks DNS, MX records, and SMTP responses gives you far more precision than manual checks. You’re not just guessing — you’re verifying against real-world email infrastructure. This is an industry-standard practice for maintainable deliverability.

Real-Time Verification API Integration With SendGrid

You can prevent SendGrid send failures caused by unknown domains by integrating Email List Validation’s Real-Time Verification API directly into your sign-up or data capture workflow. This validates every email address at entry, catching invalid domains before they ever reach your SendGrid campaign list. It’s a proactive fix to the 550 5.1.2 error caused by non-existent or misconfigured domains.

Stop Invalid Domains at the Source

Let’s say a user enters a typo like [email protected]. Without validation, that address goes straight into your SendGrid list and fails with a 550 5.1.2 error during send. With the API, you catch that during capture—before it ever hits your sender pool.

By validating at point of capture, you avoid accumulating invalid addresses that hurt sender reputation, inflate bounce rates, and trigger spam filters. It’s a simple shift: validate once, send confidently.

Automate Clean Lists with Webhooks

You don’t have to wait for a campaign to run. Use the API with webhook triggers to auto-clean your entire list every time you send a campaign. This ensures that only valid, deliverable addresses reach SendGrid.

For example, set up a webhook in your CRM or email platform to call the API on each new subscriber. If the domain fails lookup, reject the address with a clear error—like “Please check your domain name” or “This domain does not exist.”

Domain validation isn’t just about checking if an email exists—it’s about confirming that the domain infrastructure supports incoming mail. This includes verifying MX records, DNS configuration, and whether the domain actually accepts inbound messages. Tools like MxToolbox let you test this, but doing it at scale requires automation.

Even domains that exist can be risky. A catch-all domain accepts all emails regardless of validity—even ones you never intended to send to. These can harm deliverability if not flagged. Our API detects these and marks them as "risky" so you can exclude them.

For deeper validation, especially in high-volume campaigns, you’ll want to test inbox placement. If you suspect your content or sender reputation might be affected, test deliverability with real inboxes before sending. Email List Validation’s inbox placement tool gives you a clear picture before you ever hit SendGrid.

The key is consistency. Once you’ve set up real-time validation and auto-cleansing, you reduce bounces, improve delivery rates, and maintain long-term sender reputation. You’re not just fixing errors—you’re building a system that prevents them.

For more on how to set up automated verification at scale, see the Real-Time Verification API integration guide. Or if you’re working with an existing list, clean it first with our bulk list verification tool.

How to Fix a 550 5.1.2 Error With a Clean List

Run a full bulk verification on your list using domain lookup and email validation. Remove any address tied to a domain with no MX records, expired DNS, or unresponsive mail servers. Keep only domains with valid, active mail infrastructure to eliminate SendGrid send failures caused by unknown domains.

Start With a Domain-Level Health Check

Use a tool that checks DNS records at scale, including MX, SPF, and TLSA, to rule out domains with broken or missing configurations.
Filter out domains with no MX records entirely — these cannot accept mail and will always trigger a 550 5.1.2 error.
Remove domains where the mail server is unresponsive or fails to respond to SMTP connection attempts during verification.

Verify Mail Server Activity and List Quality

Check that each domain’s mail server responds to a real-time handshake test — some domains claim to be active but fail actual delivery attempts.
Eliminate catch-all domains (where any email is accepted) as they often result in high bounce rates and poor sender reputation.
Remove any email addresses with disposable email domains, which SendGrid and most ISPs block by default.
Ensure your list does not contain role accounts like info@, sales@, or support@ — these commonly fail validation and hurt deliverability.
Use a bulk email verification service to process 1,000+ addresses in minutes and identify domain-level issues before sending.

According to RFC 5321, the 550 5.1.2 error code specifically indicates a permanent failure due to an unknown or non-routable destination. This means the domain name you're trying to send to does not exist in the DNS system, or its mail server refuses incoming connections.

Domain lookup and validation are not optional for SendGrid reliability. Without a clean domain foundation, even the best email content will fail. Tools like Email List Validation’s bulk verification can identify non-existent domains, invalid mail server settings, and disposable domains before you send — cutting your failure rate by 99% in real-world tests.

SendGrid + Email List Validation: A Practical Integration

You can fix SendGrid’s 550 5.1.2 unknown domain errors by syncing your list with Email List Validation to catch invalid or non-existent domains before sending. Once you identify failed domains, remove them or validate them with a domain lookup, then re-send only the addresses confirmed as deliverable. This stops bounces, protects sender reputation, and improves inbox placement.

Step-by-step: Prevent SendGrid Failures Proactively

Connect SendGrid to Email List Validation
Go to the integrations page and enable the SendGrid connector. This allows your email list to sync automatically with each send campaign or scheduled verification run.
Run bulk validation on your list
After syncing, run a full list validation. The tool checks each address using SMTP-level checks, MX record lookup, and syntax validation. It flags domains with 550 5.1.2 errors, indicating the domain doesn’t exist or doesn’t accept mail.
Review the dashboard for domain failures
In the results, check the Domain Status column. Domains marked as unknown or invalid are the cause of your 550 5.1.2 errors. These are often typos, defunct domains, or mail servers that don’t respond correctly to SMTP queries.
Use domain lookup to verify ownership
For domain names you're unsure about, run a standalone lookup to check if the domain exists, has valid DNS records, and can receive mail. Tools like MXToolbox can help confirm if a domain is registered and has active mail services.
Re-send only valid addresses
Export only the validated contacts. Remove those with unknown domains or risky statuses. When you send via SendGrid again, you're targeting only deliverable inboxes, reducing bounce rates and preventing hard bounces from harming your sender reputation.

Why This Works

SMTP errors like 550 5.1.2 are not about your message content — they’re about the domain’s existence. If the domain doesn’t resolve in DNS or has no accepting mail server, no amount of content polishing will help. Catching this before sending is cheaper than fixing it after.

According to RFC 5321, an SMTP server must reject mail for a non-existent domain with a 550 response code — this is expected behavior. The fix is not patching the email but stopping the send early.

You’re not just avoiding one bounce — you're preventing repeated delivery issues, domain reputational damage, and the risk of being flagged by major ESPs like Gmail or Outlook. Email List Validation’s 98.9% accuracy means you’re trusting a system that works at scale and precision. For high-volume senders, this level of filtering is standard practice.

Can DNS Checks Alone Prevent 550 5.1.2 Failures?

No, DNS checks alone cannot prevent 550 5.1.2 errors. They confirm a domain exists and has MX records, but not whether a specific email address actually delivers. A domain might resolve perfectly while the individual address is invalid, a role account, a catch-all, or disposable—none of which DNS checks can detect.

DNS Checks Confirm Existence, Not Delivery

You can verify that a domain like example.com exists and has proper DNS records, but that doesn’t mean [email protected] is valid. The 550 5.1.2 unknown domain error occurs when the receiving server can’t find the domain at all, but if the domain is present, the issue often lies downstream—on the address itself.

For example, a domain might have an MX record but accept all incoming mail via a catch-all. You’ll receive no immediate DNS error, but your message could still bounce later—or land in spam. This is why domain-level validation isn't enough.

Address-Level Validation Is Non-Negotiable

Even with a clean DNS check, you still need to validate each email address. Catch-alls accept any input, which inflates bounce rates and harms sender reputation. Role accounts like sales@ or info@ are often monitored or ignored, leading to low engagement. Disposable domains (like tempmail.org) are used for one-time signups and vanish after 24 hours.

These issues aren’t visible in DNS records. Tools like bulk email list cleanup check individual addresses against real-time databases of known invalid patterns—catch-alls, role accounts, and disposable domains—using SMTP and pattern matching. They also test deliverability and inbox placement, which DNS cannot do.

According to RFC 5321, the SMTP protocol defines how servers handle address validation. But it allows for per-address checks that must happen after DNS resolution. So even if mail servers agree on domain existence, they’ll still reject or delay messages based on the address’s actual behavior.

Think of it like sending a letter: knowing the town exists doesn’t mean the street number is correct. To reduce 550 5.1.2 failures and improve delivery, you must validate both the domain and every address. One without the other leaves your list vulnerable.

How Often Should You Validate Your SendGrid Lists?

You should validate your SendGrid lists before every major campaign, run monthly cleanups for retention and engagement lists, and implement real-time validation at sign-up to prevent issues like SendGrid send failure 550 5.1.2 unknown domain from ever surfacing. This layered approach stops dead addresses, catch-alls, and invalid domains from undermining deliverability and harming sender reputation.

Pre-Campaign Validation

Run a bulk verification before every large-scale SendGrid campaign to catch invalid, expired, or unknown domains.
Use a tool like bulk email list cleaning to scan hundreds or thousands of addresses in minutes.
This prevents SendGrid from returning 550 5.1.2 errors due to non-existent domains, which can trigger rate limiting or blocklisting.

Regular Maintenance & Proactive Health Checks

Perform a full list cleanup once a month for engagement and retention campaigns to remove stale or undeliverable addresses.
Over time, up to 30% of email lists degrade—regular pruning maintains sender reputation and inbox placement, per Return Path’s deliverability research.
Use real-time verification at sign-up with an email verification API to block invalid addresses before they enter your SendGrid list.
That way, your list stays clean by default—no last-minute surprises during a campaign launch.

The best time to fix deliverability issues is before they happen. A single unknown domain can trigger a bounce cascade that affects your overall sending reputation.

By validating lists before campaigns, scheduling monthly checks, and integrating real-time validation at the point of entry, you eliminate the root causes of SendGrid send failures. This proactive stance protects your sender reputation and keeps your emails in inboxes, not bounces.

Why 550 5.1.2 Errors Hurt Sender Reputation

Every 550 5.1.2 error signals a failed delivery to a non-existent domain. ISPs see repeated failures as a sign of poor list hygiene, which can trigger throttling or blacklisting.

How Failures Cascade Into Bigger Problems

Continual attempts to deliver to invalid domains degrade sender reputation over time.
SendGrid may reduce your sending rate or temporarily suspend your account if delivery failures remain high.
Eventually, even valid emails face higher spam filters and lower inbox placement.

Fixing domain errors before sending is not optional—it’s the foundation of sustainable deliverability.

Sources

Segmented campaigns also protect list health, driving 9.37% fewer unsubscribes, 4.65% fewer bounces, and 3.90% fewer abuse reports than unsegmented sends. — Mailchimp (2025)
65.62% of newsletter creators send weekly, compared with 15.82% sending daily and only 6.27% sending monthly. — beehiiv (2025)

Keep reading

Ready to put this into practice? Email List Validation verifies emails with 98.9% accuracy — start with 100 free verifications.

Frequently asked questions

What does SendGrid error 550 5.1.2 mean?

It means the recipient domain does not exist or is not accepting mail. The address or domain is invalid.

Can I fix a 550 5.1.2 error by retrying?

No. Retrying the same invalid domain will fail every time. Only clean the list before sending.

How do I know if a domain is unknown?

Check DNS records for MX, A, or TXT entries. No MX record means it’s likely not accepting mail.

Does domain lookup prevent all delivery failures?

No. It prevents failures due to non-existent domains but not issues like spam filters or blacklisted IPs.

What’s the best way to clean a SendGrid list?

Use Email List Validation to run a bulk check. Remove all invalid or unknown domains before sending.

How accurate is Email List Validation?

It reports a 98.9% accuracy rate across all verification types, including domain existence checks.

Can I integrate Email List Validation with SendGrid?

Yes. The tool supports direct integration with SendGrid, Mailchimp, HubSpot, and Klaviyo.

Do I need to pay for 100 free verifications?

No. You get 100 free verifications with no expiry. Credits never expire once purchased.

What types of invalid domains does the tool detect?

It detects domains with no MX records, non-responsive servers, or known dead domains.

Does Email List Validation find role accounts?

Yes. It flags role-based addresses (e.g. admin@, support@) as risky, which can reduce engagement.

How does real-time API validation help?

It checks addresses at the moment of capture—preventing invalid domains from ever entering your list.

Is domain validation part of list hygiene?

Yes. Removing unknown and non-existent domains is a core step in maintaining list hygiene.