How to Add Custom Domain on Gumroad, Create Easily 2026
By Impran M NLast checked against official docs
Gumroad hosts your storefront at yourname.gumroad.com by default, but you can point a domain you already own at it instead. The setting inside Gumroad is a single field under Settings, Advanced.
Getting it to verify depends on DNS records you add somewhere else entirely, at whatever registrar sold you the domain, and that's where most setups stall. This guide gives the exact record values Gumroad's own documentation specifies for a root domain, a www subdomain, and a custom subdomain, plus what to check when Verify keeps failing after the records look right.
Before you start
- A domain name already registered somewhere other than Gumroad, since Gumroad doesn't sell domains
- Access to that registrar's DNS settings, where the new record gets added
01Find the Custom domain field
In your Gumroad account, open Settings and click into the Advanced tab. Custom domain isn't under Profile or Payments, which is where most people look first.
It sits near the top of Advanced, above unrelated developer options like email blocklists and API applications: a single Domain field with a Verify button beside it. Gumroad supports two separate setups.
A domain entered here, in the profile-level Advanced settings, points your entire storefront at that domain. You can instead open one product's edit page and enter a domain in its own Custom domain field, which routes only that product's page and leaves the rest of your profile on the default gumroad.com address.

02Add the matching DNS record at your registrar
Before Verify will pass, add a record at wherever you registered the domain, not inside Gumroad. The exact record depends on how you want the domain to look.
For www.example.com, add a CNAME record with host www pointing to domains.gumroad.com, plus a second record, a URL redirect from the bare @ host to https://www.example.com, so visitors who leave off the www still land on your store. For a bare root domain like example.com with no www, add a CNAME on the @ host pointing to domains.gumroad.com.
For a subdomain such as store.example.com, add a CNAME on the store host pointing to the same target. In every case the value is the literal text domains.gumroad.com, not yourusername.gumroad.com.
Typing your own Gumroad subdomain there instead is a common mistake, and it won't verify. A few registrars ask for an IP address instead of a CNAME target; Gumroad publishes 34.198.93.169 for that case.
03Verify, then save
Back in the Custom domain field, type the domain exactly as you configured it in DNS and click Verify. If the domain is behind Cloudflare, turn off the orange proxy cloud on the record first and set it to DNS only; Gumroad can't verify through a Cloudflare proxy.
Once Verify succeeds, click the pink Update settings button. Verifying and saving are two different actions, and stopping after the first is a common reason a domain looks connected but never goes live.
04Give DNS time to propagate
A record that fails Verify a few minutes after you add it isn't necessarily wrong. DNS changes can take anywhere from a few minutes to 24-48 hours to spread, depending on your registrar and the record's TTL. Editing the record again every time a check fails restarts that clock, so waiting an hour before retrying is usually faster than repeated changes.
05Load the domain to confirm it's live
Open the domain directly in a browser, in a private or incognito window so a cached DNS lookup can't give you a false result. It should load your storefront exactly as it appears at the default gumroad.com address.
Your original gumroad.com link keeps working afterward. Adding a custom domain doesn't replace or redirect it, so anything you've already shared under the old link still resolves.
| Domain looks like | Host to edit | Record type | Value |
|---|---|---|---|
| www.example.com | www | CNAME | domains.gumroad.com |
| example.com (no www) | @ | CNAME | domains.gumroad.com |
| store.example.com | store | CNAME | domains.gumroad.com |
The bare @ host also needs a URL redirect to https://www.example.com if visitors who leave off the www should still reach the site. Values from Gumroad's official documentation, checked September 2026.
When it doesn't work
Verify keeps failing even though the DNS record looks correct
Why: The domain is proxied through Cloudflare (the orange cloud icon), and Gumroad can't read DNS records behind a proxy.
Fix: Switch the record to DNS only in Cloudflare (grey cloud), then click Update settings again on Gumroad's Advanced page.
The CNAME record was added but the domain still won't verify
Why: The CNAME target was set to a personal Gumroad subdomain, like yourusername.gumroad.com, instead of the fixed value domains.gumroad.com that Gumroad expects.
Fix: Edit the record so the value reads exactly domains.gumroad.com, then wait for propagation before verifying again.
www.example.com works but example.com without the www doesn't
Why: A root domain needs its own record. The www CNAME only covers requests that include www.
Fix: Add a second record on the @ host, either a CNAME to domains.gumroad.com or a URL redirect to https://www.example.com, matching what Gumroad's documentation specifies for root domains.
My registrar's DNS form won't accept a CNAME value, only an IP address
Why: Some registrars restrict certain host records to A records.
Fix: Use the IP address Gumroad publishes for this case, 34.198.93.169, instead of the CNAME target.
Frequently asked questions
Do I need to buy a domain through Gumroad?
No. Gumroad doesn't sell domains. Buy one from any registrar, then connect it from Settings, Advanced.
Where exactly does the custom domain setting live?
Settings, Advanced tab, in the Custom domain section near the top, above the unrelated developer settings further down the page.
How long does verification take?
Gumroad's own check usually runs in seconds once you click Verify. What takes longer is DNS propagation beforehand, which Gumroad estimates at up to 24-48 hours after you first add the record.
Why does Verify keep failing?
The two most common reasons: the domain is proxied through Cloudflare, which blocks Gumroad from reading the record, or the CNAME target was typed as a personal gumroad.com subdomain instead of the fixed value domains.gumroad.com.
Can I connect a domain to just one product instead of my whole profile?
Yes. Product pages have their own Custom domain field on the edit page, separate from the profile-level one in Settings, Advanced.
Will my old gumroad.com link stop working once I connect a custom domain?
No. Both addresses stay live and show the same content, so links you've already shared under the gumroad.com URL keep working.
Sources and last check
Re-checked against Gumroad's official help article on custom domains in September 2026. That check supplied the exact CNAME values for root, www, and subdomain setups (the earlier draft described the DNS step only in general terms), added the profile-versus-product distinction, the IP-address fallback, and the Cloudflare proxy issue, none of which the previous version mentioned.
About the author

Impran M N
I've been hooked on technology for as long as I can remember — especially the new tools and AI apps that seem to land every other week. Easy Tech Tuts is where I write up whatever I've just worked out: I do the task in the real product, record the screen, and turn it into the guide I wish I'd found first.



