How do you add email DNS records in Bluehost?

Bluehost is a web host first, so its DNS comes with email defaults already in place: an MX record pointing at your own domain, an SPF record built for its servers, and a cPanel setting that decides whether mail for your domain is delivered locally. Those defaults are why moving email off Bluehost can look done in DNS while some mail still lands in the old mailbox.

This guide covers adding MX, SPF, DKIM and DMARC records in Bluehost, using Bluehost's own help articles for each step, plus the Email Routing setting most guides skip. Screen names are correct at the time of writing (October 2026). If you need a refresher on the records themselves, read SPF vs DKIM vs DMARC.

Does your domain use Bluehost's DNS?

Bluehost DNS records only take effect when the domain uses Bluehost's nameservers. Bluehost's zone editor article says you can manage records for domains "pointed here (using our nameservers)" (Bluehost). If your domain uses Cloudflare or another DNS host, add the records there instead, for example with our Cloudflare guide. Our MX Lookup shows the live nameservers and MX records.

Where do you add DNS records in Bluehost?

Bluehost has two editors for the same zone: the Bluehost Portal (Account Manager) and cPanel's Zone Editor. Bluehost's email articles use the Portal (Bluehost):

1. Sign in to the Bluehost Portal.
2. Select Domains in the left-hand menu, then select your domain.
3. Open the DNS tab and choose Manage Advanced DNS Records.
4. Select + Add record, then Single record.
5. Fill in the fields and save.

To edit or delete an existing record, use the vertical ellipsis (three dots) next to it. Actions > Export downloads your zone as a text file, which is worth doing before you change anything.

Bluehost's articles label the fields slightly differently depending on the record:

For reference, Bluehost's own default MX and SPF records use a TTL of 14400 seconds (4 hours), and its Google Workspace example uses 3600 (Bluehost). If you plan to move MX, lowering the TTL a day ahead helps; our DNS TTL guide explains why.

What email records does Bluehost create by default?

On Bluehost nameservers, Bluehost publishes email records for you. Its email services article says "When a domain uses Bluehost nameservers, mail is handled locally by default" (Bluehost).

How do you add or replace the SPF record in Bluehost?

SPF is a TXT record on @. Bluehost "automatically adds one to your zone file for each domain," and explains that "?all is the default configuration because we're unsure if you'll utilize your domain name" (Bluehost). A ?all ending makes no claim about other servers, so it does little against spoofing; see SPF softfail vs hardfail.

A domain must have only one SPF record. RFC 7208, section 3.2 says a domain "MUST NOT have multiple records" that an SPF check would select. Bluehost adds that "The default SPF record must be deleted from your cPanel before installing a new one."

1. Find the existing TXT record on @ that starts with v=spf1. Note its value.
2. Delete it, or edit it if you still send from your Bluehost server and only need to add an include.
3. Select + Add record, choose TXT, set Refers to @, and paste the new record as the TXT Value.
4. Save.

Example for a domain that moved mail to Google Workspace and no longer sends from the web server (example value): v=spf1 include:_spf.google.com ~all. If your website's contact form still sends mail directly from Bluehost, keep a or mx terms that cover it, or better, send form mail through your mail provider. Our SPF provider pages list each provider's include, and the SPF Record Generator merges them.

How do you add a DKIM record in Bluehost?

A DKIM record publishes the public key receivers use to check your mail's signature. Your email provider generates it, and you publish it as a TXT record, or as CNAME records if the provider hosts the key.

DKIM for mail sent from Bluehost's cPanel

Bluehost's DKIM article starts in cPanel:

1. Open cPanel, go to Email > Email Deliverability, and select Manage next to the domain. A "Problems Exist (DKIM)" notice means DKIM isn't set up.
2. Copy the Name and Value of the Suggested DKIM (TXT) Record. Bluehost's article says not to select Install the Suggested Record.
3. In the Portal, select + Add record, choose TXT, set Refers to to Other Host, enter the name as the Host Name and paste the value as the TXT Value.
4. Select Add.

Bluehost says DKIM changes usually work "within a few minutes but may take up to 8 hours to complete."

DKIM for Google Workspace, Microsoft 365 and other providers

