Theme

Popular tools

SiteGround Nameservers

SiteGround's nameservers are ns1.siteground.net and ns2.siteground.net. Copy them, then check your domain's zone at SiteGround before you switch.

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

SiteGround's nameservers

One shared setAWS Global Accelerator · AS16509
  1. ns1.siteground.net75.2.77.104
  2. ns2.siteground.net99.83.229.113

One pair for every SiteGround server since its move to centralized DNS; some delegations still show older per-server sgvps.net names. SiteGround's guide

ns1 + ns2.siteground.net

AsksSiteGroundns1 + ns2.siteground.net

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

How to point a domain to SiteGround's nameservers

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

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

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

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

  1. 1At SiteGround

    Move the site's content first, and add records you keep (MX, TXT) in Services → Domains.

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

  2. 2At the domain's registrar

    Replace the nameservers at your registrar with ns1 and ns2.siteground.net.

  3. 3The wait: the .com registry

    Keep the old host running for about 72 hours while the change propagates.

    SiteGround says72 hr
    .com referral TTL2 days

    “It takes roughly 72 hours until the changes in your domain's records propagate.”

Bars: SiteGround'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 SiteGround?

Ask one of SiteGround's nameservers directly, with recursion off: a domain it holds comes back with the aa flag and its own SOA; one it doesn't hold gets REFUSED.

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

What SiteGround's servers answereddig +norec +tcp · October 24, 2026
A zone it holdsyouradchoices.comThe zone
$ dig @ns1.siteground.net youradchoices.com SOA +norec +tcp
;; status: NOERROR · flags: qr aa
youradchoices.com. 86400 IN SOA ns1.siteground.net. root.c66082.sgvps.net. 100194 …
A domain it doesn't holdzq7x3k9p2m-dnsrobot-test…No zone
$ dig @ns1.siteground.net zq7x3k9p2m-dnsrobot-test-20261024.com SOA +norec +tcp
;; status: REFUSED · flags: qr (no aa)
;; ANSWER: 0, AUTHORITY: 0    ; NSID: dns-auth-singapore-1

How each host says “no zone”

Recorded with dig over TCP, recursion off, on October 24, 2026.

What are SiteGround's MX records?

SiteGround mail uses mx10.antispam.mailspamprotection.com (priority 10), mx20.antispam.mailspamprotection.com (priority 20), and mx30.antispam.mailspamprotection.com (priority 30) as its MX records, and _spf.mailspamprotection.com as its SPF include.

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 copySiteGround's help pages · October 24, 2026
SiteGround mailIf it's missing
MX10 mx10.antispam.mailspamprotection.com20 mx20.antispam.mailspamprotection.com30 mx30.antispam.mailspamprotection.comIf it's missing: mail can't reach the mailboxes
TXTinclude:_spf.mailspamprotection.comAdd it to the domain's SPF record; the rest of the record is your own.If it's missing: its mail fails SPF checks

www.siteground.com

How to check if a website is hosted on SiteGround

Look at the site's address, not its nameservers: SiteGround's websites run on Google Cloud (AS15169, AS396982), while its nameservers answer from AWS Global Accelerator (AS16509).

So a domain can use SiteGround'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: youradchoices.comTeam Cymru · October 24, 2026
youradchoices.com
NS
Nameserversns1 + ns2.siteground.netAS16509 AWS Global Accelerator
A
Website35.212.33.193AS15169 Google LLCon Google Cloud, where SiteGround's servers run

SiteGround runs on Google Cloud

SiteGround has no network of its own: its websites sit in Google Cloud's address space, shared with every other customer there.

AS15169AS396982
  • Address—
  • NS*.siteground.net/com
  • CNAME—
  • Headersx-proxy-cache-info · host-header
  • Check a site at SiteGroundHosting Checker
Routing data from RIPEstat, September 25, 2026; signals from the Hosting Checker's registry.

SiteGround nameservers: FAQ

What are SiteGround's nameservers?

SiteGround's nameservers are ns1.siteground.net and ns2.siteground.net. Point a domain there at its registrar, after adding the domain to your SiteGround account, then check the zone on this page before you switch. One pair for every SiteGround server since its move to centralized DNS; some delegations still show older per-server sgvps.net names.

How do I change my nameservers to SiteGround?

Move the site's content first, and add records you keep (MX, TXT) in Services → Domains. Replace the nameservers at your registrar with ns1 and ns2.siteground.net. Keep the old host running for about 72 hours while the change propagates. Then check the zone with the tool on this page before you switch.

How long does a nameserver change to SiteGround take?

SiteGround says up to 72 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 SiteGround's DNS without its hosting?

Not as a separate service. Its DNS Zone Editor covers domains registered with SiteGround and domains used for websites in your SiteGround account, once they point to its nameservers. So point the nameservers to SiteGround only once the domain is added to your plan, then check the zone on this page before you switch.

Does SiteGround support DNSSEC?

Not on its nameservers: a domain that uses SiteGround's DNS can't be signed. Turn DNSSEC off at the registrar before you point the domain to SiteGround, or validating resolvers will reject every answer. SiteGround's knowledge base says DNSSEC records can't be added for domains registered with it, and zones on its nameservers are unsigned.

What are SiteGround's MX records?

SiteGround mail uses mx10.antispam.mailspamprotection.com (priority 10), mx20.antispam.mailspamprotection.com (priority 20), and mx30.antispam.mailspamprotection.com (priority 30), with the SPF include _spf.mailspamprotection.com. They belong in the zone wherever the domain's DNS is hosted, so add them at the new host before you move the nameservers away from SiteGround, or mail stops reaching the mailboxes.

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

Not necessarily: nameservers say where the DNS is, not the website. SiteGround's nameservers answer from AWS Global Accelerator (AS16509), while its web servers are on Google Cloud (AS15169, AS396982). Look up the site's address, or run the Hosting Checker, which matches the address, nameservers, CNAME and headers.

Where does SiteGround show a site's nameservers?

In the Client Area, open Websites, then the site's menu, Website Settings and Server Details: the box shows the site's IP address and its name servers, NS 1 and NS 2. They are ns1 and ns2.siteground.net for every site, since SiteGround moved all its servers to one centralized pair of nameservers.

Can I keep my DNS elsewhere and still host on SiteGround?

Yes. Instead of changing the nameservers, you can update only the domain's A record to point to your hosting account's IP address, shown under Server Details. Your DNS and email stay where they are, but SiteGround then can't manage those records for you. Changing the nameservers instead moves every record and your email management to SiteGround.

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. SiteGroundthis pagens1 + ns2.siteground.net9
  7. DreamHostns1–3.dreamhost.com6
  8. HostGatornsN · cnsN.hostgator.comA pair per hosting plan4
  9. Bluehostns1 + 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