What does 'Structured Custom Header Set' indicate?
It indicates the domain returns a small but deliberate set of custom HTTP headers, which is typical of sites running on maintained hosting rather than a bare, unconfigured server.
It indicates the domain returns a small but deliberate set of custom HTTP headers, which is typical of sites running on maintained hosting rather than a bare, unconfigured server.
The questions every analyst asks before acting on this signal.
It indicates the domain returns a small but deliberate set of custom HTTP headers, which is typical of sites running on maintained hosting rather than a bare, unconfigured server.
It indicates a broad set of custom headers covering caching, request tracing and delivery metadata. Producing and maintaining these headers requires operational effort that short-lived abusive infrastructure rarely invests in.
It means the response carries the dense, coherent header set emitted by a managed hosting or commerce platform such as a large storefront provider, site builder or enterprise CDN, where the platform operator controls the response and enforces its own abuse policies.
Treat it as a de-risking signal whose strength grows with the sublabel. Measurement across phishing, malware, spam and compromised-site populations shows domains with four or more custom headers are cleaner than the crawled baseline, and domains with sixteen or more are close to two orders of magnitude cleaner. It does not clear a domain on its own: a malicious page can be hosted on a managed platform, so weigh it against active malicious findings rather than letting it override them.
A realistic shape of the entry the engine appends to the risk_signals array when this signal fires. Evidence keys are subgroup-default; per-signal overrides documented in the API reference.
{
"slug": "http_custom_header_fingerprint",
"name": "Structured Custom Header Set",
"group": "http_crawling_history",
"subgroup": "http_header_behaviors",
"direction": "safe",
"evidence": {
"missing_security_headers": 4,
"cors_origin": "*",
"cors_credentials_allowed": true,
"provider_type": "self_hosted",
"risky_cookie_count": 2
}
}12 other signals share the same subgroup. They detect related behaviors and often co-fire on the same IOC.
It identifies who actually serves the domain: a CDN, a managed website platform, a free hosting platform, a security pro…
It indicates that the domain is running on a recognized enterprise or managed infrastructure stack, such as well-known a…
It indicates that the site sets cookies issued by specific edge protection providers whose cookies appear far more often…
The response does not come from a real site but from a domain parking, for-sale or traffic monetization platform: a park…
The Verdict Gallery is a curated stream of real verdicts. Filter by this signal to see exactly which IOCs it caught, what other signals fired alongside it, and what the engine recommended.
1,000 verdicts/month on the free tier, LLM layer included. No card required.