Custom domains & DNS
Connect a custom hostname, verify DNS ownership, and provision HTTPS for your StaticWeb project.
Your included deployment address
Your published project gets an address such as my-site-a7k2m9.staticweb.space. DNS and HTTPS are set up automatically. You do not need to add DNS records for this address, and it does not count toward your custom-domain allowance.
Project cards show address and HTTPS setup progress. The live link appears when it is ready. Renaming a project does not change its assigned address. You can also connect a domain you own.
Add a hostname
Open Domains, choose a project, and enter the hostname you own, such as www.example.com. Your plan limits the number of custom domains across your account. Credits do not increase the domain limit.
Prove ownership
The portal provides a TXT verification record and your project’s CDN target. Copy the exact names and values shown. At your DNS provider, create the TXT record and point your hostname to the CDN target with a CNAME.
For root domains, use an ALIAS/ANAME or CNAME flattening if your DNS provider supports it. Otherwise use www with a CNAME and configure a root-to-www redirect at your DNS provider. Use the exact target shown in your project, not the staticweb.site website address.
Verify and enable HTTPS
Click Check DNS & HTTPS after saving your DNS records. Changes can take time to propagate. HTTPS is set up automatically once ownership and routing are confirmed. Keep these DNS records in place while using the domain.
Check for conflicting records and restrictive CAA records if certificate provisioning fails. Contact support with the hostname and the exact portal error.