The consensus is that new or uncommon domain extensions (gTLDs) have an indirect but noticeable impact on email deliverability. While email protocols don't technically discriminate against them, ISPs and spam filters might treat them with more suspicion due to a higher association with spam or lower-quality content. This can result in lower sender reputation. However, a good sender reputation, built through consistent sending practices, proper email authentication (SPF, DKIM, DMARC), and good list hygiene, can mitigate this effect. Experts recommend monitoring the reputation of the TLD and the individual domain, and avoiding practices associated with spammers. Established TLDs like .com also experience abuse, and new domains sending high volumes of email are at risk regardless of the extension.
12 marketer opinions
The impact of new or uncommon domain extensions (gTLDs) on email deliverability is indirect but present. While not the primary factor, these extensions can influence deliverability through sender reputation. Spam filters may scrutinize new TLDs more closely due to their potential association with spam or low-quality websites. Building a positive sender reputation, proper email authentication (SPF, DKIM, DMARC), and consistent sending practices are crucial for overcoming any initial disadvantages associated with these domain extensions. Some data suggests certain TLDs have a higher propensity for spam. Established .com domains with poor sending practices are as likely to face deliverability issues as newer or less common extensions.
Marketer view
Email marketer from StackExchange (Webmasters) responds, pointing out that some spam filters assign scores based on various factors, including the domain extension. Less common extensions may start with a slightly higher 'risk' score, but this can be overcome by good sending practices.
4 Jan 2022 - StackExchange (Webmasters)
Marketer view
Email marketer from Mailjet Blog shares that the domain extension *can* indirectly influence deliverability. While not inherently bad, some newer TLDs may be more frequently associated with spam or low-quality websites, impacting sender reputation if not carefully managed. They recommend verifying the TLD's reputation and building a positive sender history.
12 Jun 2025 - Mailjet Blog
5 expert opinions
The expert opinions suggest that while domain extensions themselves are not the sole determinant of email deliverability, they can contribute to the overall reputation and trust assigned to a sender. Some ISPs might exhibit bias against 'weird' or less common TLDs due to concerns about compliance and abuse. High abuse levels are not limited to new TLDs; established domains like .com, .net, and .org also experience significant spam activity. The sender's reputation, influenced by sending practices and the TLD's historical association with spam, plays a vital role. Both new and established domains sending high volumes of email without a proven positive reputation are at risk of being flagged as spam. Continuous monitoring of domain reputation is recommended, along with careful domain selection.
Expert view
Expert from Email Geeks explains that .com, .net and .org also have high abuse levels
14 Mar 2024 - Email Geeks
Expert view
Expert from Email Geeks explains that some ISPs and filtering companies may block "weird" TLDs due to a bias against commercial TLDs. This bias is because the companies running them prioritize profit and lack effective compliance, and may engage in practices like offering large numbers of free domains with purchases.
10 May 2022 - Email Geeks
3 technical articles
The documentation sources highlight that, technically, email protocols do not discriminate against specific domain extensions. RFCs dictate that email systems rely on DNS for routing, treating all validly registered domains equally. However, practical guides from Google Workspace and Microsoft Docs emphasize email authentication (SPF, DKIM, DMARC), list hygiene, and sender reputation as critical for deliverability. These factors outweigh the impact of the domain extension, suggesting that proper configuration and responsible sending behavior are more important for reaching the inbox.
Technical article
Documentation from Google Workspace Admin Help shares that, although not explicitly mentioned, it strongly emphasizes proper email authentication (SPF, DKIM, DMARC) and maintaining a good sender reputation. This implies that the technical configuration and sending behavior outweigh the impact of the domain extension itself.
20 May 2022 - Google Workspace Admin Help
Technical article
Documentation from RFC-Editor.org, explains that the technical specifications governing email (SMTP, RFC 5321) don't explicitly discriminate against specific domain extensions. Email systems rely on DNS to resolve domain names and that all validly registered domain names should function technically the same for email routing.
21 Jul 2021 - RFC-Editor.org
Are there deliverability issues sending from new .us domains to Gmail?
Do different TLDs affect cold email deliverability?
Do I need to re-warm up my IP when changing domain extension?
Does the top level domain (TLD) affect email deliverability?
How do top-level domains (TLDs) impact email deliverability and spam filtering?
What are the risks of using newer TLDs like .clinic or .vet for email sending domains?
What TLDs should be avoided for email domains due to spam or reputation issues?