iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
If your Hostinger AI Builder website is unavailable, shows a placeholder, or fails to display recent edits, check the domain connection, publication status, account, and exact browser error first. Then test whether the problem affects every visitor or only one browser or network. The steps below follow Hostinger’s current manual-mode troubleshooting guidance, checked October 7, 2026; the cause of a specific site problem depends on its settings and error message.
Start by identifying what is not working
Separate the symptom before changing settings. Is the site unavailable to everyone, showing a Coming Soon page, missing recent edits, returning a 403 Forbidden error, displaying an SSL warning, or breaking after you added custom code? Also test the site in a private or incognito window and, if possible, on another network such as mobile data. If only one browser or network has the problem, focus on its cache or DNS cache before changing the site itself.
Hostinger’s manual-mode troubleshooting guide covers these issues as possible causes, not as a diagnosis of any particular website.
Recommended Free Tools
Check the domain and its connection to the site
- Confirm that the domain is connected to the website you intend visitors to reach, and that it points to Hostinger.
- Check that the domain owner’s contact details are correct.
- If you changed domain pointing recently, verify the settings again. Hostinger lists recent pointing changes as a possible cause but does not specify a DNS propagation window in its guide.
- If the domain is registered with another provider, check whether DNSSEC is enabled there. Hostinger says this DNSSEC check does not apply to domains registered at Hostinger.
Domain pointing and DNSSEC are separate checks: confirm the domain points to the right website, then check DNSSEC only when the domain is externally registered. Hostinger’s optional nslookup guide explains a way to inspect DNS records, but running a lookup is not required for the checks above.
Make sure the site is published and visible
The site is unavailable or visitors see a placeholder
Open the website in Hostinger AI Builder and confirm it has been published. If visitors see a placeholder rather than your pages, check whether Coming Soon mode is enabled. Hostinger’s guide to changes not appearing includes publication and Coming Soon status among the checks for a site that does not look as expected online.
A store product is missing
Check that the site has a product section, that the product is set to Active, and that it is saved. Then publish the website again. A product’s status and the site’s publication status are distinct: verify both.
Check whether the domain or hosting plan has expired
Review your Hostinger account for the domain and hosting plan status. Hostinger lists expiration of either as a possible reason a website may not work. If an account item has expired, follow the account’s renewal or recovery options; the troubleshooting guide does not establish that expiration is the cause without checking your account.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsUse the exact error to choose the next check
403 Forbidden
Note the full error and when it appears. Hostinger lists a 403 Forbidden response among the symptoms to investigate, but the guide does not establish a single cause for every 403. Continue with the domain, publication, account, and browser/network checks rather than assuming an SSL or code problem.
SSL or “Not Secure” warning
First confirm that the website is published. Hostinger’s SSL warning guidance says publication is a check for a “Not Secure” or “Not Private” warning. Hostinger associates ERR_SSL_PROTOCOL_ERROR with an SSL certificate that is not installed or is not working properly; that explanation should not be treated as the cause of every SSL error.
Rule out a stale browser or network view
- Open the site in a private or incognito window.
- Clear the browser cache and load the site again.
- If the problem persists, clear the DNS cache where applicable.
- Test from another network, such as mobile data, to see whether the result changes.
Hostinger notes that Website Builder does not have Cache Manager. Its general cache guidance should not be read as meaning that the Builder has that control; use the browser and DNS cache checks where relevant.
Restore missing edits and avoid editor-session conflicts
If your changes appear in the editor but not on the live site, close other builder tabs or devices so that only one editor session remains active. Reapply any needed changes in that session and publish. Hostinger’s manual-mode guidance identifies concurrent editor sessions and an unpublished update as possibilities; check both rather than assuming the edits were lost.
Test custom code if the site broke after adding it
- Remove all custom-code snippets from the website.
- Publish the site and check whether it works.
- If it does, add the snippets back one at a time, publishing and checking after each one, to identify the snippet associated with the break.
Hostinger’s manual-mode custom-code guide says code changes need to be published to reach the live site. Custom code is visible in preview and online, not inside the editor itself, so the editor view alone may not show how it affects visitors.
Best Value
When to contact Hostinger support
If the domain, publication, account, error, cache/network, editor-session, and recent-code checks do not resolve the issue, contact Hostinger support. Include the exact browser error, whether the issue affects other browsers or networks, and any recent domain, site, or code changes. Those details help support distinguish a site-wide problem from one limited to a particular connection or recent change.
Do not default to generic PHP or .htaccess troubleshooting for an AI Builder site. Hostinger’s general website-error guide explicitly excludes AI Builder from its generic PHP troubleshooting and directs Builder users to the Builder-specific route.
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.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →
