How to fix: Cloudflare CF-Ray request identifier present
The Cloudflare CF-Ray response header exposes the request identifier that Cloudflare assigns to every proxied request.
Why it matters
CF-Ray alone does not leak sensitive information, but it confirms your origin sits behind Cloudflare and lets attackers correlate request IDs to logs.
CF-Ray is informational: it lets support teams trace a specific request through Cloudflare's edge. It does not contain user data, PII, or session tokens.
How to fix it
- 1CF-Ray cannot be removed from Cloudflare responses. If you want to hide CDN usage, terminate the proxy at the origin (no Cloudflare).
- 2If you want to keep Cloudflare but reduce fingerprinting, ensure all other Cloudflare-specific headers (cf-ray, cf-cache-status, cf-worker) are also present so attackers cannot easily distinguish them.
Code examples
Cloudflare Transform Rule
# Disable if you migrate off Cloudflare. Otherwise leave it for traceability.
# In Cloudflare dashboard → Rules → Transform Rules → Modify Response Header
# Action: Remove Header → Name: cf-rayReferences
Detected automatically by VulnRadar. The check id is cf-ray-header, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is Cloudflare CF-Ray request identifier present?
- VulnRadar rates this info severity in the headers category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id cf-ray-header, which stays the same between runs so you can filter, diff, or gate CI on it.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.