Security scan: HTTP TRACE / TRACK method enabled
The server answers TRACE requests, which a scanner flags as a cross-site tracing risk.
HTTP TRACE method enabledTRACE and TRACK methods are enabledHTTP TRACE / TRACK Methods AllowedCross-site tracing XST Meaning
TRACE echoes the request back and can expose headers such as cookies or auth tokens in XST attacks. Disable it: Apache TraceEnable off, nginx only allows GET/HEAD/POST by default (check proxies and app servers), IIS request filtering verb deny.
Common causes
- Apache default
TraceEnable on - Application server or proxy allowing TRACE
- Old IIS/Tomcat config
- Load balancer forwarding TRACE
- Scanner reporting TRACK too
⚡ Quick fix
- Apache:
TraceEnable off - Deny TRACE/TRACK at the proxy or WAF
- Re-scan:
curl -i -X TRACE https://example.com/
Detailed fix by platform
Apache
TraceEnable off
How to diagnose
- TRACE — Answered 200?
- Layer — Apache, proxy or app?
- Re-scan — Clean?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- 1005 Cloudflare Error 1005: Access denied — The owner of this website has banned the autonomous system number (ASN) your IP address is in
- 1006 Cloudflare Error 1006 / 1007 / 1008: Access denied — Your IP address has been banned
- 1009 Cloudflare Error 1009: Access denied — The owner of this website has banned the country or region your IP address is in
Most viewed in HTTP
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 18 Nov 2026