SoftEther VPN Counts Show Remote Administration at Internet Scale
SoftEther VPN provides a VPN Server, a VPN Bridge and a remote management utility. The server can be administered through VPN Server Manager or vpncmd, including from a remote host. It also supports virtual hubs, user authentication, access control lists and server certificates.
ZoomEye count-only queries on 2026-11-18 returned 771,114 matches for app="SoftEther VPN" and 838,473 for title="SoftEther VPN". These are among the largest counts in this batch. A product match can represent a client page, a management interface or a service banner. The count does not distinguish a VPN endpoint from the administration path.
SoftEther's documentation describes remote administration through VPN Server Manager and HTTP or SOCKS proxies. It also describes an adminip.txt file that can restrict which addresses reach the administration utility. The server certificate is used by VPN clients to authenticate the server. Those controls are separate: a valid tunnel certificate does not make the manager password private, and an IP allowlist is only useful when the source address is meaningful.
Protect the administration plane first
The installation guide states that the manager password for the entire VPN Server is not set when the server is first installed. An unconfigured management interface should not be reachable from an untrusted network. Set a strong administrator password, restrict the management source by firewall or adminip.txt, and verify that the management port is not exposed by a broad cloud security group.
Virtual Hub administration adds another level. A server administrator can manage the server, while a Virtual Hub administrator may have a narrower scope. Review which accounts exist, which hubs they can manage and whether external authentication such as RADIUS is used where appropriate. Remove default or shared administrative accounts.
Server certificates should be issued for the actual hostname used by clients. Client-side validation should reject an unexpected certificate even if the tunnel starts. A self-signed certificate can be acceptable in a controlled deployment, but it should be distributed through a managed trust process, not accepted blindly on every client.
Treat VPN exposure as a routing and identity problem
A public VPN endpoint is intended to accept connections from untrusted networks. The security question is what happens after authentication. Segment virtual hubs by user group, restrict routes and audit connections. An access control list on a hub can reduce unwanted source addresses, but it should not replace account authentication and device policy.
Collect logs for administrator logins, failed password attempts, certificate changes, virtual hub changes and unusual connection patterns. Keep those logs separate from general VPN session logs. An administrator login from a new source deserves a different alert than a normal user reconnecting.
The large counts are a reminder that this is common infrastructure, not a rare lab product. Use cloud and network inventory to find the organization's own endpoints, then test the management plane from an external address. A clean VPN session does not prove that the manager path is protected.
Top comments (0)