Skip to content
DMARC Pulse
Guides

Bluehost

Bluehost DMARC: how to add DMARC, SPF and DKIM step by step

Set up Bluehost DMARC in the Portal DNS tab, with the SPF and DKIM values for cPanel Email, Professional Email and Google Workspace.

How to set up DMARC on Bluehost

To set up Bluehost DMARC, first check _dmarc on your domain's DNS tab in the Bluehost Portal. Preserve any valid existing policy. Only if none exists, add a TXT record starting with p=none. Check SPF and DKIM for the mail service that actually sends for your domain.

Existing DMARC policy: authenticating Bluehost does not require resetting it. Keep one _dmarc record, preserve p, subdomain and alignment settings, and merge any needed rua address with existing destinations. The p=none example below is only for a new deployment without a valid record.

Bluehost is a web host that sells more than one email product, and each product gets its records from a different place.

Find out which mail service you use

  • cPanel Email is the mailbox built into Bluehost hosting. Its SPF, DKIM and DMARC values are generated per server and per domain, and you read them in Email Deliverability.
  • Professional Email is Bluehost's paid service powered by Titan. You get its DKIM record from the Email Reputation page.
  • Google Workspace generates its DKIM key in the Google Admin Console. Bluehost says it does not add SPF, DMARC or DKIM for you, even when it configured your MX records. See the Google Workspace guide for Google's side.

Check two things before you edit anything:

  1. Your nameservers. The steps below assume your domain uses Bluehost nameservers. If it points somewhere else, add each record at that DNS provider.
  2. Email Routing in cPanel. On Bluehost nameservers, this setting must match your mail service. Choose Local Mail Exchanger for cPanel Email and Remote Mail Exchanger for Professional Email or Google Workspace.

Careful here. Keep MX records from one email provider active at a time. Bluehost warns that mixing them can cause unpredictable routing and lost messages. Save a copy of your current DNS records before you change them.

Set up SPF

SPF (Sender Policy Framework) lists the servers allowed to send mail for your domain. Bluehost adds a default SPF record to each domain's zone, so you will usually edit a record instead of creating one.

For cPanel Email, use the value shown in Email Deliverability, because Bluehost generates it per server. Its SPF article gives this example for shared and cloud hosting:

TXT
v=spf1 a mx include:websitewelcome.com ~all

For Professional Email, Bluehost documents this value:

TXT
v=spf1 include:spf.titan.email ~all

For Google Workspace, it documents this one:

TXT
v=spf1 include:_spf.google.com ~all
  1. In the Bluehost Portal, click Domains in the left menu and select your domain.
  2. Click the DNS tab.
  3. Under TXT records, look for a record whose value starts with v=spf1.
  4. If you find one, edit it. Keep every service that still sends mail for your domain.
  5. If there is none, click + ADD RECORD and choose Single record. Set Type to TXT, Refers to to @, and paste the value into TXT Value. Click ADD.

Publish a single SPF record. Two records that start with v=spf1 make receivers return permerror. Bluehost's SPF article has you delete the default record before you add a new one. Editing it avoids any gap.

Count the DNS lookups. SPF allows 10. On 9 November 2026, include:websitewelcome.com cost 8 lookups by itself, so Bluehost's example with a and mx reached exactly 10. Add include:spf.titan.email or a marketing tool to that record and it goes over the limit, and receivers can return permerror. These counts change when Bluehost edits its records, so run the SPF checker after each edit.

If you go over, remove services you stopped using. When your website sends through the Bluehost server and your mailboxes live elsewhere, you can send the website's mail through your mailbox provider, as the WP Mail SMTP guide explains. Remove the Bluehost entries only after no mail leaves that server.

Skip Bluehost's strict example. Its article offers v=spf1 a mx ptr include:Bluehost.com -all. On the same date, include:Bluehost.com alone cost 15 lookups, and RFC 7208 says ptr should not be published.

Bluehost's SPF article describes ?all as the default configuration, which states no policy for unlisted servers. Use ~all while you collect reports. Move to -all only after your reports show every legitimate sender in the record.

Set up DKIM

DKIM (DomainKeys Identified Mail) adds a signature to each message, and receivers check it against a public key in your DNS. On Bluehost the key sits under your own domain, so the signature carries your domain in d=. That is what lets DKIM align with your From address for DMARC.

Bluehost does not publish a fixed selector for cPanel Email. cPanel's API documentation checks default._domainkey, so expect default, and let the Name in your panel decide. Professional Email generates a selector per domain, and Bluehost gives titan1._domainkey as an example.

DKIM for cPanel Email

  1. In the Bluehost Portal, click Hosting, select My Plans and click the cPanel button.
  2. In the Email section, open Email Deliverability and click Manage next to the domain.
  3. Under DKIM, copy Name and Value from Suggested DKIM (TXT) Record. Publish them at the authoritative DNS provider and verify the result. Review any automatic installation proposal before applying it.
  4. In the Portal, click Domains and open the DNS tab. Look for a TXT record whose host matches the Name you copied. If one exists, edit it and replace its value, because a selector must hold only one DKIM record. If there is none, click + Add Record and select Single Record.
  5. Set Record Type to TXT and Refers to to Other Host. Paste the Name into Host Name and the Value into TXT Value, then click Add.

DKIM for Professional Email

  1. In the Portal, click the Email tab. If several plans are listed, click Manage on the one you want.
  2. Open Email Reputation and click Add beside Add DKIM record.
  3. Copy the DNS Host Name and TXT Record Value.
  4. On your domain's DNS tab, add a Single record of type TXT. Paste the host name into Refers to and the value into TXT Value, then click Add.
  5. Return to Email Reputation, confirm you added the record and click Verify changes. DKIM Record should show VERIFIED.

