Theme

Popular tools

Bluehost Nameservers

Bluehost's nameservers are ns1.bluehost.com and ns2.bluehost.com. Copy them, then check your domain's zone at Bluehost before you switch.

Bluehost's own help pages · its nameservers asked directly · no log kept

Bluehost's nameservers

One shared setCloudflare · AS13335
  1. ns1.bluehost.com162.159.24.80
  2. ns2.bluehost.com162.159.25.175

One pair for every account, sent in the order email and shown in the Bluehost Portal under Domains → Nameservers. Bluehost's guide

ns1 + ns2.bluehost.com

AsksBluehostns1 + ns2.bluehost.comGlobalping

No domain at hand? Try , a site at Bluehost.

How to point a domain to Bluehost's nameservers

Add the domain to your Bluehost account first, then change the nameservers at the domain's registrar to ns1 + ns2.bluehost.com. Nothing is copied in the switch.

Your visitors keep reaching the old host until resolvers follow the new delegation.

Leaving Bluehost? Add every record at the new host first, then change the nameservers, and keep Bluehost's zone answering for the .com referral's 2 days.

The switch, in three placesBluehost's help pages · October 24, 2026

  1. 1At Bluehost

    Add the domain (Domains → ADD A DOMAIN) and connect it to your Bluehost plan.

    Nothing is copied when the nameservers change: the zone at Bluehost starts with what you add.

  2. 2At the domain's registrar

    Change the nameservers at the registrar: Bluehost can't change them for an external domain.

  3. 3The wait: the .com registry

    Wait 24 to 48 hours, then edit the DNS records in the Bluehost Portal.

    Bluehost says24 hr–48 hr
    .com referral TTL2 days

    “Nameserver changes typically take 24-48 hours to propagate globally.”

Bars: Bluehost's own figure, and the NS TTL the .com registry gave out when we asked on October 24, 2026.

Is my domain's DNS at Bluehost?

Ask Bluehost's nameservers directly, with recursion off: a domain they hold comes back with the aa flag and its own SOA. A name they don't hold gets aa too, from a catch-all whose SOA belongs to the TLD.

The check above does this at every Bluehost server for your domain, then compares each record with what Google and Cloudflare hand out.

What Bluehost's servers answereddig +norec +tcp · October 24, 2026
A zone it holdspaint.netThe zone
$ dig @ns1.bluehost.com paint.net SOA +norec +tcp
;; status: NOERROR · flags: qr aa
paint.net. 86400 IN SOA ns1.bluehost.com. root.box2545.bluehost.com. 2026101100 …
A domain it doesn't holdzq7x3k9p2m-dnsrobot-test…No zone
$ dig @ns1.bluehost.com zq7x3k9p2m-dnsrobot-test-20261024.com SOA +norec +tcp
;; status: NOERROR · flags: qr aa
com. 300 IN SOA a.gtld-servers.net. abuse.bluehost.com. 2009091600 …
↳ catch-all: the SOA belongs to com., not the name

How each host says “no zone”

Recorded with dig over TCP, recursion off, on October 24, 2026. Bluehost's servers are on Cloudflare's network, so the check above asks them through a Globalping probe.

What are Bluehost's MX records?

Bluehost's cPanel mail has no shared MX host: the MX points at your-domain, priority 0, and its SPF include is websitewelcome.com.

They sit in the zone wherever the domain's DNS is hosted: change the nameservers without them and mail stops. What breaks in a move

The records to copyBluehost's help pages · October 24, 2026
cPanel mailIf it's missing
MX0 your-domainYour own name: the highlighted part is your domain.If it's missing: mail can't reach the mailboxes
TXTv=spf1 a mx include:websitewelcome.com ~allIf it's missing: its mail fails SPF checks

www.bluehost.com

How to check if a website is hosted on Bluehost

Look at the site's address, not its nameservers: Bluehost's websites run on AS46606, while its nameservers answer from Cloudflare (AS13335).

So a domain can use Bluehost's DNS and be hosted elsewhere, or the other way round. The Hosting Checker reads the address, nameservers, CNAME and headers together.

One domain, two networks: paint.netTeam Cymru · October 24, 2026
paint.net
NS
Nameserversns1 + ns2.bluehost.comAS13335 Cloudflare
A
Website50.87.184.106AS46606 Unified Layerin Bluehost's network

Bluehost's address spaceRIPEstat · September 25, 2026

AS46606UNIFIEDLAYER-AS-1

Unified Layer · ARIN · since 2008

797,952

IPv4 addresses · 259 prefixes
162.214.0.0/15162.240.0.0/1550.87.0.0/16
  • AddressAS46606
  • NS*.bluehost.com
  • CNAME—
  • Headershost-header
  • Check a site at BluehostHosting Checker
