Adding SMTPUTF8 TXT Record to DNS to Resolve 554 SMTP Refusal
Resolve 554 SMTP refusal errors by adding the SMTPUTF8 TXT record to DNS. Learn how to diagnose, verify, and prevent delivery failures with precise.
Why does your email get rejected with a 554 SMTP refusal?
You send an email with a non-ASCII character—maybe a name like Élodie, a subject line in Japanese, or a local domain name with umlauts—and it bounces back with a 554 SMTP refusal. No warning, no explanation. Just a hard stop.
This isn’t spam. It’s not even about your content. A 554 refusal is a technical rejection from the receiving server itself—proof that something in the SMTP handshake failed at the protocol level. The most common culprit? Missing or incorrect SMTPUTF8 TXT records in your DNS.
Without this record, your server can’t declare support for internationalized email, and the receiving mail server refuses the connection outright. It’s like showing up to a meeting in a foreign country without having the right visa—even if your message is valid, the gate won’t open.
Key takeaways
- SMTPUTF8 TXT records in DNS are required for sending emails with non-ASCII characters in addresses or subject lines.
- A 554 SMTP refusal during connection setup often signals a missing or invalid SMTPUTF8 TXT record.
- Resolving this affects deliverability to modern mail systems, especially for global domains and multilingual content.
What is SMTPUTF8 and why does it matter to your email delivery?
SMTPUTF8 lets your email system send messages with non-ASCII characters—like accented names or non-Latin scripts—by extending the traditional SMTP protocol. Without it, servers reject emails containing such characters, especially common in global outreach. Adding the SMTPUTF8 TXT record to your DNS lets mail servers know your domain supports these extended characters, reducing delivery failures and ensuring your messages land in inboxes, not bounces.
How SMTPUTF8 works in practice
Traditional SMTP only allowed ASCII characters in email addresses and headers. That means names like José, Müller, or राम are problematic if you’re not using SMTPUTF8. When your message includes one of these, a receiving server without UTF-8 support will reject it with a 554 error. That’s where SMTPUTF8 comes in—it allows the transmission of UTF-8 encoded content across the full email stack.
The key is DNS configuration. By adding an SMTPUTF8 TXT record to your domain’s DNS, you’re formally announcing that your domain supports UTF-8 beyond the basics. This lets receiving servers safely process your messages, even if they contain non-Latin scripts or diacritical marks. It’s not a magic fix, but it’s a necessary layer for reliable global delivery.
Why your email infrastructure needs this today
With global outreach, multilingual campaigns, and diverse customer bases, you can’t afford to lose messages simply because someone’s name includes an accent. Without proper SMTPUTF8 support, even well-crafted emails fail before they’re delivered. According to the IETF’s RFC 6531, which formalizes SMTPUTF8, this isn’t optional—it’s a step toward inclusive email infrastructure. Major providers like Gmail and Outlook now support it, but not all domains have declared that support.
Verifying your DNS setup isn’t just a technical formality. It’s part of maintaining sender reputation and inbox placement. If your domain sends messages that trigger 554 errors due to missing character support, it affects overall deliverability. You’re not just fixing one error—you’re preventing a cascade of trust issues.
While most tools don’t flag missing SMTPUTF8 records, a proper email verification service can surface these issues indirectly by identifying address formats that would otherwise fail. For example, bulk verification tools like our bulk verification service help you catch invalid or problematic addresses before sending, ensuring your list is clean and deliverable.
How does the SMTPUTF8 TXT record work in DNS?
Adding an SMTPUTF8 TXT record to your DNS tells mail servers your domain supports UTF-8 in email addresses and message headers. If missing or incorrect, servers reject incoming mail with a 554 error. You publish it at the root level (example.com) with the value SMTPUTF8=1, and servers check it before accepting messages.
What the record actually does
When a mail server receives an email with non-ASCII characters—like non-Latin scripts or special diacritics—it checks your domain’s DNS for the SMTPUTF8 TXT record. This record confirms you accept UTF-8 encoding, which is required for proper delivery of global email addresses. Without it, even valid addresses may be blocked outright.
Think of it as a gatekeeper. If your domain doesn’t declare UTF-8 support, the receiving server assumes the message is malformed or potentially malicious and refuses it with a 554 error. This is common when sending to international domains or addresses using accents, Arabic, Cyrillic, or other non-ASCII characters.
How to publish and verify it
You add the TXT record at your domain’s root (not subdomains). The record value must be exactly SMTPUTF8=1. It’s not case-sensitive, but spelling must be exact. Some DNS providers show it as a separate "SPF" or "DKIM" type, but it’s a standalone TXT record.
Once published, propagation can take 1–24 hours. You can test it using tools like MXToolbox or RFC 6531, the official specification for UTF-8 in email. The RFC explains that UTF-8 support is mandatory when using internationalized addresses, and the SMTPUTF8 record is part of the validation chain.
If you're sending to addresses with special characters or managing a global audience, confirming this record is essential. It prevents hard bounces and deliverability issues on messages that would otherwise be valid.
For teams managing large email lists, verifying SMTPUTF8 compatibility is part of broader list hygiene. Use tools like bulk email verification to catch address issues early—including those caused by missing or incorrect DNS records—before they impact your sender reputation or inbox placement.
How to verify your domain has the correct SMTPUTF8 TXT record
Run a DNS lookup on your domain using a tool like MxToolbox or dig. Check for a TXT record at the root (@ or your domain name) with the value SMTPUTF8=1. If it’s missing, malformed, or set to something else, your emails may be silently rejected with a 554 error—especially if you’re sending to international addresses with non-ASCII characters. This one check often explains why outbound mail fails.
Step-by-step: How to confirm your DNS record is correct
- Go to a DNS lookup tool such as MxToolbox or open your terminal and run
dig TXT yourdomain.com. - Look through the results for a TXT record with a name of
@or your full domain (e.g.,example.com). - Check the record value. It must be exactly
SMTPUTF8=1. No extra spaces, quotes, or other content. - If the record is missing, shows another value, or contains malformed syntax (like
SMTPUTF8=11), your server is not signaling support for UTF-8 in email headers and addresses—this triggers 554 rejections from strict mail servers. - Compare your result with the specification in RFC 6531, which defines SMTPUTF8 as part of modern email standards. A correct setup enables proper delivery of emails with non-ASCII characters in sender or recipient fields.
Why this matters for your deliverability
Many modern email systems now expect the SMTPUTF8 TXT record to be present. Without it, even valid email addresses can fail silently—especially outside the US. The 554 refusal response is common in mail logs when the sender claims UTF-8 support but lacks the DNS signal. This is not a sender reputation issue; it’s a protocol compliance issue.
Once confirmed, fix any missing or incorrect records in your DNS provider’s interface. Updates can take up to 48 hours to propagate. After that, test your outbound mail flow again—especially to domains in Europe, Asia, or Latin America.
If you’re managing a large email list or sending via third-party platforms (like SendGrid or Mailchimp), use bulk email verification to detect invalid or non-deliverable addresses early. A clean list improves your sender reputation and reduces the risk of hitting 554 errors due to outdated or malformed domains.
Adding the SMTPUTF8 TXT record to your DNS zone
Adding an SMTPUTF8 TXT record with value SMTPUTF8=1 to your DNS zone lets mail servers accept international email addresses with non-ASCII characters. This resolves SMTP refusal errors like 554 when sending to domains that use UTF-8 in email addresses, such as café@example.com. The change takes effect after DNS propagation, typically within minutes to 24 hours.
Step-by-step DNS configuration
- Log in to your domain’s DNS management interface—this is usually your hosting provider’s dashboard, like Cloudflare, GoDaddy, or AWS Route 53. You need access to edit DNS records at the zone level for your domain.
- Create a new TXT record. Set the name to
@(for the root domain) or your full domain (e.g.,example.com). This record applies to the domain itself, not subdomains. - Set the value to
SMTPUTF8=1. This signals to receiving mail servers that your domain supports internationalized email addresses (RFC 6531). Without it, servers may reject valid UTF-8 emails with a 554 SMTP refusal. - Set TTL to 3600 (one hour) or use the default. A shorter TTL speeds up future changes. Most providers accept 3600 as standard.
- Save the record. Changes propagate across the internet over time. While DNS updates can appear in minutes, full propagation may take up to 24 hours due to caching.
Testing the change
After saving, verify the record was added correctly using tools like MXToolbox or DNSLeakTest. Query for TXT records on your domain and confirm SMTPUTF8=1 appears. Many email verification services, such as bulk email verification, can also validate delivery readiness by checking for such DNS records during address validation. Once confirmed, your domain can reliably send to email addresses with non-Latin characters.
When sending in multilingual campaigns, this small DNS adjustment prevents 554 errors from mail servers that don’t recognize UTF-8 support. It's an industry-standard fix for international email compatibility and ensures your email infrastructure remains robust across global audiences.
How SMTPUTF8 impacts inbox placement and deliverability
Adding an SMTPUTF8 TXT record to your DNS helps prevent 554 SMTP refusal errors when sending emails with non-ASCII characters—like accented names, non-Latin scripts, or special emojis. Without it, modern email gateways may reject your messages even if your sender reputation is strong, hurting inbox placement. Proactively configuring SMTPUTF8 reduces edge-case bounces and improves reliability, especially for global campaigns.
Why missing SMTPUTF8 causes delivery issues
When your domain doesn’t support SMTPUTF8, email servers that handle multilingual content may flag your messages as invalid—especially if they contain non-ASCII characters in subject lines, sender names, or headers. This isn’t about spam; it’s about protocol compliance. Even a single invalid character can trigger a 554 error if the receiving server enforces strict UTF-8 validation.
Mail providers like Gmail, Outlook, and Apple Mail increasingly validate the presence of SMTPUTF8 records during transactional and bulk email processing. If your domain lacks the TXT record, that validation fails—even if your IP reputation, SPF, DKIM, and DMARC are all solid. This means you can be blocked not for being bad, but for not meeting basic internationalization standards.
How it improves deliverability long-term
While strong sender reputation helps, it doesn’t override protocol-level issues. A missing SMTPUTF8 record increases the chance of hard bounces or quarantined messages, especially for users in regions using non-Latin scripts. Over time, these edge-case failures can damage your sender reputation, even if they don’t appear in sender reputation reports immediately.
Configuring the SMTPUTF8 TXT record correctly—using the standard format defined in RFC 6531—ensures your domain is recognized as UTF-8-capable. This reduces unexpected rejections and boosts consistency, particularly for campaigns targeting users in Europe, Asia, or Latin America. It’s not a substitute for good content or list hygiene, but it removes a common technical barrier to inbox placement.
Let’s say you’re sending a promotional email with a subject like “¡Hola, ¡Bienvenido/a! 🎉” or “Morgen, liebe Kunden.” Without SMTPUTF8, those messages may fail silently. Using a tool like bulk verification, you can detect not only invalid addresses but also signs of problematic headers or metadata that could lead to such failures before they happen.
How Emaillistchecker.io helps prevent SMTPUTF8-related delivery failures
You can prevent SMTPUTF8-related 554 errors by verifying that email addresses and domains support UTF-8 encoding before sending. Our tools check for valid syntax, domain-level UTF-8 readiness, and inbox placement—catching issues that would otherwise trigger delivery refusal. This reduces failures from invalid, unsupported, or malformed addresses.
Real-Time Validation for UTF-8 and Protocol Compliance
Let’s be clear: not every email server supports non-ASCII characters in addresses. When your message includes a name like "José@domain.com" and the recipient’s server doesn’t support SMTPUTF8, it will reject the connection with a 554 error. Our real-time API checks recipient domains for support of UTF-8 and standard email protocols, including DMARC and SPF, before you send. This means you’ll catch unsupported domains early, even if they appear valid at first glance.
Unlike tools that only validate syntax, Emaillistchecker.io evaluates the actual deliverability path—including whether the receiving server allows non-ASCII input. This prevents wasted sends on addresses that technically pass syntax checks but fail during SMTP negotiation. You’re not just checking format—you’re testing real-world readiness.
Bulk Checks and Inbox Placement Testing
If you’re sending to a large list, especially with international recipients, bulk verification is essential. Our bulk verification tool scans entire lists for deliverability health, flagging any address with a mismatched or unsupported domain configuration. The system identifies risky or invalid addresses—especially those with non-ASCII components—before you hit Send.
Even if a domain supports SMTPUTF8, your message might still end up in spam folders. That’s why our inbox placement tests simulate delivery across providers like Gmail, Outlook, and Apple Mail. These tests confirm your message not only reaches the server but lands in the inbox, even when UTF-8-encoded data is involved. You’re getting a real-world preview of performance.
Our 98.9% accuracy rate comes from continuous updates to our domain database and validation logic. We don’t rely on outdated checks—we assess live server behavior, including support for SMTPUTF8, greylisting, role accounts, and disposable domains. This helps you avoid the 554 refusal caused by sending to a server that doesn’t understand extended character sets.
For detailed verification workflows, explore our bulk verification tool or integrate our API for automated validation in real time. Whether you’re validating a list manually or syncing with Mailchimp, HubSpot, or SendGrid, our integrations keep your workflows efficient and error-free.
SMTPUTF8 isn’t just a technical detail—it’s a delivery gate. We help you test it at scale, without guesswork.
Common pitfalls when setting up SMTPUTF8 TXT records
Setting up an SMTPUTF8 TXT record often fails not because of the mechanism itself, but due to small errors like placing it on the wrong domain, missing the required prefix, or ignoring DNS propagation delays. These issues are common even among experienced admins, and catching them early prevents 554 SMTP refusal errors during email delivery. Let’s walk through the most frequent missteps that break validation.
Incorrect placement or structure
- Don’t use a subdomain like
mail.example.com—the SMTPUTF8 record must be at the root domain (example.com). - Always include the required
SMTPUTF8=1syntax—just entering1is invalid and will be ignored by compliant systems. - Check your DNS provider’s interface: some tools treat
"1"as a string, not a valid TXT value. You must enter the fullSMTPUTF8=1as a single string.
Conflicts and delays
- Running multiple TXT records for the same domain with different
SMTPUTF8values creates ambiguity. DNS resolvers may return unpredictable results—only one valid record should exist. - Assuming the record is live immediately after update is a common mistake. DNS propagation can take anywhere from a few minutes to 48 hours. Use DNSChecker.org or MXToolbox to verify the record is visible globally before testing email delivery.
- Verify your setup using the inbox placement test to confirm the domain resolves properly in real-world SMTP environments.
SMTPUTF8 is part of an industry-standard mechanism defined in RFC 6531, which specifies how UTF-8 email addresses should be handled. Getting it wrong can break delivery to recipients with non-ASCII characters in their addresses—especially in European or Asian regions where extended characters are common.
How to test if SMTPUTF8 is working after DNS update
After updating your DNS with the SMTPUTF8 TXT record, verify it’s working by sending an email with non-ASCII characters—like a subject line with accented letters or an address with Unicode. If the email delivers without a 554 error, your SMTPUTF8 configuration is active. Use tools like Mail-Tester or SendGrid’s SMTP diagnostic utility to trace delivery and check DNS responses directly.
Step-by-step verification process
- Send a test email with non-ASCII content. Use an email address like
café@example.comor a subject with characters like "Café, Münchener Beruf". This triggers the SMTPUTF8 protocol during delivery. If your server rejects it with a 554 code, SMTPUTF8 isn’t active or isn’t properly recognized. - Check delivery logs for rejection codes. Look for SMTP errors like
554 5.7.1 Message rejected due to policyor explicit554 SMTPUTF8rejections. These indicate the mail server didn’t accept the UTF-8 content, pointing to a misconfigured or missing TXT record. - Run the message through an SMTP diagnostic tool. Use services like Mail-Tester or SendGrid’s SMTP diagnostic tool to simulate delivery. These tools analyze the full flow—SMTP handshake, header parsing—and report whether UTF-8 was accepted. If the tool shows
SMTPUTF8=1in the report, you're good. - Confirm the TXT record is publicly visible. Use standard DNS lookup tools like DNSChecker.org or
dig TXT example.comfrom the command line. The output must show a TXT record withSMTPUTF8=1. If it’s missing or outdated, the change hasn’t propagated.
Why each step matters
Only a real test with non-ASCII content truly triggers SMTPUTF8. A DNS record alone doesn’t guarantee functionality—delivery depends on both DNS and server-side handling. Mail-Tester and SendGrid’s diagnostics replicate real ISP behavior, which is more reliable than internal logs. The final check on public DNS ensures your domain is ready for global sending, especially for international audiences.
For teams managing large send lists, verifying UTF-8 readiness is part of ensuring inbox placement. You can validate entire lists for technical health, including invalid or malformed domains, using bulk verification tools that detect issues before sending.
Other DNS records that affect SMTP delivery success
You can have a perfect SMTPUTF8 TXT record, but if your SPF, DKIM, or DMARC records are missing or misconfigured, receiving servers may still reject your email with a 554 refusal. These three records form the core of email authentication—without them, your messages appear suspicious even if technically compliant. Let’s go over what each actually does and why missing or incorrect versions can block delivery.
SPF: Authorizing Your Sending Servers
SPF (Sender Policy Framework) tells receiving mail servers which IP addresses are allowed to send email on your domain’s behalf. If you send from a new server or service without updating SPF, the recipient may reject the message. A common mistake is failing to include all authorized systems, including third-party email platforms like SendGrid or Mailchimp.
DKIM: Ensuring Message Integrity
DKIM adds a digital signature to each outgoing email. Receiving servers verify this signature using your domain’s public key in DNS. If DKIM is missing or malformed, the message may be flagged as tampered or untrusted—even if SPF passes. This is especially critical for bulk senders.
DMARC: Setting the Ground Rules
DMARC (Domain-based Message Authentication, Reporting & Conformance) builds on SPF and DKIM. It tells receivers what to do with messages that fail authentication—either quarantine them or reject them outright. If DMARC is set to reject but SPF or DKIM fails, your email gets blocked regardless of other settings.
Even with a correctly added SMTPUTF8 TXT record, one weak link in this chain can cause a 554 refusal. For example, a misconfigured DKIM selector or an SPF record that excludes a critical IP will result in rejection. These issues often go unnoticed until your delivery rates drop unexpectedly.
Real-world data shows that SPF, DKIM, and DMARC alignment errors contribute to a significant portion of bounce and rejection rates—particularly for outbound marketing and transactional mail. Testing your full authentication stack is not optional, it’s essential. Tools like inbox placement testing help identify such gaps before they impact deliverability.
For those managing large lists, automated verification can catch misconfigured domains early. Bulk verification checks not just validity but also domain-level authentication health across your entire list. It’s a way to preempt delivery failures before sending.
When diagnosing SMTP 554 refusals, always audit your DNS records for SPF, DKIM, and DMARC—not just SMTPUTF8. You can reference standards like RFC 7243 (for SMTPUTF8) and RFC 7483 (for DMARC) for guidance, but real-world delivery depends on all three working together.
Fixing 554 SMTP refusal is not about content—it’s about infrastructure
A 554 error is rarely caused by your message content or list quality. It is a signal that your email infrastructure fails to meet modern SMTP standards at the server level.
Issues like missing or incorrect SMTPUTF8 TXT records in DNS often prevent delivery, even when everything else—content, domain reputation, and sending practices—appears correct. These are protocol-level barriers, not list hygiene problems.
Ensuring your domain supports SMTPUTF8 is one of the final, frequently overlooked steps in full deliverability compliance. It’s not about tweaking copy or cleaning your list—it’s about validating that your DNS and mail server configuration are fully RFC-compliant.
Use Emaillistchecker.io to validate your list and infrastructure holistically—before sending, not after.
Sources
- By early 2026, 937,931 of 1.8 million analyzed domains had valid DMARC records — up 79% in three years — but about 56% of them still sit at monitoring-only p=none. — DMARC Report (EasyDMARC 2026 data) (2026)
- Validity's analysis of 22+ million domains found 84% of domains used in email From addresses have no published DMARC record at all. — Validity (2024)
Keep reading
- Email authentication: SPF, DKIM, DMARC and BIMI (complete guide)
- Email Deliverability Platform with TLS Handshake Timeout Detection in Clustered SMTP Environments
- Resolving Transient SMTP 451 Errors Caused by TLS Timeout in Clusters
- Integrated Email Verification and DMARC Alignment Enforcement Tool 2026
- How to Validate SMTP 250 Success Code with Delayed TLS Handshake in Email Clusters
Ready to put this into practice? Emaillistchecker.io verifies emails with 98.9% accuracy — start with 100 free verifications.
Frequently asked questions
What does SMTPUTF8=1 mean in a DNS TXT record?
It indicates that your domain supports UTF-8 encoding in email addresses and headers, allowing non-ASCII characters in messages.
Can I have multiple SMTPUTF8 TXT records?
No. DNS allows only one TXT record per name. Multiple entries are not valid and can cause delivery issues.
Why do I get a 554 error even with a correct SMTPUTF8 record?
Other factors like SPF misconfiguration, blacklisting, or a rejected message from a non-compliant server may cause 554 refusals.
Does SMTPUTF8 affect only non-ASCII email addresses?
Yes—only messages involving non-ASCII characters in the sender, recipient, or subject require SMTPUTF8 support.
How long does it take for a new SMTPUTF8 TXT record to take effect?
DNS propagation can take up to 24 hours, but most DNS providers update within minutes.
Is SMTPUTF8 required for every email sender?
Only if your messages include non-ASCII characters. Most standard ASCII-only emails don’t require it.
Can Emaillistchecker.io detect missing SMTPUTF8 records?
Not directly, but our deliverability tests and domain checking can flag delivery risks tied to protocol compliance.
Why don’t major email providers require SMTPUTF8 by default?
Because most emails still use ASCII-only content. It’s only necessary when extended character support is needed.
What happens if I don’t add the SMTPUTF8 TXT record?
Emails with non-ASCII content from your domain will be rejected with a 554 SMTP refusal by compliant servers.
Does Emaillistchecker.io help with DNS-level deliverability checks?
It verifies the deliverability of email addresses and domains, helping you identify infrastructure-related risks before sending.
Can SMTPUTF8 prevent spam filtering?
No—it doesn’t affect spam filtering directly. It only ensures technical compatibility with non-ASCII content.
Are SMTPUTF8 records checked by all mail servers?
Not universally. Smaller or legacy systems may not enforce UTF-8 requirements, but modern servers do.