Free tools Windows power users keep installed
One-click scans. No signup required.
If your website shows an error with Hostinger CDN enabled, first check whether the failing response actually passed through the CDN. Then use the error code and controlled tests—Development mode, other cache layers, and, if needed, temporarily disabling the CDN—to distinguish a CDN-path issue from an application, hosting, proxy, or DNS problem.
Confirm whether Hostinger CDN handled the failing request
- Open your site and reproduce the error. In your browser’s developer tools, open the Network panel, select the failed request, and inspect its response headers.
- Look for
x-hcdn-request-id. Hostinger says a response delivered through its CDN includes this header. If it is absent, the request did not pass through Hostinger CDN; it may have reached your site directly or gone through another proxy. Save the full request ID when present. - Check
x-hcdn-cache-status, if shown. Values can includeHIT,MISS,EXPIRED,DYNAMIC,BYPASS, andREVALIDATED. This describes how the CDN handled caching for that response; it does not, by itself, prove that the cache caused the error.
The error code alone cannot identify which layer is responsible. Note whether the failure affects every page or only a particular form, login, API request, or callback, and compare the response headers for the affected request.
As an Amazon Associate I earn from qualifying purchases.
Triage the error code
403 Forbidden
Review Hostinger CDN traffic-blocking rules for IP-address or country blocks, and check whether the security level is rejecting legitimate visitors. If the failure is limited to a form, login, REST API call, page-builder AJAX request, or payment callback, inspect that exact request and the relevant rules and security setting. Hostinger’s guide to fixing blocked legitimate requests covers this case.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
408 Request Timeout and 504 Gateway Timeout
Hostinger distinguishes these errors by which connection timed out: a 408 means the visitor’s connection was too slow to complete the request, while a 504 means the website did not respond before the CDN stopped waiting. For a 504, check hosting resource usage and consider whether a recently added plugin or resource-heavy page builder is contributing.
#1 Best Overall
500 Internal Server Error
A 500 usually points to the website application. Check the application’s error logs and review recent code, plugin, or theme changes. Hostinger notes that an application-caused 500 also appears when the CDN is disabled, so use the comparison test below rather than assuming the CDN generated it.
502 Bad Gateway and 503 Service Unavailable
Hostinger describes 502 and 503 errors as possible signs that the website was temporarily unreachable or overloaded; they may clear on their own within minutes. If they persist, continue with the isolation steps below and check application logs and hosting resource use. For broader 5xx troubleshooting, Hostinger also lists code problems, plugin or theme overload or logical errors, and exhausted hosting resources as possible causes. Try another network or device and rule out local caching as well.
Test the CDN cache with Development mode
Hostinger’s Development mode makes the CDN fetch each request directly from the website instead of serving CDN-cached content. Use it as a test, not as a repair:
- In your Hostinger account, open the CDN settings for the affected website and enable Development mode.
- Reproduce the same failing request and check whether the error remains.
- If the error disappears, flush the CDN cache, then turn Development mode off.
- If the error remains, clear other relevant cache layers, such as LiteSpeed server cache or a WordPress caching plugin, before concluding that the application itself is responsible.
Hostinger states that it does not cache error responses, so fixing the underlying issue should make the error disappear for visitors immediately. That does not rule out other caches or a separate failure elsewhere in the request path.
Compare the site with Hostinger CDN temporarily disabled
If Development mode and cache checks do not isolate the problem, temporarily disable Hostinger CDN and allow a few minutes for DNS changes to take effect. Test the same URL and request:
- If the error remains with the CDN off, investigate the website, its hosting environment, or another proxy.
- If the error occurs only while the CDN is enabled, turn the CDN back on and contact Hostinger support with the failing URL, time of the error, and full request ID.
Disabling the CDN changes DNS routing, so this is not an instantaneous comparison for every visitor. Hostinger says some visitors may continue reaching the CDN or see a placeholder while DNS caches expire, usually within hours; that is not a guaranteed propagation time. Contact Hostinger support if the site remains unreachable more than 24 hours after enabling or disabling the CDN.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Check redirect loops, DNS, and certificate errors
Redirect loop
Hostinger identifies two common causes of redirect loops: another active proxy, such as Cloudflare, and conflicting manual redirects in .htaccess or WordPress settings. Check whether another proxy is active, then review redirect rules individually. Hostinger recommends using only one CDN for a site.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchDNS routing
Hostinger says the domain must use Hostinger nameservers for its CDN. When the CDN is enabled, it routes the root and www A/AAAA records to the CDN and manages those records. Disable the CDN before changing the root or www records. See Hostinger’s explanation of Hostinger CDN and DNS records.
Certificate error
Hostinger says its CDN serves certificates for the root and www hostnames. If a certificate error affects www, check that the hostname uses the Hostinger-managed CNAME. Also confirm that the domain’s DNS is configured for the CDN before changing records.
Rank #4
What to send Hostinger support
When you escalate a persistent issue, provide details that let support match the failure to the relevant request path:
- The exact failing URL and error code or message.
- The date and time the error occurred.
- The full
x-hcdn-request-id, if the response includes it. - Whether the error affects all requests or a specific form, login, API, or callback.
- Whether it persists in Development mode and with the CDN temporarily disabled.
- Which cache layers you cleared and any relevant application-log or hosting-resource findings.
For the full error-specific workflow, see Hostinger Help Center’s Hostinger CDN: Troubleshooting website errors.
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.
