X-Hcdn-Cache-Status
Hostinger's CDN reports its cache verdict in the
unofficial X-Hcdn-Cache-Status response header.
The header appears on responses from Hostinger-hosted
sites beside Platform: hostinger and
Panel: hpanel, with
X-Hcdn-Request-ID and
X-Hcdn-Upstream-Rt completing
the CDN's header set.
Usage
Hostinger documents its CDN as a platform feature
without documenting the headers, so observed
behavior fills in the detail. The value set matches
the nginx cache-status vocabulary, and the origins
behind the CDN frequently answer with LiteSpeed
cache headers of their own, stacking two cache
layers whose verdicts diverge: an edge MISS with
an origin X-LiteSpeed-Cache
hit means the page came from the origin's cache
rather than fresh rendering.
Values
MISS
The dominant observed value. The CDN held no stored copy and fetched the response from the origin.
DYNAMIC
The CDN classified the response as uncacheable content and passed the request through, the treatment WordPress pages with sessions receive.
HIT
The response came from the CDN's edge cache.
BYPASS and EXPIRED
Rarer verdicts: BYPASS marks a request the CDN
declined to serve from cache, and EXPIRED a stored
copy past its lifetime, refetched from the origin.
Example
A first fetch of a Hostinger-hosted page misses the edge cache, with the platform's signature headers alongside.
HTTP/1.1 200 OK
X-Hcdn-Cache-Status: MISS
X-Hcdn-Request-ID: 21ce2b4449c992d00655258b41ceafa3-bos-edge1
X-Hcdn-Upstream-Rt: 0.119
Platform: hostinger
Panel: hpanel