Registering a domain doesn't automatically make a website appear. Registration just reserves the name for you at the registry. The domain won't load anything in a browser until it's pointed at a server that actually has a website on it, and that pointing takes a little time to spread across the internet. If you just registered and got a "server not found" or a placeholder page, that's expected, not broken.
Here's what has to happen, in order.
1. Point the domain at hosting
A freshly registered domain has no idea where your site lives yet. You need to connect it to hosting, either by pointing its nameservers at ours, or by adding hosting-specific DNS records if it's staying with another DNS provider.
- If you also host with us: go to Services, open your hosting service, and add the domain (as the primary domain if it's a new account, or as an Addon Domain if you're adding it to existing hosting).
- If your domain is registered with us but hosted elsewhere: go to Domains, open the domain, and update the nameservers on the DNS subpage (up to 5). Note that this only changes nameservers, not individual records. Editing actual DNS records (A, CNAME, MX, TXT) for hosting on our platform happens under Services → your hosting → DNS Zone Editor, not on the domain's DNS page.
- If you're pointing the domain at a third-party platform like Shopify or Wix instead of traditional hosting, see pointing your domain or subdomain to Shopify, Wix, and other services for the record types those platforms expect.
2. Wait for DNS to propagate
This can take anywhere from a few minutes to several hours, occasionally longer, depending on the resolvers involved. The full mechanics, including how to flush your local DNS cache so you're not staring at a stale copy, are covered in how long does DNS propagation take.
A common source of confusion here: your phone might show the new site while your laptop still shows nothing, or shows the registrar's placeholder page. That's normal during propagation. Different devices hit different resolvers with different cache states. It isn't a sign anything is misconfigured.
3. Check that SSL has issued
Once DNS actually resolves to your hosting, we auto-issue a free Let's Encrypt SSL certificate, typically within about 5 minutes of DNS pointing correctly, and it renews itself after that. If you visit the domain right after DNS resolves and get a certificate warning instead of a working site, that's usually just this step still catching up. Give it a few more minutes before assuming something's wrong.
4. Confirm there's actually a site to show
If DNS is correct and SSL is issued but you still see a blank page or a default placeholder, check whether there's a site installed at all. A brand-new hosting account with nothing uploaded, or a WordPress install that hasn't been completed, will show a placeholder instead of an error. If you're migrating an existing site from another host rather than building fresh, our team can move it for you at no charge; that's typically a 2 to 5 business day process and your old site stays live during the move.
Quick troubleshooting order
- Confirm the domain is actually assigned to your hosting under Services, or that nameservers were changed under Domains → DNS.
- Flush your local DNS cache and try again, or check a propagation tool to see if the change has spread yet.
- Try the domain on a different network (mobile data instead of wifi) to rule out a stale local cache.
- Check for a certificate warning specifically. That's a different symptom than a blank page and usually just means SSL hasn't caught up yet.
- If you're replacing an old domain and want the old one to forward here instead of running its own site, that's a separate setup. See domain forwarding and redirects.
When to contact support
If it's been a while and the domain still isn't resolving to your hosting, open a ticket from Support in the portal. A real person will check the zone and your hosting assignment directly rather than have you guess from outside. If you're moving this domain away from us later, see transferring a domain away from Flashcloud. This is also the right move if you transferred the domain in recently and aren't sure whether DNS carried over correctly.