If your Hostinger AI Builder website is unavailable, shows a placeholder, or does not display recent edits, first identify what visitors actually see. Then check the domain connection, publication status, account status, browser or network, and any recent editor or custom-code changes. Hostinger’s current manual-mode guides describe these as separate possible causes; no single fix applies to every site.
Start by identifying the symptom
Check the live site in a private or incognito browser window, and if possible on another device or network. Note whether the site is unavailable for everyone, only one browser or network, or whether it loads but shows an old version or a placeholder. Record any exact error, such as 403 Forbidden or an SSL warning. That distinction helps you choose the right checks below.
As an Amazon Associate I earn from qualifying purchases.
Check the domain and its connection to the website
- Confirm the domain’s owner contact details are valid, and make sure the domain is connected to the intended Hostinger website.
- Check that the domain points to Hostinger. If you recently changed its pointing, that change may be involved; Hostinger’s guide does not specify a universal waiting period.
- If the domain is registered with another provider, check whether DNSSEC is enabled there. Hostinger’s manual-mode guide identifies DNSSEC as a possible issue for externally registered domains; it says this check does not apply to domains registered at Hostinger.
DNS pointing and DNSSEC are different checks: verify both only when relevant to your domain setup. If you need background on checking DNS records, Hostinger explains the nslookup command and how to use it.
Make sure the site is published and visible
In the AI Builder, confirm the website has been published. If visitors see a placeholder rather than your site, check whether Coming Soon mode is enabled. After changing publication or visibility settings, publish the website again so the live site reflects the change.
If a store product is missing
Check that the website has a product section, then verify that the product is marked Active and saved. Publish the site again after making changes. A product that is inactive or not saved may not appear on the live site.
Check the domain and hosting plan status
Verify that neither the domain nor the hosting plan has expired. An expired service is one of the possible causes Hostinger lists for a site that is not working. If either has expired, follow the renewal or account instructions shown in your Hostinger account.
Use the exact browser error to choose the next check
403 Forbidden
Note the full error and check the domain connection, publication status, and account status above. The error alone does not establish which of those applies.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
SSL or “Not Secure” warning
Confirm that the website is published. Hostinger associates ERR_SSL_PROTOCOL_ERROR with an SSL certificate that is not installed or is not working properly, but that explanation should not be assumed to cover every SSL warning. For general guidance, see Hostinger’s article on fixing “Not Secure” or “Not Private” connection errors.
Rule out a browser, network, or cached version
- Open the website in a private or incognito window.
- Clear the browser cache and check the site again.
- If the problem continues, clear the DNS cache where applicable, then test using another network, such as mobile data.
Hostinger says Website Builder does not have Cache Manager. Do not follow instructions for a different hosting product as if that control were available for an AI Builder site. See Hostinger’s cache-clearing guidance for the product-specific context.
If recent edits are missing, publish from one editor session
Changes in the editor may not yet be live. Close other builder tabs or devices so that only one editor session remains open. Reapply any changes that are missing, then publish the website and check the live version again. Hostinger’s manual-mode guide for changes that do not appear on a website also recommends checking publication, Coming Soon mode, and product status where relevant.
If the problem began after adding custom code
A code snippet may be responsible for a site that stopped working after a code change. Remove all custom-code snippets and publish the website. If it works, add the snippets back one at a time, publishing after each, to identify the one associated with the break. Hostinger notes that custom-code changes reach the live source when the site is updated, and that code is visible in preview and online rather than inside the editor. Follow its manual-mode custom-code instructions.
Free tools Windows power users keep installed
One-click scans. No signup required.
Use AI Builder-specific troubleshooting
Hostinger’s general website-error guidance explicitly excludes AI Builder sites from its PHP-error troubleshooting. Do not apply PHP or .htaccess fixes by default; use the manual-mode checks above instead. See Hostinger’s website-error guidance and its scope.
Best Value
When to contact Hostinger support
If the checks do not resolve the issue, contact Hostinger support. Include the domain, the exact browser error or behavior, whether the issue affects other devices or networks, and any recent changes to domain pointing, publication settings, the account, editor sessions, or custom code. Those details help support distinguish among the possible causes.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
