Platform
The unofficial Platform response header identifies the hosting platform or infrastructure serving the response.
Usage
The Platform header is sent by managed hosting providers to expose which platform backs a given site. Hostinger is the dominant sender, using the header to identify its hPanel-based hosting environment. The value "hostinger" appears on the vast majority of sites including this header.
Platforms send the header as part of a broader set of
infrastructure-identifying headers. On Hostinger, Platform often
appears alongside X-Powered-By,
Panel,
x-hcdn-cache-status, and X-Hostinger-Node. Together these headers
describe the full stack: platform, control panel, CDN cache status,
and edge node.
Values
hostinger
Indicates the response is served from Hostinger's hosting infrastructure. This is by far the most common value, present on nearly all sites sending the header.
Other platform identifiers
Some infrastructure providers and smaller hosting platforms use the header with their own identifiers. Values such as "By TurboCloud" and similar strings indicate platform-specific branding rather than a standardized format.
Example
A response from a site hosted on Hostinger. The value identifies the platform directly by name, confirming the request was served from Hostinger's infrastructure.
Platform: hostinger
A response from a smaller or custom hosting platform branding its value differently.
Platform: By TurboCloud
Observed in the wild
Crawl data across 332 hosts sending Platform
shows a single value dominating: hostinger, on
effectively every observation. The header is in
practice a Hostinger fingerprint rather than a
convention shared across providers.
The header travels as a pair. 313 of the observed
hosts send Panel alongside, carrying
hpanel, Hostinger's control panel, so the two
together identify both the hosting company and the
management layer in one glance at the response.
The pair matters mostly for reconnaissance, in both directions. An operator debugging an unfamiliar site learns the host without a DNS lookup, and the same transparency hands attackers the platform name for targeting known issues, which is the standing argument against infrastructure headers carrying vendor identity.