Connect your domain to SGEN
Your SGEN site has an SGEN-assigned address from day one. To use your own domain (on a paid plan), open the site's DNS settings in SG-Dashboard. SGEN lists two A records to add — your root (@) and www, both pointing at 34.144.203.31. Add them at your registrar, then click Check DNS. DNS propagates in minutes to 48 hours; once it resolves, your site shows DNS configured and SSL active and serves over HTTPS — no nameserver change, no certificate to buy.
Two A records do the work
SGEN lists the records to add: an A record for @ and one for www, both with Value 34.144.203.31. You add them at your registrar — there is no nameserver change.
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. Propagation takes minutes to a few hours, occasionally up to 48 hours.
HTTPS is handled for you
SGEN secures connected domains over HTTPS automatically — there is no certificate to buy or install. Once the domain resolves, the site loads with a padlock.
When to use this guide
Use this guide when you want visitors to reach your SGEN site at your own domain. Common situations:
Pointing a new or existing domain at SGEN
Add two A records and run Check DNS.
Going live from the SGEN-assigned address
Keep building on the assigned URL, then point your domain when you're ready.
Moving a domain in from another platform
The same A-record step, run during a planned cutover.
Not this guide. Email records (MX, SPF, DKIM) stay in your registrar's DNS panel and are not affected by pointing your website records at SGEN. Connecting a custom domain needs a paid plan — a free sandbox site shows "Coming Soon" in its DNS settings.
Before you start
Plan
A paid (live) site
The DNS settings are available on a paid site; a sandbox site shows "Coming Soon."
Domain
A registered, active domain
If you have not registered one, do that first at a registrar.
DNS Access
Access to your registrar's DNS panel
You sign in there to add the records; have credentials ready.
Records
The records SGEN shows
Two A records (@ and www), both pointing at 34.144.203.31. Each has a copy button.
Where to go
In SG-Dashboard, open the site, then go to its DNS settings (from Site Manager → your site, the Point your domain action also lands here). The page has:
Canonical Rules
Force HTTPS (shown as Always On) and a Preferred Domain choice (www vs non-www).
A Record Checker
A Check DNS button that verifies your domain is configured.
DNS Setup Instructions
The two Required A Records, with copy buttons and links to DNS lookup tools.
Steps — connect your domain to SGEN
1
Open your site's DNS settings
In SG-Dashboard, open your site and go to its DNS settings. Note the two Required A Records under DNS Setup Instructions — each has a copy button. Keep this open while you make the change at your registrar.
2
Add the two A records at your registrar
Log in to your registrar and open the DNS records area for your domain. Add both records SGEN lists:
| What you are connecting | Record type | Name / Host | Points to |
|---|---|---|---|
Root domain (yourdomain.com) | A | @ | 34.144.203.31 |
www (www.yourdomain.com) | A | www | 34.144.203.31 |
Name / Host: use the prefix only — @ for the root, www for the www name. TTL: a low value such as 300 seconds during setup lets changes spread quickly; raise it later once stable. If your registrar will not allow an A record on the root, use its ALIAS, ANAME, or CNAME-flattening option on @ — as long as it resolves to 34.144.203.31, it connects.
Save both records. There is no nameserver change — your registrar keeps managing DNS, including any email records, which are unaffected.
3
Run Check DNS
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 — propagation takes minutes to a few hours, occasionally up to 48 hours.
4
Wait for the status, then confirm over HTTPS
Once your records resolve, the site shows DNS configured and SSL active — SGEN secures the domain over HTTPS automatically, so there is no certificate to buy or install.
Under Canonical Rules, pick your Preferred Domain (www or the bare domain). Then open your domain in a private browser window — https://yourdomain.com loads your SGEN site with a padlock in the address bar.
What success looks like
DNS configured / SSL active
The site status reads both.
Loads over HTTPS
https://yourdomain.com resolves to your SGEN site in a private browser window, with a padlock and no security warnings.
Pages reachable on your domain
Published pages are reachable at their full URLs — https://yourdomain.com/about, and so on.
HTTPS renews automatically
You never manually renew a certificate.
What to do if it does not work
Check DNS still reports not-configured after several hours
Confirm you saved the records at your registrar (some require an explicit save). Then look your domain up in a public DNS lookup tool and confirm both @ and www resolve to 34.144.203.31. A wrong or missing value is the most common cause. If correct but still not configured after 24 hours, contact support — some registrar TTL settings extend propagation.
The status is connected but the browser shows "Not secure"
HTTPS settles shortly after DNS resolves. Confirm you are visiting https with the secure prefix, wait a little, and reload in a private window. If it persists once the status reads SSL active, contact support.
www works but the bare domain does not (or vice versa)Confirm BOTH A records are present at your registrar — @ and www, each → 34.144.203.31.
The domain loads an SGEN page that says "No site found"
The domain is resolving to SGEN but is not matched to your site. Confirm you added the records for the correct domain and that you are looking at the right site in SG-Dashboard.
Email stopped working
Pointing your website A records at SGEN does not change email — your MX/SPF/DKIM records stay at your registrar. If email broke, check those records are still present in your registrar's DNS panel; nothing about this step removes them.