DKIM for Google Workspace

Generate the key in the Google Admin Console. On the DNS tab, add a TXT record with Refers to set to Other Host, enter google._domainkey, and paste Google's value. Then return to the Admin Console and click Start authentication.

Add the DMARC record

DMARC tells receivers how to treat mail that fails and where to send reports. A message passes when SPF or DKIM passes and aligns with the From domain, so one aligned result is enough. Set up both anyway.

  1. On your domain's DNS tab, look for a TXT record with the host _dmarc.
  2. If one exists, edit that record. Receivers discard every DMARC record when a name holds more than one.
  3. If there is none, click Add Record and set Type to TXT.
  4. Set Refers to to Other Host and enter _dmarc.
  5. For a new record only, paste the starter value below into TXT Value with your reporting address. For an existing record, preserve its current policy and merge only the needed report address, then save:

New policy only: use this starter value only when no valid DMARC record exists. For an existing record, keep its policy and merge the report address instead of pasting over the value.

TXT
v=DMARC1; p=none; rua=mailto:dmarc@example.com

With p=none, the policy requests no enforcement for a DMARC failure; receivers can still apply other filtering. The rua tag asks receivers to send aggregate reports, so replace the address with one you monitor. If you use DMARC Pulse, enter your DMARC Pulse reporting address. If you start from the value suggested in Email Deliverability, confirm it has a rua tag.

One Bluehost article suggests adding pct=10 through pct=50 during the quarantine phase. RFC 9989 removed pct, so leave it out.

Confirm it worked, then tighten the policy

Bluehost says individual DNS changes can take up to 8 hours, and its Professional Email article allows 24 to 48 hours. When they are live, check the DKIM checker with the selector from your panel.

Send a message to an outside mailbox and paste its headers into the email header analyzer. You want spf=pass, dkim=pass and dmarc=pass. SPF counts toward DMARC only when the domain in smtp.mailfrom aligns with your From domain.

Preserve existing policy during authentication. For a new policy, start at p=none and collect representative reports, which may take months. After fixing all legitimate streams, consider p=quarantine and observe reports again. Evaluate p=reject separately: it is optional, needs aligned DKIM rather than SPF alone, and RFC 9989 §7.4 advises against it when users post to mailing lists. Forwarding and list transformations need testing; receiving servers decide the final disposition.

Before p=reject, confirm DKIM on every mail stream. RFC 9989 says a domain publishing p=reject must not rely on SPF alone. A policy set too early can make receivers refuse your real mail.

Common problems

  • A checker cannot see your record. Confirm your domain uses Bluehost nameservers. If it does not, the record belongs at the provider your nameservers point to.
  • The banner Problems Exist (DKIM) stays visible. It means DKIM is not set up for that domain yet. Bluehost says the status updates on its own, and that can take up to 8 hours after you add the record.
  • Professional Email DKIM will not verify. Bluehost lists four causes: the record is missing, the value has a typo, more than one DKIM record exists for the host name, or the domain uses other nameservers. Use the Copy buttons and keep one record.
  • SPF returns permerror. Look for two v=spf1 records, often left over from a previous provider, and for a lookup count above 10.
  • Reports do not arrive. Confirm the record has rua. If the address is on another domain, that domain must publish a TXT record such as example.com._report._dmarc.example.net, or receivers ignore the address. See DMARC reports not arriving.
  • Mail goes to the old provider after a switch. Remove the old MX records and confirm Email Routing in cPanel matches the new service.
  • Messages stop sending after a burst. Bluehost lists "Maximum emails per hour have been exceeded" as a cause. The default for cPanel Email is 200 per hour, and this limit has nothing to do with DMARC.

Frequently asked questions

Does Bluehost add a DMARC record automatically?
Bluehost's Google Workspace guide says it does not add SPF, DMARC or DKIM for you. For cPanel Email, Bluehost tells you to review the suggested records in Email Deliverability, and for Professional Email it lists DMARC as an optional record that you publish. Look for a TXT record on the host _dmarc in your DNS tab to see what your domain has.
What is the Bluehost SPF include?
For its shared and cloud hosting, Bluehost documents include:websitewelcome.com. Professional Email uses include:spf.titan.email, and Google Workspace uses include:_spf.google.com. For cPanel Email, Bluehost says the value is generated per server, so copy it from Email Deliverability.
What DKIM selector does Bluehost use?
Bluehost does not publish a fixed selector for cPanel Email. cPanel's API documentation checks default._domainkey, so default is what to expect, but the Name field in Email Deliverability decides. Professional Email generates the selector per domain, with titan1._domainkey as Bluehost's example. Google Workspace uses google._domainkey in Bluehost's guide.
Should I click Install the Suggested Record in Bluehost?
That cPanel button can publish the suggested record when the server controls authoritative DNS. Review the suggestion first; otherwise copy Name and Value to your actual DNS host and verify there. Do not assume a saved local record is public.
Should I add pct to my Bluehost DMARC record?
No. A Bluehost article suggests pct=10 through pct=50 during the quarantine phase, but RFC 9989 removed the pct tag because receivers applied partial values inconsistently. Change the p value in one step when your reports are clean.
Where do I add DMARC if my domain uses another DNS provider?
Add it at the provider your nameservers point to. Bluehost's instructions for the DNS tab apply only to domains on Bluehost nameservers.

Sources consulted

RFC 6376 §3.6.2.1 Namespace
checked 2026-11-09

Keep it healthy

Know the moment something breaks

Point your DMARC reports to DMARC Pulse and see who sends email as your domain, what fails and why — with a calm alert when anything changes.

Free plan: 1 domain, no credit card.