Public Tunnel creates an outbound-only HTTPS path from your device to DNSExit so visitors can reach a local app, dashboard, NAS interface, or webhook receiver even when inbound access is blocked.
Browser-based services you want to reach from anywhere.
Need SSH, RDP, or VPN instead? Static-IP Relay →
The client on your device connects outward to DNSExit, so nothing has to wait for inbound traffic and no router port has to be opened.
Pick by how your service can be reached today.
Still the right answer when you already have public inbound access and only need the hostname to follow a changing IP.
Free Dynamic DNS →Better when inbound access is blocked, router settings are unavailable, or you want a simpler path for web traffic.
Get started →Public Tunnel is web-first; Static-IP Relay is the better path for TCP services such as SSH, RDP, or VPN.
Static-IP Relay →Reach a self-hosted dashboard or web app when the router cannot accept inbound traffic.
View use case →Receive callbacks from public services while developing against a local app.
View use case →Send a preview link before you deploy a demo, review build, or temporary site.
View use case →No. The client connects outward to DNSExit, so you do not need to open inbound router ports for the first web-focused workflow.
Yes. A public HTTPS callback URL that forwards to a local app is one of the strongest early use cases.
Usually not. Public Tunnel is web-first; Static-IP Relay is the better path for TCP services such as SSH, RDP, or VPN.
Yes. A tunnel makes the app reachable; it does not replace authentication, authorization, or sensible app security.
Tell us what local web service you need to reach, and we will use those answers to shape the first customers.