Once your site is published, the next step is usually to put it on the domain you own. RebelSites supports any domain you have registered anywhere, with HTTPS handled automatically. There are two paths through the setup, and both are designed to take just a couple of minutes.
You need a published site (so there is a project to connect a domain to) and a domain registered at any registrar like GoDaddy, Namecheap, Google Domains, Cloudflare, and so on. You do not need any DNS knowledge. The flow handles the records for you in most cases.
Open your project, click the Domains section in the toolbar, and enter the domain you want to use. You can enter just the apex like yourbusiness.com, or a subdomain like www.yourbusiness.com. RebelSites treats the apex and www variants as a pair, so connecting one configures both, and visits to the apex automatically redirect to the www version for consistency.
For most registrars, RebelSites uses a one-click integration that signs you into your registrar in a popup and writes the DNS records for you. You confirm the change and the records are in place within seconds. After that, the only waiting is for DNS to propagate (usually a few minutes, sometimes longer) and for the HTTPS certificate to be issued, which happens automatically.
If your registrar is not on the supported list, the connect flow shows you the exact records to add, including a CNAME for www, A and AAAA records at the apex, and a TXT record for ownership verification. Copy the values into your registrar's DNS settings, save them, and the site usually becomes live within a few minutes. Both records are required for the apex to work properly, so do not skip the TXT record even though it looks unrelated.
If your domain's nameservers are on Cloudflare, the flow automatically takes a slightly different path under the hood, using a redirect bridge for the apex and standard records for www. From your perspective the connect experience is the same. You enter the domain, follow the prompts, and you are done.
HTTPS is provisioned automatically once DNS is in place. There is nothing to configure on your side. Both www and apex traffic land on a valid certificate, and certificate renewals continue automatically for as long as the domain is connected.
If the site does not appear right away, the most common cause is DNS propagation. Wait ten minutes and try again from a fresh browser tab or an incognito window. If you still see the old site (or a different site you used to host on the domain), your local DNS cache or your ISP's cache may be stale. Restarting your machine usually clears it. If something is still not working after that, the Domains section in your project shows the current verification status for both hostnames and surfaces any errors so you know exactly what is pending.
