OpenSender.email
Documentation

Sending domains, explained.

A From domain must be authorized in OpenSender and in every provider that sends it. This page covers DNS, multi-provider routing and troubleshooting.

Provider data verified 2026-11-21 API v1 SMTP smtp.opensender.email

Sending domains and provider authorization

OpenSender is a delivery gateway, not the final sender. A From domain such as abc.com has to be authorized at two independent layers before a message can be sent through a provider account.

LayerWhat it provesWhere to configure it
Provider verificationThis provider account may send as abc.com.Resend, SendGrid, Bird, Mailtrap, SendFox, Postmark, Mailgun or the provider dashboard.
OpenSender Sending DomainThis OpenSender tenant may use abc.com as a From domain.Dashboard → Settings → Sending Domains
Recipient authenticationSPF, DKIM and DMARC pass at the receiving mailbox.Your DNS provider, using the records supplied by the email provider.
Both layers are required. OpenSender cannot bypass a provider's domain authorization, and provider verification does not automatically authorize the domain inside OpenSender.
What happens with multiple providers

If abc.com is routed through Resend, SendGrid and Bird, each provider used for that domain must verify abc.com. You do not need to verify providers that are excluded from the route. When provider bindings have been imported, OpenSender only uses providers whose binding is verified for that From domain.

From domainProviderProvider verifiedResult
abc.comResendYesEligible for routing
abc.comSendGridYesEligible for routing
abc.comBirdNoSkipped or rejected until verified
Do I need a second set of OpenSender DNS records?

No. OpenSender verifies the SPF, DKIM and DMARC records that already exist in DNS for the domain. It does not add a second DKIM signature. With multiple providers, publish each provider's DKIM selector and add its required SPF include to the same domain.

SPF:    one TXT record with all required includes
DKIM:   one TXT or CNAME per provider selector
DMARC:  one policy at _dmarc

Example selectors:
resend._domainkey.abc.com
s1._domainkey.abc.com
brevo1._domainkey.abc.com
bird1._domainkey.abc.com
IPv6 and reverse DNS

Email authentication also depends on reverse DNS. The PTR for the connecting IP should match the SMTP HELO/EHLO hostname. If your VPS provider cannot set IPv6 rDNS, do not publish an AAAA record for the submission host and configure the MTA to use IPv4 only. A valid IPv4 PTR is better than an IPv6 address with no PTR.

Why does send-test return sender_domain_not_allowed?

The From domain is not active in OpenSender. Add the exact domain under Settings → Sending Domains, publish the provider's DNS records, and click Verify. The domain becomes active when SPF and DKIM are verified. The domain match is exact: verifying abc.com does not authorize mail.abc.com.

Can I test with test@send.opensender.email?

Not for testing your own provider API key. Your Resend, SendGrid, Bird or Mailtrap account must also authorize that From domain. OpenSender-owned test senders only test OpenSender's own delivery path, not a customer's provider credentials. Use a domain verified in both OpenSender and the selected provider.

Use a domain verified on both sides. Add the domain to the provider first, copy its DNS records, then add the same domain in OpenSender and verify it. Exact DNS values are account-specific and always come from the provider dashboard.