Introduction
A custom domain lets you publish your Gamma site on your own web address (for example, yourcompany.com or site.yourcompany.com) instead of the default gamma.site address.
This guide covers everything in one place: connecting your domain, the DNS records to add, verification and SSL, and how to fix the most common issues.
🌀 Insight: Most domains connect within a few minutes. If something isn't working, jump to the Troubleshooting section below — each common issue has its own fix.
How to Connect a Custom Domain
Before You Start
Custom domains are available on Pro plans and above.
Your site's gamma must be in your paid workspace. If it's in a different (for example, Free) workspace, you won't be able to connect a domain.
Each domain can be used by one site in one workspace at a time.
Step 1: Connect Your Domain
Open your site.
Click the three-dot menu (…) in the upper-right corner.
Select Site settings.
Go to Publishing & domains.
Enter your domain under Connect an existing domain, and click Connect.
Choose Automatic Setup (recommended) or Manual Setup, then follow the prompts.
🔷 Note: Enter just the domain, for example yourdomain.com or site.yourdomain.com. Don't add https:// at the start or a dot at the end (yourdomain.com.).
Don't own a domain yet? Click Buy new domain in Publishing & domains to purchase one through Gamma — it's connected to your site automatically. To learn more, check out:
Step 2: Add DNS Records (Manual Setup)
If you chose Manual Setup, add the records below at your DNS host (usually the registrar where you bought your domain).
Root domain (yourdomain.com)
Record type | Name / Host | Value | TTL |
A | @ (root domain) | 3.136.232.26 | 3600 |
A | @ (root domain) | 3.137.108.170 | 3600 |
CNAME | www | sites.gamma.app | 3600 |
@ means your root domain — some registrars label this as your bare domain name or leave the Name/Host field blank. You must add both A records; adding only one is a common cause of domain verification failure.
Subdomain (for example, blog.yourdomain.com)
Record type | Name / Host | Value | TTL |
CNAME | blog (the subdomain part only) | sites.gamma.app | 3600 |
For a subdomain, add just this one CNAME record. Enter only the subdomain part in the Name / Host field (for example, blog, not blog.yourdomain.com). No A records are needed.
🔷 Note: Remove any other A or AAAA records on @ (your root domain) or www — leftover records from a previous host can stop your domain from verifying. Don't change your MX or TXT records; those are used for things like email.
Standalone www-only domains aren't supported. Gamma treats www and your root domain as the same, so you can't connect only www.yourdomain.com. Use a different subdomain instead (for example, site.yourdomain.com), or point your root domain to Gamma using the records above.
Finding your DNS settings: the section has different names depending on your registrar — DNS (GoDaddy), DNS / Records (IONOS), Advanced DNS (Namecheap), DNS → Records (Cloudflare — set records to DNS Only / grey cloud, not Proxied), DNS / Nameservers (Hostinger), Zone Editor (HostGator / cPanel).
Using Cloudflare? Set your Gamma records to DNS Only (grey cloud), not Proxied (orange cloud). For more Cloudflare-specific fixes, check out:
Step 3: Wait for Verification
Verification usually takes a few minutes but can take up to 24 hours. You can check your domain's status in Site settings → Publishing & domains. Once it's verified, click Publish to push your site live on your domain.
Troubleshooting
My Domain Shows Failed or Won't Verify
If your domain shows Failed, or is still pending after 24 hours:
Check and fix your DNS records at your DNS host (see the common causes below).
Open Site settings → Publishing & domains and click FAILED next to the domain to re-run verification. You can also remove the domain and add it again.
Common causes:
A typo in an IP address or the CNAME value. The A records must be exactly 3.136.232.26 and 3.137.108.170, and the CNAME must point exactly to sites.gamma.app with no trailing characters or spaces.
Only one A record. You must add both A records — having only one is a frequent cause of a Failed status.
Leftover A or AAAA records on @ or www from a previous host. Delete them.
A wildcard (*) record on your domain. Remove it so it doesn't conflict with your Gamma records.
Cloudflare proxy is on. Set your Gamma records to DNS Only (grey cloud).
Leftover DNSSEC or DS records from a previous domain registrar. If you recently transferred your domain from another registrar, go to your current registrar's DNS settings, find any DS or DNSSEC entries, and delete them. Then wait up to 24 hours.
💎 Pro Tip: Use a tool like whatsmydns.net to confirm your records have propagated globally. If everything looks correct and the domain still isn't working, let us know — a human agent can check the domain status on our end.
"Your Connection Is Not Private" or SSL Certificate Errors
After your domain verifies, Gamma issues an SSL certificate for it. This can take up to 24 hours. Until it's issued, you may see a temporary security warning such as "Your connection is not private." This applies no matter which DNS host or registrar you use.
While you wait, check that both A-record IPs are entered correctly, and if you use Cloudflare, that your records are set to DNS Only. Clear your browser cache and test in a private/incognito window.
Contact support if:
It's been more than 24 hours since your domain showed as verified and the warning is still there, or
Your domain worked before and now shows a certificate error (for example, ERR_CERT_DATE_INVALID or NET::ERR_CERT_COMMON_NAME_INVALID).
🔷 Note: A certificate error on a domain that used to work needs the Gamma team to fix — removing and re-adding the domain won't resolve it. A human agent can check the SSL certificate status directly.
Placeholder Page, Blank Page, or Wrong Content
If your domain shows a placeholder page ("This space is full of potential"), a blank page, or the wrong content, it's usually caused by a missing homepage setting. The page that appears at your custom domain is whichever page has a blank URL path. To fix it:
Open Site settings.
Go to Page settings and select your homepage (marked with a house icon).
Make sure the URL path field is completely empty.
Click Save.
Go to Publishing & domains and click Publish.
You can also do this from the Pages panel (top-left toggle): hover over the page that should be your homepage, click the three-dot menu (…) → Page setup, and clear the URL path field. Then republish your site.
💎 Pro Tip: If changes you've published don't show up on your domain, republish your site.
I Can't Add Another Domain (Domain Limits)
Every connected domain counts toward your plan's limit, including subdomains and domains that are failed or pending.
Pro and Team: 10 domains per workspace
Ultra, Business and Enterprise: 100 domains per workspace
Domain add-ons aren't available and the limit can't be raised on your current plan. To get more, upgrade to Ultra, Business or Enterprise, or create a second Gamma account for 10 more.
Remove any failed or unused domains to free up space. If you can't remove a domain, contact support.
🔷 Note: If you see "Maximum number of custom domains" but no domains are listed, the site's gamma is usually in a different (often Free) workspace. Make sure the gamma is in your paid workspace.
Move, Remove, or Disconnect a Domain
Move a Domain to Another Site
To move a domain to another site in the same workspace:
Open the new site and go to Site settings → Publishing & domains.
Enter the domain under Connect an existing domain.
Click Transfer domain to this site.
Remove a Domain
Go to Site settings → Publishing & domains.
Remove the custom domain. Your site goes back to its gamma.site address.
🔷 Note: If Remove is greyed out, the domain is set as your preferred domain. Set your gamma.site address as the preferred domain first, then remove the custom domain.
Go Back to Your Old Website
Connecting a custom domain to Gamma changes where your domain points. It doesn't delete the website you had before. Your original site is probably still with your previous host (for example, your domain provider, Squarespace, Wix, or WordPress). Your domain is just sending visitors to Gamma instead. To point it back:
Remove the domain in Gamma. Click the three-dot menu (…) → Site settings… → Publishing & domains, and remove your custom domain.
Remove Gamma's DNS records at your registrar. Delete the two A records (3.136.232.26 and 3.137.108.170) and the www CNAME pointing to sites.gamma.app.
Restore your original host's records. Your previous website host or domain registrar can tell you which records to add back.
Give it time. DNS changes can take up to 24 hours to update.
🔷 Note: Gamma can't change or release your DNS records. Only your DNS host (usually your domain registrar) can do that.
FAQs & Common Issues
Does the Make discoverable toggle affect my domain?
No. The Make discoverable toggle has no effect on domain verification or SSL.
What is ERR_QUIC_PROTOCOL_ERROR and how do I fix it?
This error typically appears after DNS has propagated but while Gamma's SSL certificate is still being provisioned for your domain. It usually resolves on its own once the certificate is issued, which can take up to 24 hours after verification. Try again later, or test in a different browser or an incognito window. If it persists beyond 24 hours after your domain showed as verified in Gamma, let us know — a human agent can take a closer look at the setup.
Will connecting my domain affect my email?
Not if you leave your MX and TXT records as they are. Gamma only needs the A and CNAME records listed above.