Catch a callback behind NAT, CGNAT or campus Wi-Fi
Free, and no account needed for one session. Create a listener and follow along.
Create a listenerAuthorized use only. Use RevSheller only on CTFs, your own labs, training platforms and engagements where you have permission.
Why port forwarding fails
A classic listener such as nc -lvnp 4444 only works if the target can open a connection to your machine. That assumes your machine has an address the outside world can reach. On most home and student networks it does not, for three separate reasons.
- Ordinary NAT. Your router shares one public address between every device. Inbound connections that match no existing outbound flow are dropped unless you add a forwarding rule. That is fine at home if you own the router, but it ties the listener to one network and exposes a port on your own machine.
- CGNAT. Many ISPs, especially mobile and some fibre providers, put their own NAT in front of your router. The address on your router's WAN side is not public, so a forwarding rule on your router changes nothing. You cannot fix this from your side.
- Managed networks. University halls, campus Wi-Fi, coworking spaces, hotels and coffee shops typically block inbound traffic entirely and often filter outbound traffic to a short list of ports. You do not control the gateway, and client isolation may stop machines on the same network from reaching each other.
A quick check for CGNAT: compare the WAN address in your router's status page with the address a “what is my IP” site reports. If they differ, or the router address falls in 100.64.0.0/10 or a private range, you are behind carrier NAT.
Flip the direction of the problem
NAT only blocks connections that start from the outside. Outbound connections work fine, which is why web browsing works everywhere. RevSheller uses that. The listener lives on Cloudflare's edge at your session's own subdomain. Two outbound connections meet there:
- The target runs a generated payload and connects out to the hosted endpoint over HTTPS or WSS on port 443.
- Your browser opens the operator terminal for the same session, also outbound over WSS on 443.
The session relays between the two. Neither side needs a public address, a forwarding rule or a dynamic DNS name, so CGNAT and campus gateways are irrelevant: both ends are simply making ordinary HTTPS-style connections.
Steps
- Open revsheller.com and create a session. One anonymous session is allowed for trying it out, and registering is free during the beta.
- Copy the Auto payload (or the Windows variant) from the generator. It carries a per-session target token, so it only works for that session.
- Run it on the machine you are authorized to test: a CTF box, a VM in your lab or a host covered by your scope.
- The terminal in your browser attaches when the target connects. Delete the session when you are done; idle sessions also time out.
Because the traffic is HTTPS and WSS on 443, it usually passes egress filters that block unusual outbound ports, which is the usual reason a callback to port 4444 never arrives from a locked-down network.
When the target cannot reach the internet
The hosted endpoint only helps if the target can reach it. A box on a VPN-only lab network often cannot. In that case run the bridge agent on a machine that is connected to both the lab VPN and the internet. The target connects to the bridge over plain TCP, and the bridge carries it to RevSheller over WSS. The THM and HTB guide covers this in detail.
Honest limits
- Cloudflare does not accept inbound raw TCP, so a bare
ncor/dev/tcpone-liner cannot connect to the edge directly. Use the generated payloads or the bridge. - If the network blocks outbound HTTPS to
revsheller.comor its subdomains entirely, the target cannot reach the listener, and this approach will not help. - Your campus or employer may forbid running these tools on their network. Check the acceptable use policy and stay within it. RevSheller is for systems you are permitted to test.
FAQ
Do I need to forward any port to use RevSheller?
No. The target connects out over HTTPS or WSS on 443 and you attach from your browser.
How do I know if I am behind CGNAT?
Compare your router's WAN address with your public address. If they differ, or the router address is in 100.64.0.0/10 or a private range, your ISP is translating your connection.
Does this work if my target is on a VPN-only lab network?
Only if the target can reach the internet. Otherwise use the bridge agent from your VPN-connected machine.
Can I use it on any network or machine?
Only on systems you own or have explicit permission to test, and where network policy allows it. See the Terms of Service.
Ready to try it? One click creates a listener; you paste one command on a machine you are authorized to test.
Create a listener