Gmail.com sending domain restrictions

When adding a custom email sending domain in BetterUnite, the email platform does not allow gmail.com to be used as a sending domain.

This restriction is common across most Email Service Providers (ESPs), including the platform we utilize. It exists to prevent email spoofing, maintain strong deliverability rates, and protect sender reputation.

To send email through BetterUnite, the sending domain must be verified. Verification requires adding specific DNS records. - such as SPF and DKIM—to the domain’s DNS settings. These records prove that you own the domain and authorize BetterUnite to send email on its behalf.

Because gmail.com is a public domain owned and managed by Google, individual users and third-party services cannot add the required DNS records. As a result, it cannot be verified as a sending domain.

Using Google Workspace Domains

If your organization uses Google Workspace (formerly G Suite) with a custom domain (for example, yourorganization.org), you can still use that domain as a sending domain in BetterUnite.

In this case:

• The domain (yourorganization.org) belongs to your organization.

• You have access to the domain’s DNS settings.

• You can add the required verification records.

The restriction only applies to shared public domains such as:

• gmail.com

• yahoo.com

• outlook.com

To configure a sending domain successfully, use a domain your organization owns and controls.