No recent scans recorded.
Target hosts and tested ports will appear here automatically for fast 1-click re-testing.
Test router port forwarding and external TCP port reachability instantly without bloat or ads.
Parallel scan on 216.73.216.246.
Too many requests from your IP. Please wait for the cooldown window to reset.
No recent scans recorded.
Target hosts and tested ports will appear here automatically for fast 1-click re-testing.
Understand port probe outcomes and quick fixes before changing router settings.
Your host responded to the TCP probe. The port is open and routing traffic normally.
Packets reached your device, but the OS rejected the connection (TCP RST).
127.0.0.1 instead of 0.0.0.0.No response within 2000ms. Packets were blocked or discarded on route.
If ports show FILTERED despite correct rules, your ISP likely uses Carrier-Grade NAT (WAN IP 100.64.0.0/10). Standard port forwarding won't work without a static IP or Cloudflare/Tailscale tunnel.
Testing ports 80 or 443 on home routers can fail because the router reserves them for its own web UI. Remap external port (e.g., forward external 8443 to internal 443) and assign a static LAN DHCP reservation.
Everything you need to know about checking open ports, router port forwarding, and network security.
Enter your public IP (auto-detected above) and the target port number (e.g. 25565, 80, 443, 22), then click "Check Port". Our edge server sends an immediate TCP SYN packet. If your router forwards the packet and your application responds with SYN-ACK, the port is OPEN and accessible to the internet.
To test port 443 (HTTPS), keep your web server running, type 443 in the Port field, and click "Check Port". If it shows CLOSED or FILTERED, confirm your SSL web daemon (Nginx, Apache, Caddy, or IIS) is bound to 0.0.0.0 and your router does not reserve 443 for its remote admin panel.
No. onmyport.com operates with a strict zero-logging policy. Probes are executed strictly in memory to perform the TCP handshake and verify reachability. We do not store your IP address, target ports, or scan history on any database or persistent log.
Your external WAN IP is automatically detected when you open onmyport.com. Simply choose your port number or select a quick preset (such as Minecraft 25565, RDP 3389, or SSH 22) and hit "Check Port". You can also test remote domains or secondary servers anytime.
In Windows Command Prompt (CMD), run "netstat -ano | findstr :<PORT>" to see if an application is LISTENING locally. In PowerShell, run "Test-NetConnection 127.0.0.1 -Port <PORT>" to verify socket connectivity and obtain "TcpTestSucceeded : True".
Unlike TCP which uses a 3-way handshake (SYN, SYN-ACK, ACK), UDP is connectionless and does not respond unless the specific application protocol answers with valid payload. Most online UDP port scanners guess or rely on ICMP "Port Unreachable" packets, which routers routinely drop. For reliable UDP verification (DNS 53, WireGuard 51820), local socket testing or bidirectional protocol testing is required.
Log into your router (e.g. 192.168.1.1 or 192.168.0.1), navigate to Port Forwarding / Virtual Server, and forward the external port (e.g. 25565) to your PC's internal static IP. Ensure Windows Defender Firewall allows inbound TCP traffic, then test your public IP on onmyport.com. If still FILTERED, verify your ISP does not use CGNAT.
A FILTERED result means your TCP SYN packet was silently dropped without any acknowledgment—typically caused by Windows Defender Firewall, an upstream router without a forwarding rule, or ISP CGNAT. In contrast, a CLOSED result proves your host is reachable, but the target operating system replied with a TCP RST packet because no application is listening on that port or it is restricted to 127.0.0.1.
Learn how to port forward Minecraft 25565, check listening ports in PowerShell, or bypass CGNAT with zero-trust tunnels.