Public Tunnel

Expose a local web service without opening router ports

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.

  • No port forwarding: the client connects outward, so you do not need router changes to start
  • Web-first service: start with HTTPS use cases before widening into more complex TCP workflows
  • Built for self-hosters: good for home labs, demos, dashboards, and callback URLs

Good first uses

Browser-based services you want to reach from anywhere.

  • Home-lab dashboards
  • Local development demos
  • NAS or camera web panels
  • Webhook receivers and test apps

Need SSH, RDP, or VPN instead? Static-IP Relay →

How Public Tunnel works

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.

Your local web serviceApp, dashboard, NAS interface or webhook receiver
outbound
DNSExit Public TunnelPublic HTTPS endpoint
Visitors and callbacksReach your app by URL in a browser
Keep your app login controls. A tunnel makes the app reachable; it does not replace authentication, authorization, or sensible app security.

When Public Tunnel beats Dynamic DNS

Pick by how your service can be reached today.

Inbound access works

Dynamic DNS

Still the right answer when you already have public inbound access and only need the hostname to follow a changing IP.

Free Dynamic DNS →
Inbound access blocked

Public Tunnel

Better when inbound access is blocked, router settings are unavailable, or you want a simpler path for web traffic.

Get started →
SSH, RDP or VPN

Static-IP Relay

Public Tunnel is web-first; Static-IP Relay is the better path for TCP services such as SSH, RDP, or VPN.

Static-IP Relay →

Explore common use cases

Compare the alternatives

Common questions

Does Public Tunnel require port forwarding?

No. The client connects outward to DNSExit, so you do not need to open inbound router ports for the first web-focused workflow.

Can I use it for webhooks?

Yes. A public HTTPS callback URL that forwards to a local app is one of the strongest early use cases.

Is this the right fit for SSH or RDP?

Usually not. Public Tunnel is web-first; Static-IP Relay is the better path for TCP services such as SSH, RDP, or VPN.

Do I still need app login controls?

Yes. A tunnel makes the app reachable; it does not replace authentication, authorization, or sensible app security.

Signup is open

Want early access?

Tell us what local web service you need to reach, and we will use those answers to shape the first customers.

;