FINDING · DETECTION
The paper identifies a fundamental architectural vulnerability in single-IP circumvention designs: a relay must generate new observable flows (via DNS or TLS SNI) to reach end services after receiving client connections, creating a detectable server-and-client behavioral contrast. A relay accessing user-facing domains (news, social media) scores high on a Relay Suspicion Score (w=0.9) versus infrastructure domains (w=0.1). The paper argues this host-level signal is censorship-invariant and cannot be concealed by link obfuscation.
From 2026-almutairi-server — Server, Client, or Relay? Dual-Role Detection of Circumvention Relays · §2.4, §4 · 2026 · Free and Open Communications on the Internet
Implications
- Circumvention tools that reuse the same IP for ingress (client→proxy) and egress (proxy→destination) are fingerprinted at the host level; separate relay and egress IP addresses defeat the heuristic entirely.
- Destination scoring based on SNI metadata means accessing high-value domains (news, social media) directly increases suspicion; tunneling all egress through an infrastructure-looking endpoint (CDN, update mirror) lowers the Relay Suspicion Score.
Tags
Extracted by claude-sonnet-4-6 — review before relying.