CC Proxy Detector

CC Proxy Detector v5.2

Detect the real backend origin of Claude Code proxy/relay services.

检测 Claude Code 中转站的真实后端来源。

Features

- Three-backend detection: Anthropic API / AWS Bedrock / Google Vertex AI
- Reverse-engineering source identification: Kiro, Antigravity, Droid, Windsurf, Warp, Claude Code Max, etc.
- Multi-model scanning: Detect mixed-channel routing (different models → different backends)
- Ratelimit dynamic verification: Distinguish real vs forged ratelimit headers
- Anti-disguise: Missing-field negative evidence to catch deep spoofing

Backend & Reverse-Engineering Sources

All Claude access ultimately routes through one of three backends. Various tools reverse-engineer these backends:

Behavioral Anomalies (Reverse-Engineering Clues)

Beyond fingerprint fields, reverse-engineered channels often exhibit runtime anomalies:

- tool_use pairing errors: Each tool_use block must have a corresponding tool_result block — proxy rewrites tool IDs but breaks the pairing chain
- Intermittent HTTP 500: Proxy's format conversion pipeline fails on certain model/feature combos
- Model availability gaps: Some models work, others don't — proxy only mapped certain model IDs
- Elevated latency + variance: Extra hop through proxy adds 1-3s and higher P99 tail latency
- Thinking/streaming glitches: Proxy fails to properly relay SSE events or thinking blocks
- Multimodal/image reading failure: Image data lost in transit or backend doesn't support vision — Read returns empty for images
- Write large content errors: Proxy has request/response body size limits, writing beyond a threshold fails
- WebFetch blocked: Proxy network policy blocks external domain access
- Tool parameter validation errors: Some tools (e.g. TaskList) hit parameter validation errors due to incomplete…