Summary
IDN/Punycode domains use Unicode characters converted to ASCII for DNS compatibility, allowing for broader language support. However, they present phishing risks and face deliverability issues due to inconsistent support across systems. A common Gmail authorization error is pasting the TXT record into MX record fields, which prevents email delivery. Fixing this involves correctly setting up MX and TXT records as prescribed by Google Workspace and testing across different email clients. Ensure systems universally accept all domain name scripts.
Key findings
- IDN/Punycode Domains: Represent Unicode characters in ASCII format for DNS compatibility.
- Phishing Risk: IDNs can be used in phishing attacks by utilizing similar-looking characters.
- Deliverability Issues: Inconsistent support for IDNs across email clients and servers can cause delivery problems.
- Gmail Authorization Error: Pasting the TXT record into the MX record field is a common misconfiguration in Google Workspace.
- Importance of MX Records: Correct MX record setup is crucial for directing email to the correct mail server.
- TXT vs MX Record Usage: TXT records provide text information and should not be used in place of MX records.
- Universal Acceptance: Ensuring all systems support and correctly process all domain name scripts.
Key considerations
- Thorough Testing: Test IDN handling across various email clients and systems to ensure proper display and functionality.
- Correct DNS Configuration: Verify that MX and TXT records are configured according to Google Workspace instructions.
- Phishing Awareness: Be aware of potential phishing attacks using visually similar IDN characters.
- Address Universal Acceptance: Ensure all systems support and process all domain name scripts correctly.
- DNS Settings Check: Verify DNS settings and ensure MX records are correctly configured.
What email marketers say
11 marketer opinions
IDN/Punycode domains use non-ASCII characters, converted for DNS compatibility, allowing for broader language support. However, they can be used in phishing and may face deliverability issues due to inconsistent support across systems. A common Gmail authorization error is pasting the TXT record into MX record fields, causing email delivery failure. Fixing this involves correctly setting up MX and TXT records as provided by Google Workspace.
Key opinions
- IDN/Punycode Purpose: IDN/Punycode domains enable the use of non-ASCII characters in domain names, broadening language support and local recognition.
- Phishing Risk: IDNs can be exploited in phishing attacks by using similar-looking characters from different alphabets.
- Deliverability Issues: Inconsistent support for IDNs across email clients and servers can cause deliverability problems, including emails being blocked or marked as spam.
- Gmail Authorization Error: A common misconfiguration is pasting the TXT record into the MX record field when setting up Google Workspace, which prevents email delivery.
- MX record and TXT record differences: TXT records are for text information, whereas MX records are for routing emails to mail servers.
Key considerations
- Test IDN Support: Test email deliverability with IDN addresses across various email clients and systems to ensure proper display and functionality.
- Verify DNS Records: When setting up Google Workspace, carefully verify that MX and TXT records are configured according to Google's instructions to avoid email delivery issues.
- Be aware of Phishing: Be aware of domains using IDN to spoof a real URL.
- Proper Set Up of MX: Set up MX records as provided by Google Workspace.
Marketer view
Email marketer from VeriSign shares that Punycode is a way to represent Unicode characters using the limited ASCII character set, allowing for the use of non-English characters in domain names. It provides compatibility with the existing DNS infrastructure.
13 Mar 2022 - VeriSign
Marketer view
Email marketer from StackOverflow shares that a common mistake is to paste the TXT verification record into the MX record field when setting up Google Workspace. This leads to a non-functional email setup, because MX records require specific server address formats, not arbitrary text.
22 Sep 2021 - StackOverflow
What the experts say
2 expert opinions
IDN support is not universal, so testing is critical for deliverability. Gmail authorization errors often involve incorrectly pasting the TXT record into the MX record, causing email delivery failure and requiring MX record resolution.
Key opinions
- IDN Support: Older systems may not fully support IDNs, necessitating thorough testing.
- Gmail MX record Errors: Pasting the TXT record in the MX record during Gmail setup is a common authorization error.
- Consequences of MX Record Errors: Incorrect MX record configuration results in email delivery failure.
Key considerations
- Test IDNs: Test how IDNs are handled across different email clients and systems.
- Resolve MX Records: Ensure correct MX record setup for Gmail authorization to guarantee email deliverability.
Expert view
Expert from Word to the Wise explains that while IDNs are gaining support, many older systems and software may not fully support them. He shares that it's essential to test how IDNs are handled by different email clients and systems to ensure proper display and functionality.
22 Jan 2025 - Word to the Wise
Expert view
Expert from Email Geeks explains that the MX record issue looks like someone made a mistake with their Gmail/Google authorization records, pasting the TXT record in the MX. They also explain this means they don't receive mail and it's important to resolve MX records.
17 Jan 2025 - Email Geeks
What the documentation says
5 technical articles
IDNs use Unicode, converted to ASCII Punycode for DNS compatibility. Correct MX record setup is crucial for email delivery, especially in Google Workspace, where TXT records should not replace MX records. Universal acceptance ensures all scripts work across all systems.
Key findings
- IDN Definition: IDNs use Unicode characters, converted to ASCII Punycode.
- MX Record Importance: Correctly configured MX records are crucial for email delivery.
- Google Workspace Setup: Follow instructions carefully for MX and TXT records to avoid misconfiguration.
- Punycode Reversibility: Punycode conversion is reversible, allowing recovery of the original Unicode string.
- Universal Acceptance: Universal Acceptance ensures all domain names and email addresses are universally accepted.
Key considerations
- Follow Instructions: Adhere to setup instructions, especially for DNS records.
- Verify MX Records: Verify MX records to ensure correct email routing.
- Ensure Universal Acceptance: Ensure all systems support and correctly process all domain name scripts.
Technical article
Documentation from Google Domains explains that DNS records must be setup according to the instructions to enable services to function. For Google Workspace, follow all instructions for MX records, TXT records etc. or risk a misconfiguration.
1 May 2025 - Google Domains
Technical article
Documentation from Internet Society shares that universal acceptance is about ensuring all domain names and email addresses, regardless of script, can be used by all applications, devices, and systems. It means websites are accessible, email is delivered, and users can fully participate online, no matter their language or script.
6 Jun 2022 - Internet Society
How can I avoid Gmail security warnings on emails?
How can I avoid the Gmail promotions tab and should I even try?
How can I fix my Gmail email deliverability issues?
How can I improve email deliverability from GSuite when sending 1-to-1 emails and encountering spam placement issues?
How can I improve my domain reputation with Gmail?
Why is there a sudden increase in Gmail spam filtering?
