Your Connection Overview
What is IPPortTest.com?
IPPortTest.com is a free, browser-based network diagnostics tool that lets you test port connectivity, ping remote hosts, inspect HTTP responses, verify SSL/TLS certificates, and scan devices on your local network — all without installing any software. Whether you're a home user trying to open a port for a game server, a sysadmin verifying firewall rules, or a developer debugging a web service, this tool gives you instant, accurate results.
TCP Port Testing
Check whether a specific TCP port is open, closed, or filtered on any public IP address or hostname. Our server performs the real connection — bypassing browser security restrictions — so you get accurate results every time. Supports all ports from 1 to 65535.
ICMP Ping
Send ICMP echo requests to any public host to check if it's online and measure round-trip latency. Useful for verifying that a server is reachable before troubleshooting port-specific issues. Falls back to TCP probing if ICMP is blocked by the target's firewall.
HTTP Response Check
Fetch the HTTP headers from any web server and instantly see the response code, server software, redirect location, and response time. Quickly identify 200 OK, 301 redirects, 403 forbidden errors, and 500 server errors without opening a browser tab.
SSL Certificate Inspector
Connect to any HTTPS host and retrieve full TLS certificate details including expiry date, days remaining, certificate authority, common name, and all Subject Alternative Names (SANs). Get alerted when a certificate is expired or expiring within 14 days.
LAN Port Scanner
Scan devices on your local network directly from your browser. Auto-detect your router's gateway IP, probe individual ports on any LAN device, or run a full scan of 80+ common ports at once. Identifies open services on home servers, NAS devices, smart home hubs, and more.
Network Info & IP Lookup
Automatically detects your public IP address, geographic location, ISP, ASN, timezone, and browser information on page load. Useful for verifying VPN connections, confirming your public-facing IP, and checking what information your connection exposes.
How to Use This Tool
Testing a WAN Port (Internet / Router)
WAN mode tests ports from our server against any public IP address. This is the most common use case — for example, checking if port forwarding is working on your router, or verifying that a game server or web service is accessible from the internet.
To test a port: select WAN TEST, choose the TCP PORT tab, pick a preset port from the dropdown or type a custom port number, enter your target IP or hostname (or leave it blank to test your own public IP), then click RUN TEST. The result will show whether the port is open, closed, or filtered by a firewall.
Testing a LAN Port (Local Network)
LAN mode runs directly from your browser and tests devices on your local network such as your router, NAS, home server, or smart home hub. Switch to LAN TEST, enter the local IP address of your device (e.g. 192.168.1.1 for a typical router), and click RUN TEST.
Not sure of your router's IP? Click DETECT MY GATEWAY and the tool will automatically probe common gateway addresses and populate the field for you. To scan all common ports at once, enter the target IP and click SCAN HOST.
Understanding Test Results
- Open — The port is reachable and a service is actively listening. Connections can be made successfully.
- Closed — The host responded but rejected the connection. The port is reachable but no service is running on it.
- Timeout / Filtered — No response was received within 5 seconds. This usually means a firewall is silently dropping packets to that port.
Checking Your SSL Certificate
Select WAN TEST → SSL CERT tab, enter your domain name in the host field, set the port to 443 (pre-filled by default), and click RUN TEST. You'll see the full certificate chain details, expiry date, and how many days remain before renewal is needed. This is especially useful for catching expired certificates before your users do.
Frequently Asked Questions
A network port is a virtual communication endpoint identified by a number between 1 and 65535. When a computer sends data over a network, it uses an IP address to reach the destination machine and a port number to reach the specific service or application on that machine. For example, web servers listen on port 80 (HTTP) and 443 (HTTPS), SSH servers listen on port 22, and Minecraft servers default to port 25565. Think of the IP address as a building's street address and the port number as the specific apartment inside that building.
TCP (Transmission Control Protocol) and UDP (User Datagram Protocol) are the two most common transport protocols. TCP establishes a reliable two-way connection before sending data, guarantees delivery and order of packets, and confirms receipt — making it ideal for web browsing, email, file transfer, and SSH. UDP sends packets without establishing a connection first and doesn't guarantee delivery or order, making it faster and better suited for real-time applications like video streaming, VoIP, DNS lookups, and online gaming where speed matters more than perfect reliability. This tool tests TCP ports, as UDP requires raw socket access not available in a web environment.
The most common reasons are: (1) the service or application isn't actually running on that port — the port must have something actively listening on it; (2) the port forwarding rule in your router is set to the wrong internal IP address or the wrong port; (3) your ISP is blocking the port at their network level (common for ports 25, 80, and 443 on residential connections); (4) Windows Firewall or another host-based firewall on the destination machine is blocking inbound connections; or (5) the port is open but you tested it against the wrong public IP. Try running the test with no host entered to test your own public IP automatically.
A timeout means our server sent a connection request to the target port and received no response within 5 seconds. This is almost always caused by a firewall silently dropping packets — rather than actively rejecting them with a "connection refused" response. A closed port sends back an immediate refusal (RST packet in TCP), while a filtered port simply goes silent. Firewalls often filter ports this way to avoid revealing which ports are in use. If you see a timeout, check your router's firewall rules, your ISP's restrictions, and any host-based firewall on the target machine.
UDP testing requires raw socket access at the operating system level, which is not available in a web server environment for security reasons. Unlike TCP, UDP has no handshake — you send a packet and either get a response or you don't, and many services simply don't respond to unexpected UDP packets at all, making remote UDP testing inherently unreliable. To test UDP ports, use a tool like nmap -sU -p <port> <target> from your local machine or server, or nc -u -vz <target> <port> on Linux and macOS.
Yes, IPPortTest.com is completely free to use with no account required. There are no rate limits, no sign-ups, and no paywalls. The site is supported by Google AdSense advertising. We do not store your IP address, test results, or any personal information — see our Privacy Policy for full details.
WAN test results are highly accurate for TCP port reachability — our server makes a real TCP connection attempt to the target, so the result reflects exactly what any external machine would see when connecting to that port. LAN results are performed client-side using browser APIs and are generally reliable, though Chrome's Private Network Access (PNA) security policy may occasionally block connections to certain local IP ranges depending on your browser version and network configuration. For critical infrastructure testing, always verify results with dedicated tools like nmap.
Common gaming ports include: Minecraft Java (25565 TCP), Minecraft Bedrock (19132 UDP), Steam and Source games like CS2 and TF2 (27015 TCP/UDP), Terraria (7777 TCP), PlayStation Network (3478 UDP), and Xbox Live (3074 TCP/UDP). For home servers: Plex Media Server (32400 TCP), Jellyfin (8096 TCP), Home Assistant (8123 TCP), Proxmox (8006 TCP), Portainer (9000 TCP), and SSH remote access (22 TCP). Use the Port Library section below to browse all supported ports with descriptions, or use the LAN scan feature to discover which services are already running on a device.
Port Reachability Tester
Common Port Library
| PORT | SERVICE | PROTO | CATEGORY | DESCRIPTION | TEST |
|---|