The steps are the same, using the host and value your provider shows: a TXT record such as google._domainkey for Google Workspace, or CNAME records such as selector1._domainkey for Microsoft 365. Bluehost doesn't document how it handles very long TXT values, so after saving a 2048-bit key, check that the published key is complete; our 2048-bit DKIM key guide explains what to look for. Then turn on signing in your provider's console, as shown in DKIM setup for Microsoft 365 and Google Workspace.

How do you add a DMARC record in Bluehost?

DMARC is a TXT record at _dmarc. Bluehost's template uses the same values (Bluehost):

1. Select + Add record and choose TXT.
2. Set Refers to to Other Host and enter _dmarc as the Host Name.
3. Enter the policy as the TXT Value, for example v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com.
4. Save.

Keep one record at _dmarc. Start with p=none and a reporting address you read, then tighten the policy as reports show every sender passing. The DMARC Record Generator builds the record, and our none-to-reject guide covers the rollout.

How do you change MX records in Bluehost?

Bluehost's rule is simple: "Only one email provider's MX records should be active for a domain at a time" (Bluehost). A move takes two steps: change MX in DNS, then change Email Routing in cPanel.

Step 1: replace the MX records

From Bluehost's MX article:

1. Export the zone or note the current MX records so you can roll back.
2. Select + Add record and choose MX.
3. Enter @ as the Host Record. Bluehost says, "In most cases, you need to type the @ symbol."
4. Enter the mail server hostname in Points To. It must be a hostname, not an IP address.
5. Enter the Priority your provider gives, leave TTL at the default, and save.
6. Delete the old Bluehost MX record that points to your own domain.

For Google Workspace, Bluehost lists either smtp.google.com at priority 1 or the older five ASPMX records, and warns "Do not mix the two." For Microsoft 365, use the MX value shown in the Microsoft 365 admin center for your domain.

Step 2: set Email Routing in cPanel

This is the Bluehost quirk. Outside senders follow your new MX records, but with Local Mail Exchanger set, cPanel says "the server will always accept mail for the domain" and delivers it to the local mailbox (cPanel), so mail that starts on the Bluehost server, such as your website's form notifications, goes to the old Bluehost mailbox. Bluehost says the "matching Email Routing setting in cPanel must also be confirmed" after an MX change.

1. Log in to cPanel and select MX Entry or Email Routing (Bluehost).
2. Select your domain.
3. Choose Remote Mail Exchanger if mail is hosted elsewhere, or Local Mail Exchanger if you use Bluehost's cPanel email. Bluehost says to use Automatically Detect Configuration "with caution after a provider switch."
4. Select Change.

Do this last. Bluehost's Google Workspace troubleshooting article explains that editing MX records "can cause these settings to be reset," so "It's important this step is performed last." For the wider plan, read how to change MX records without losing email.

How do you check the records after saving?

Bluehost says DNS records can take "a few minutes" but up to 8 hours, and its MX article allows up to 48 hours. Then check:

1. MX with our MX Lookup: only your new provider's hosts should appear.
2. SPF with the SPF Checker: exactly one record, no ?all, 10 lookups or fewer.
3. DKIM with the DKIM Checker and your selector.
4. DMARC with the DMARC Checker.
5. Submit your website's contact form and send a message from another account, and confirm both reach the new mailbox. If the form's message lands in cPanel webmail, Email Routing is still local.

Open a test message's headers and look for spf=pass, dkim=pass and dmarc=pass; our header guide shows where.

What are the common Bluehost email DNS mistakes?

• Email Routing left on Local Mail Exchanger after moving to Google Workspace or Microsoft 365.
• Two SPF records: Bluehost's default plus a new one.
• Leaving ?all on the default SPF record.
• Keeping the old MX record that points to your own domain next to the new provider's MX.
• Editing Bluehost DNS while the nameservers point elsewhere.
• Website form mail failing SPF after the move, because the server no longer appears in the record. See website form emails going to spam.

Next steps

1. Export your Bluehost zone before you start, so you can roll back.
2. Run the Email Health Check after the change to see MX, SPF, DKIM and DMARC together.
3. Replace the default SPF record using the SPF Record Generator.
4. Agencies managing many client sites on Bluehost can find a per-domain approach on our web agencies page.

If you point MX at a filtering service such as iBlockSpam, the same two steps apply: new MX values, then Remote Mail Exchanger. Our pricing page shows the per-domain plans. More walk-throughs are in setup guides.