Routing data from RIPEstat, September 25, 2026; signals from the Hosting Checker's registry.

Bluehost nameservers: FAQ

What are Bluehost's nameservers?

Bluehost's nameservers are ns1.bluehost.com and ns2.bluehost.com. Point a domain there at its registrar, after adding the domain to your Bluehost account, then check the zone on this page before you switch. One pair for every account, sent in the order email and shown in the Bluehost Portal under Domains → Nameservers.

How do I change my nameservers to Bluehost?

Add the domain (Domains → ADD A DOMAIN) and connect it to your Bluehost plan. Change the nameservers at the registrar: Bluehost can't change them for an external domain. Wait 24 to 48 hours, then edit the DNS records in the Bluehost Portal. Then check the zone with the tool on this page before you switch.

How long does a nameserver change to Bluehost take?

Bluehost says 24 hours to 48 hours. The real bound is the registry's NS TTL: the .com registry hands out a delegation for 2 days, so some resolvers keep asking the old nameservers that long. Keep the old host's zone answering until then, and compare both zones before deleting anything.

Can I use Bluehost's DNS without its hosting?

Not as a separate service. Bluehost edits an external domain's DNS once it resolves to ns1 and ns2.bluehost.com, and connecting a site to it needs a hosting plan. So point the nameservers to Bluehost only once the domain is added to your plan, then check the zone on this page before you switch.

Does Bluehost support DNSSEC?

Only in some cases. The Bluehost Portal has a DNSSEC toggle under Domains → DNS for supported extensions; turn it off before moving the nameservers away. Where it isn't offered, turn DNSSEC off at the registrar before you point the domain to Bluehost, or validating resolvers will reject every answer.

What are Bluehost's MX records?

Bluehost's cPanel mail points MX at the domain's own mail host on your server, with the SPF include v=spf1 a mx include:websitewelcome.com ~all. They belong in the zone wherever the domain's DNS is hosted, so add them at the new host before you move the nameservers, or mail stops reaching the mailboxes.

Is a site hosted on Bluehost if it uses Bluehost's nameservers?

Not necessarily: nameservers say where the DNS is, not the website. Bluehost's nameservers answer from Cloudflare (AS13335), while its web servers are on AS46606. Look up the site's address, or run the Hosting Checker, which matches the address, nameservers, CNAME and headers.

Why is Bluehost checked through Globalping?

Bluehost's nameservers are on Cloudflare's network (AS13335), and our checks run on Cloudflare Workers, which can't open a DNS connection to it. So your browser asks a Globalping probe to send the query, recursion off, and the result names the probe's city and network. An authoritative answer is the same whoever asks.

Why does Bluehost answer for a domain it doesn't host?

Bluehost's nameservers run a catch-all: asked for a name they hold no zone for, they still answer with the aa flag, and the SOA in the reply belongs to the top-level domain, such as com., not to the name. So an aa flag alone proves nothing at Bluehost: the SOA's owner has to be the domain itself, which is what the check on this page tests.

Which SPF include does Bluehost mail use?

Bluehost says mail from its Portal accounts leaves through websitewelcome.com, so the SPF record should include websitewelcome.com rather than a brand name, for example v=spf1 a mx include:websitewelcome.com ~all. The same include serves HostGator, another Newfold Digital host. Its MX is the domain itself at priority 0, created automatically on Bluehost's nameservers.

Other hosts' nameservers

The 13 hosts this check asks, by how many of 4,000 sampled websites use their nameservers.

Sites on each host's nameservers4,000 sites, Tranco ranks 20,001–600,000
  1. GoDaddynsNN.domaincontrol.comA pair per account140
  2. Namecheapdns1 + dns2.registrar-servers.comSeveral sets43
  3. OVHcloudnsNN + dnsNN.ovh.netA pair per domain27
  4. Hostingername.dns-parking.comA pair per site19
  5. IONOSns1ZZZ.ui-dns.de / .biz / .org / .comA set of four per domain16
  6. SiteGroundns1 + ns2.siteground.net9
  7. DreamHostns1–3.dreamhost.com6
  8. HostGatornsN · cnsN.hostgator.comA pair per hosting plan4
  9. Bluehostthis pagens1 + ns2.bluehost.com3
  10. Hosting.comns1–4.stableserver.net3
  11. 20ins1–4.stackdns.com2
  12. Squarespaceconnect1 + connect2.squarespacedns.comSeveral sets2
  13. WixnsN.wixdns.netA pair per account1
Nameservers read through 1.1.1.1 for 4,000 random sites of the Tranco list; each row opens that host's page.

Missing something?Suggest a feature or a new tool

Related tools