Tunnel Profiles for SSH and Custom Connections
DarkTunnel centers its workflow on selecting a tunnel type and preparing a target before pressing Connect. The app supports SSH, SSH through DNSTT (SlowDNS), VMess, VLess, Trojan, Shadowsocks, and custom V2Ray configurations, giving experienced users several ways to express an existing server setup.
The main card keeps the selected service, operating style, and target together. A target can be written in a host-and-port form with credentials, while a payload field holds the request template used by the chosen connection. This layout is useful for people who already have server details and want one workspace for switching between profiles without navigating through a long setup wizard.
Direct, SNI, Proxy, and DNSTT Modes
Injection mode is the app's practical decision point when a connection needs a particular route or handshake style. Direct mode sends the setup toward its target, while SNI, proxy, and DNSTT choices expose alternate ways to shape the connection. The mode label stays visible beside the selected tunnel type, so users can see the relationship before they connect.
This range is useful when the same server details need different transport handling in different networks. A proxy field appears when proxy routing is selected, and SNI-oriented pages provide a server-name indication field. Users can move between these choices without rebuilding the entire workspace, keeping repeat configuration tasks easier to compare.
Transport Protocols and DNS Controls
DarkTunnel brings transport details into the same configuration flow instead of hiding them behind a separate advanced area. Its supported network options include TCP, WebSocket, and gRPC, while the protocol-oriented controls expose fields for server name, public key, UDP DNS, and other mode-specific values. These choices let a prepared profile match the way its remote service expects traffic to arrive.
The DNS control is especially useful for setups that rely on a specific resolver or DNSTT route. Users can enter a resolver such as 1.1.1.1:53, add a server name where the mode needs one, and keep the payload beside those values for quick review. The result is a more deliberate connection setup for technical users who need control over each transport detail.
Target Fields and One-Tap Connection Control
The main screen is arranged around a clear sequence: choose a tunnel and injection mode, fill the target or proxy details, review the payload, and press Connect. A large button keeps the final action easy to find, while the form uses separate labels for target, proxy, DNS, server name, public key, and payload so users can adjust one part without losing the rest of the setup.
This compact arrangement suits people who maintain their own SSH or V2Ray-style connection information and revisit it during travel, troubleshooting, or network changes. It is less useful for anyone expecting a consumer VPN with ready-made locations, because the workspace assumes that the user already knows the server, credentials, and route details needed for a successful connection.