Fix guide · Hostinger

Hostinger has two caches. Clearing one doesn’t clear the other.

A Hostinger site can sit behind a server cache (LiteSpeed, managed in hPanel’s Cache Manager) and Hostinger CDN in front of it. Each keeps its own copy and has its own button. CacheWins itself runs on Hostinger, behind Hostinger CDN.

Two Hostinger layers, each with its own copy. Clear the server cache first, then the CDN, so the CDN fetches the fresh page.

Not sure this is the layer? Paste your URL and the checker reads the headers for you.

Check my site

How to tell which one served your page

x-hcdn-request-idPresent on every response delivered through Hostinger CDN. If you see it, the CDN is in front of your site. source

x-hcdn-cache-statusWhat the CDN did: HIT served from cache, MISS fetched from your site, EXPIRED cached copy expired and fetched again, DYNAMIC not cacheable, BYPASS cache skipped, REVALIDATED refreshed. source

x-litespeed-cacheThe server cache. Hostinger’s Cache Manager controls only the LiteSpeed web server cache. source See the LiteSpeed guide for what its values mean.

In our own checks Hostinger CDN responses also carry server: hcdn (seen on cachewins.com, 11 Sep 2026). Hostinger doesn’t document that, so treat x-hcdn-request-id as the reliable sign.

How to clear it, in this order

1. The server cache

Web or Cloud hosting: hPanel → Websites → Dashboard next to the site. On the Essentials card press Clear cache. source
Agency hosting: press Flush cache on the Settings card. source
WordPress sites: WordPress → Overview, then Flush Cache on the Core card. source
One URL: Websites → Dashboard, search for Cache Manager. It can purge the whole site or a specific URL. source

2. Hostinger CDN

hPanel → Websites → Dashboard → Performance → CDN in the left sidebar (on Agency plans, CDN directly). Press Flush cache. Hostinger says it takes effect within seconds. source

Why the order matters: if you flush the CDN first while the server still holds the old page, the CDN’s next request fetches the old page again and caches it afresh.

If it keeps coming back

Automatic cache. With Cache Manager’s automatic cache on, Hostinger stores your content and refreshes it every 30 minutes, so an unpurged change can take up to that long to appear. source
Hostinger’s own test: switch on the CDN’s Development mode. If the problem disappears, flush the CDN cache, then turn Development mode off. source

Working without it for a while

Development mode (in the CDN section) makes Hostinger CDN skip its cache so every change shows at once. Turn it off when you’re done: while it’s on, the site loses the CDN’s speed. source For the server cache, the No cache preview button on the Essentials card shows the site without it. source

Other fix guides

LiteSpeed Cloudflare WordPress Vercel Netlify nginx Service workers

Sources

Every step above was written from these pages, read on 11 Sep 2026. Vendors move buttons; if one has moved, the source page will say where.