263 Enterprise Mail: MX, SPF, DKIM & DMARC Setup
Configure 263 Enterprise Mail on a custom domain: mxw.263.net at priority 5, mx.263.net at 10, the spf.263.net include, DKIM generated in the admin console, and DMARC reporting.
Aliyun Mail & DirectMail: DKIM, SPF & DMARC Setup
Step-by-step Aliyun DirectMail sender domain verification: the six DNS records, the SPF include values, region-based DKIM selectors and DMARC publishing.
Alibaba Mail (Alimail) SPF, DKIM & DMARC Setup Guide
Configure Alibaba Mail / Aliyun Enterprise Mail on your own domain: mx1-mx3.qiye.aliyun.com, the spf.qiye.aliyun.com include, default._domainkey DKIM and a DMARC record.
HubSpot Email Authentication: DKIM, SPF & DMARC
HubSpot sends your marketing email from its own infrastructure, which means that without domain authentication your messages are signed by hubspot.com rather than by your domain. Receivers show a "via hubspot.com" hint next to your From address, and DMARC never passes because the signing domain does not align with your From domain. Since Gmail, Yahoo and Microsoft made SPF, DKIM and DMARC mandatory for bulk senders, an unauthenticated HubSpot domain is a direct deliverability problem, not a cosmetic one.
The fix is HubSpot's connected email sending domain: one wizard generates every record you need — DKIM, SPF, DMARC and an MX for bounces — so HubSpot signs and sends as your domain. This guide walks through the connection and how to verify it.
What you need
- A HubSpot account with domain settings permissions. Only users with that permission, usually Super Admins, can connect sending domains.
- Access to your DNS provider. You will publish records in the zone of the domain you send from.
- A From address domain that is free for sending. HubSpot requires the sending domain to not serve your website at the same time; a dedicated subdomain such as mail.yourdomain.com works well and is the recommended pattern.
- A list of other services that already send as your domain, so you can merge HubSpot into your existing SPF record instead of creating a second one.
Configuration steps
- In HubSpot, click the settings icon in the top navigation, then navigate to Content > Domains & URLs (in older accounts this appears as Website > Domains & URLs).
- Click the Email Sending tab, then click Connect sending domain.
- Enter a From email address you actually use for marketing sends (for example, newsletter@yourdomain.com), confirm the domain, and choose to set the records up manually with your DNS provider.
- HubSpot generates the DNS records for authentication. The DKIM records are two CNAMEs using the hs1 and hs2 selectors, and the SPF record is a TXT record that includes your portal ID:
CNAME hs1._domainkey -> <unique value>.dkim.hubspotemail.net
CNAME hs2._domainkey -> <unique value>.dkim.hubspotemail.net
TXT @ -> v=spf1 include:123456.spf03.hubspotemail.net -all
The wizard also generates an MX record for bounce handling on the sending domain and a DMARC TXT record. Always copy the exact hostnames and values from your own wizard — the include value contains your portal ID and the CNAME targets are account-specific.
- Publish the records at your DNS provider. If you already have an SPF record, do not create a second one — merge HubSpot's include into the existing record:
v=spf1 include:_spf.google.com include:123456.spf03.hubspotemail.net -all
- Return to HubSpot and click Verify. DNS changes usually take 10–70 minutes to become visible, up to 48 hours in rare cases. Each sending domain then shows one of three statuses: Not authenticated, Partially authenticated (DKIM verified, SPF or DMARC pending) or Authenticated.
If you use Cloudflare for DNS, turn off the proxy (orange cloud) for these records and disable domain-wide CNAME flattening for the zone while authenticating, otherwise verification fails.
Verify
Send a test email from HubSpot to a Gmail inbox and open Show original. You want to see SPF pass, DKIM pass with d=yourdomain.com, and DMARC pass — alignment now works because the From domain, the DKIM signing domain and the SPF envelope all use your domain.
Check each record directly with the SPF Checker, the DKIM Checker (selector hs1) and the DMARC Lookup, or review everything at once with the Email Health Check. If you are new to the underlying protocols, start with the email authentication fundamentals guide.
Common mistakes
- Publishing a second SPF record. Two v=spf1 TXT records on one domain cause a permanent SPF failure for every sender. Merge includes into one record.
- Letting the DNS provider append your domain to the host. Some providers turn hs1._domainkey into hs1._domainkey.yourdomain.com.yourdomain.com, causing a DNS error and endless pending verification. Enter the host exactly as HubSpot shows it.
- Sending from a domain you never connected. If your From address is on a subdomain that was not authenticated, DMARC fails no matter how good your root records are. The From domain must match the connected sending domain.
- Using the website's root domain as the sending domain. HubSpot does not allow connecting a domain that hosts your website content. Use a subdomain instead.
- Skipping DMARC monitoring. If other services also send as your domain, publish DMARC with p=none first and read the reports with the DMARC Report Analyzer before enforcing.
Frequently asked questions
Do I need both hs1 and hs2 DKIM records?
Yes. HubSpot publishes two selectors so it can rotate keys and fail over without breaking signing. Publishing only one leaves your mail unsigned whenever the other selector is used.
Can I connect a subdomain instead of my root domain?
Yes, and it is the recommended setup. Connect mail.yourdomain.com and send from newsletter@mail.yourdomain.com. DMARC policies published at the root domain are inherited by subdomains, so you only manage one DMARC record.
Does this affect one-to-one sales emails sent from HubSpot?
No. Email sent through a connected Gmail or Outlook inbox in the CRM travels through your own mailbox and is authenticated by your provider. This guide covers marketing email sent by HubSpot's infrastructure.
Why does my SPF include value look different from a tutorial?
The SPF include HubSpot generates contains your portal ID (for example 123456.spf03.hubspotemail.net), so it is unique per account. Always copy it from your own wizard.
Related Tools
Need Help?
Our tools are designed to be intuitive, but if you need assistance, we're here to help.
About Our Tools
Professional-grade email and DNS diagnostic tools trusted by IT professionals worldwide.
