Set up a custom domain for your site
A custom domain replaces your site's default address with a name you own. Open your site's DNS settings in SG-Dashboard, add the two A records SGEN lists — @ and www, both pointing at 34.144.203.31 — at your registrar, then click Check DNS. Once they resolve (up to 48 hours), your site shows DNS configured and SSL active, and serves on your domain over HTTPS. You need a paid site and access to your domain's DNS records before you start.
Two A records do the work
SGEN lists exactly what to add: an A record for @ and one for www, both with Value 34.144.203.31. You add them at your registrar — nothing is uploaded to SGEN.
Check DNS confirms it
Click Check DNS in the A Record Checker and SGEN verifies your domain. Once your records resolve, the site shows DNS configured and SSL active. DNS changes can take up to 48 hours to propagate.
HTTPS is handled for you
Force HTTPS is Always On, and SGEN secures connected domains. There is no certificate to buy or install — once the domain resolves, the site loads with a padlock.
What this page covers
A custom domain is the public name of your site. Setting one up replaces the default address your site was given when it was created with a name your audience knows you by. This page covers the everyday path: add the two DNS records SGEN gives you, run the built-in check, and confirm the site serves over HTTPS. It also covers moving a domain in from another platform — the same DNS step, run during a planned cutover.
It does not cover registering a domain — that happens at a registrar, outside SGEN. It does not cover email — connecting your website records does not change your mail setup.
Sandbox note. Custom domains connect on a paid (live) site. A free sandbox site shows "Coming Soon" in its DNS settings — sandbox sites run on their SGEN address and do not take a custom domain. Move the site to a paid plan first.
How a custom domain works
A custom domain works entirely through DNS — the internet's address book. You do not upload anything to SGEN; you add two records at your registrar that tell the internet your domain now lives at SGEN's address. From then on, every visit to your name is routed to your SGEN site and secured over HTTPS.
A visitor opens your domain
They type example.com or www.example.com in the address bar.
DNS looks up your A records
The @ and www records you added return 34.144.203.31 — SGEN's address.
SGEN matches the domain to your site
The request reaches the SGEN site that has this domain connected.
Your site loads over HTTPS
Force HTTPS is Always On, so the connection is secured automatically — no certificate to buy.
Knowing this order helps when something looks wrong: if the site does not load, the fix is almost always in the DNS records, not in SGEN. The records point your name at 34.144.203.31; everything after that is handled for you.
Before you start
Confirm these items before you open the DNS settings.
Plan
A paid (live) site
Custom-domain DNS is available on a paid site; a sandbox site shows "Coming Soon."
DNS Access
Access to your DNS records
You can sign in and edit DNS records for the domain at your registrar or DNS host.
Access
Site-admin access
You are signed in with admin access to the SGEN site you are putting the domain on.
Records
The records SGEN lists
A records on @ and www, both pointing at 34.144.203.31.
For a move-in. DNS changes can take up to 48 hours to spread. Plan the change for quiet hours so visitors are not caught mid-switch.
Where to find it
In SG-Dashboard, open the site and go to its DNS settings. The page shows Canonical Rules (Force HTTPS "Always On" plus a Preferred Domain choice), an A Record Checker with a Check DNS button, and DNS Setup Instructions listing the Required A Records with copy buttons.
Record 1 — root
Type A · Name @ · Value 34.144.203.31
Record 2 — www
Type A · Name www · Value 34.144.203.31
Check DNS
The A Record Checker button that verifies your domain once the records are in place. DNS changes may take up to 48 hours to propagate.
Step 1 — Add the A records at your registrar
Open your site's DNS settings and note the two Required A Records under DNS Setup Instructions — @ and www, both → 34.144.203.31. Then sign in to your DNS provider, open the DNS records area for the domain, and add them.
| Connecting | Record type | Name / Host | Points to |
|---|---|---|---|
Root domain (example.com) | A | @ | 34.144.203.31 |
www (www.example.com) | A | www | 34.144.203.31 |
- Name / Host: the prefix only —
@for the root,wwwfor the www name. Some providers append the rest of the domain for you; others want the full name. - TTL: a low value such as 300 seconds during setup lets changes spread quickly. Raise it later once the domain is stable.
If your provider does not allow an A record on the root, use its ALIAS, ANAME, or CNAME-flattening option on @ instead — as long as it resolves to 34.144.203.31, the check passes.
For a move-in from another platform. Add the SGEN records but do not remove the old host's records until Check DNS passes and the site serves on SGEN. Both can resolve during the switch; retire the old records only once SGEN is serving.
Where the DNS records area lives in common providers:
Cloudflare
Dashboard → domain → DNS → Records
Namecheap
Domain list → Manage → Advanced DNS
GoDaddy
My Products → DNS → Manage Zones
Google Domains / Squarespace DNS
DNS → Custom records
AWS Route 53
Hosted zones → select zone → Create record
Step 2 — Run the DNS check
Back on the DNS settings page, in A Record Checker, click Check DNS. SGEN verifies your domain and confirms whether it is correctly configured. If the records have not spread yet, give it time and click Check DNS again — DNS changes can take up to 48 hours to propagate, though they often complete much sooner.
DNS configured
Your domain resolves to SGEN.
SSL active
Served over HTTPS — no certificate to buy.
Step 3 — Set your preferred domain and confirm over HTTPS
Under Canonical Rules, pick your Preferred Domain (www or the bare domain). Force HTTPS is Always On, so traffic is secured automatically.
With the status reading DNS configured and SSL active, open the domain in a fresh browser tab. The site loads on your domain with a padlock. If the padlock does not appear within a short while of the status turning green, wait a little and reload. If it persists, contact support — certificate setup is handled by SGEN.
Registrar walkthroughs
Every registrar keeps DNS records in a slightly different place, but the two records you add are always the same — an A record on @ and an A record on www, both pointing at 34.144.203.31.
Cloudflare
Open DNS → Records. Add an A record with Name @ and IPv4 34.144.203.31; set Proxy status to DNS only (grey cloud) during setup. Repeat for www. Cloudflare also accepts a pasted zone file via Advanced → Import DNS records.
Namecheap
From Domain List → Manage → Advanced DNS, under Host Records add an A Record with Host @ and Value 34.144.203.31, then a second with Host www. Remove Namecheap's default parking records (URL redirect on @ or a CNAME on www) first.
GoDaddy
Open My Products → DNS → Manage Zones. Add an A record with Name @ and Value 34.144.203.31, then one with Name www. GoDaddy usually ships a default A on @ pointing at a parking page — edit that record rather than adding a duplicate.
Google Domains / Squarespace DNS
Open DNS → Custom records. Add an A record with Host @ and data 34.144.203.31, then one with Host www. Remove any default synthetic or forwarding records that answer for @ or www.
If your provider is not listed, the pattern is identical everywhere: find the DNS (or Advanced DNS) area, add two A records — @ and www — point both at 34.144.203.31, and save.
Moving a domain in from another platform
Moving a live domain is the same DNS step as a first launch, run during a planned cutover. The goal is a switch your visitors never notice: they keep typing the same name, and the site behind it changes from the old host to SGEN. Because both hosts can answer during the switch, there is no window where the domain goes dark.
Plan the cutover
Finish and review the SGEN site on its default address first. Lower the old @ and www records' TTL to 300 a day ahead so caches let go quickly. Pick a low-traffic window.
At cutover
Copy the two Required A Records from the DNS settings page. Change the existing @ and www A records from the old host's address to 34.144.203.31. Do not delete anything else yet. Click Check DNS and re-run it as the change spreads.
After cutover
Retire the old host's records only after SGEN is serving and Check DNS has passed. Leave mail records (MX, SPF, DKIM) untouched. Raise the TTL back up once the domain has been stable for a day or two.
Move-in pitfalls. If the domain still opens the old site, a cache is holding the old value — wait out the previous TTL and re-run Check DNS. If email stopped, a mail record (MX / SPF / DKIM) was removed by mistake; website records do not touch email — restore them. If only one name switched, you changed
@ but not www (or the reverse) — point both at 34.144.203.31.What success looks like
Check DNS passes
The A Record Checker confirms the domain is configured.
DNS configured / SSL active
The site status shows both, and the domain opens your SGEN site over HTTPS with a padlock.
Correct domain
The domain opens your SGEN site rather than the default address.
Old host retired
For a move-in, traffic now reaches SGEN rather than the old host.
What to do if it does not work
| Symptom | Likely cause | Fix |
|---|---|---|
| Check DNS reports not-configured after adding the records | DNS not propagated yet, or a wrong value | Wait (up to 48 hours, often less) and re-run Check DNS; confirm in a public DNS lookup tool that @ and www resolve to 34.144.203.31 |
| Records resolve to the wrong address | A leftover record from a previous host, or the wrong value entered | Confirm both A records point at 34.144.203.31; delete stale records; save and re-check |
| Check DNS passes but the browser shows "Not secure" | HTTPS still settling after DNS resolved | Wait a little and reload in a fresh tab; if it persists once the status reads SSL active, contact support (certificates are handled by SGEN) |
| Root will not accept an A record | Provider does not allow A on the apex | Use the provider's ALIAS / ANAME / CNAME-flattening on @ so it resolves to 34.144.203.31 |
| Cloudflare shows the records but Check DNS still fails | The record is proxied (orange cloud), so the check sees Cloudflare's address | Set the record to DNS only (grey cloud) until Check DNS passes and the status reads SSL active |
| A moved-in domain is slow to switch over | A high TTL on the old records keeps caches serving the previous host | Wait out the TTL window; nothing needs re-entering once the records are correct |
Common questions about custom domains
Does adding a custom domain cost extra?
The domain itself is billed by your registrar. Custom-domain connection is part of a paid site; check your plan settings in SG-Dashboard for the exact policy.
Do I need to buy an SSL certificate?
No. SGEN secures connected domains over HTTPS and shows SSL active once the certificate is in place — there is nothing to buy or install.
Why does my sandbox site say "Coming Soon"?
Sandbox sites run on their SGEN address and do not take a custom domain. Move the site to a paid plan to connect your own domain.
Can I choose www or the bare domain?
Yes — set it under Canonical Rules → Preferred Domain on the DNS settings page. Point both names at SGEN so either resolves.
Can I attach the same domain to two different SGEN sites?
No. A domain points at one SGEN site at a time. For separate sections, use a subdomain on its own site.
How long does the full setup take?
DNS changes can take up to 48 hours to propagate, but a registrar that propagates quickly often connects within minutes to an hour. A high previous TTL on the old records can extend the window.
Do I need both the root and www records?
Point both so either name resolves, then choose which one visitors see under Canonical Rules → Preferred Domain. If you add only one, the other name will not load.
Does my old SGEN default address keep working?
Yes. The default address your site was created with continues to resolve. With a Preferred Domain set, visitors are guided to your custom domain, which becomes the name shown in the address bar.
Reference — record summary
Whatever your situation, the value is always 34.144.203.31.
| Connecting | Record type | Name / Host | Value |
|---|---|---|---|
| Root domain | A | @ | 34.144.203.31 |
| www | A | www | 34.144.203.31 |
Root, where an A record on @ is not allowed | ALIAS / ANAME / CNAME-flattening | @ | resolves to 34.144.203.31 |
| A subdomain on its own SGEN site | A | <subdomain> | 34.144.203.31 |
- TTL:
300seconds during setup; raise it once stable. - Force HTTPS: Always On — nothing to configure.
- Preferred Domain: choose
wwwor the bare domain under Canonical Rules.