Online port exposure checker
A port check tries to connect to selected TCP services on a public IP address. It can help identify reachable web servers, SSH endpoints or mail services, but it is not a vulnerability scan.
Run the basic TCP port checkThe main checker opens in its existing compact interface. Results are not indexed as public content.
What does an open TCP port mean?
An open port indicates that a TCP connection from the xMyIP server to the target IP and port succeeded at the time of the test. It suggests some network endpoint accepted the connection; it does not prove which software is running, whether authentication is strong, or whether the service is vulnerable.
For example, port 443 often serves HTTPS, port 22 is commonly used for SSH, and port 25 for SMTP. These conventions are helpful labels only: applications can listen on nonstandard ports, and a port number by itself cannot identify the running software.
Why do ports appear closed or filtered?
A failed connection can mean no service is listening, a firewall dropped the packet, a provider blocked inbound access or the response took longer than the scan timeout. The homepage intentionally tests only a small list of common TCP ports with short timeouts.
Network address translation, carrier-grade NAT, VPNs and hosting firewalls can all change what is reachable from the public internet. An empty result is not evidence that every possible port is closed.
What ports does xMyIP check?
The homepage checks a concise set of common ports including 20, 21, 22, 25, 80, 443, 465, 587 and 8080. The Advanced tool checks a broader fixed list of TCP ports on demand, and report downloads are available after a successful run.
The checks are made from the xMyIP server toward the submitted public address. Results can differ when tested from another country or another network because firewalls and routing rules may depend on source address.
How should I respond to an unexpected result?
Confirm which service should be listening, check your router port forwarding settings and examine local firewall rules. Remove unnecessary public exposure, keep any required service updated and use authentication appropriate for the service.
If a web service is intentionally public, an open port is expected. The relevant security question is whether it is configured and maintained safely. Run diagnostics only for systems you own or are authorized to test.