Overview
If your guest-facing website is showing as offline, the cause is almost always one of four things: the publish toggle is off, the wrong domain is set as primary, the domain expired at your registrar, or the DNS records at your registrar are misconfigured. Work through the steps below in order — the first two are inside Amenitiz, the rest happen at your domain registrar.
Before you start
If the site was working yesterday and broke overnight, the most likely cause is your domain expiration — check this first at your registrar.
DNS changes can take up to 48 hours to propagate worldwide. During that window the site may still appear offline even if everything is configured correctly.
Your SSL certificate is managed automatically by Amenitiz — you don't renew or configure it yourself. If you see an SSL warning that doesn't resolve on its own, contact support.
Step 1 — Check the website is set to online
In the sidebar, go to
Website→Website.Find the Online / Offline toggle near the top of the page. Make sure it's set to Online.
Step 2 — Check the correct domain is set as primary
Go to
Website→Domain name.Under Choose your primary domain, confirm that your custom domain (
www.yourdomain.com) is selected — not the Amenitiz subdomain.Save changes if you had to switch.
Step 3 — Check your domain hasn't expired
Log in to the registrar where you bought your domain (GoDaddy, OVH, Namecheap, Google Domains, etc.).
Find the domain's expiration date.
If it has expired, renew it. Some registrars block DNS resolution within hours of expiry — the site won't come back until the renewal is processed and DNS propagates again.
Step 4 — Check your DNS records
In your registrar's DNS settings, your domain needs two records pointing to Amenitiz:
CNAME record for the
wwwhost → points toyour-hotel.amenitiz.io(write it exactly that way — it's the shared Amenitiz hostname, not a placeholder).A record for the root domain (empty host or
@) → points to35.180.238.216.
Also remove any conflicting records — duplicate hostname entries, leftover A records on www, or IPv6 (AAAA) records on the root or www. They override the correct records and break resolution.
Save and allow up to 48 hours for DNS to propagate.
Step 5 (optional) — Use the Amenitiz subdomain as a temporary primary
If your custom domain is still propagating or you need the site live immediately, switch to your Amenitiz subdomain as a workaround:
Go to
Website→Domain name.Under Choose your primary domain, select the option that ends in
.amenitiz.io.Save. Guests can now reach the site at your Amenitiz subdomain.
Once DNS for your custom domain has fully propagated, switch the primary back.
FAQs
How long do DNS changes take to propagate?
How long do DNS changes take to propagate?
Up to 48 hours worldwide, though many networks see changes within a few hours. During propagation some visitors will see the new configuration and others the old one. Use a DNS lookup tool like dnschecker.org to monitor.
Do I need to manage the SSL certificate myself?
Do I need to manage the SSL certificate myself?
No. Amenitiz issues and renews SSL automatically for your custom domain. If you see an SSL warning that doesn't clear within 24 hours of DNS being correct, contact [email protected].
What if the site shows a Cloudflare or CDN error page?
What if the site shows a Cloudflare or CDN error page?
External infrastructure providers occasionally have outages. These resolve automatically once the provider restores service. If the site stays down after the provider's status page reports recovery, contact support.
Can the site be live on both my custom domain and the Amenitiz subdomain at the same time?
Can the site be live on both my custom domain and the Amenitiz subdomain at the same time?
Only one can be the primary domain at a time. The non-primary one redirects to the primary. To switch, go to Website → Domain name and change Choose your primary domain.
I've checked everything and the site is still offline — what now?
I've checked everything and the site is still offline — what now?
Contact [email protected] with: your custom domain, when you first noticed the issue, a screenshot of the error visitors see, and confirmation that you've checked the publish toggle, primary domain, registrar expiry, and DNS records.