Website profiles · Technology insights · Alternatives

portchecker.co

Port Checker is a simple tool to check for open ports and test port forwarding setup on your router. Verify and diagnose connection errors on your computer.

No paid content found
Visit website
Profile views 13 Outbound visits 5 Normal
Port Checker Full homepage screenshot

At a glance

Category
Resources & Utilities
Language
English
Paid-content signal
No paid content foundObserved
Registered
2014
Hosting
Akamai Connected CloudInferred
HTTPS certificate trusted
PassedObserved
Last updated

Website review

This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.

What is Port Checker?

Port Checker is a free online tool that tests whether a specific port on your computer or network is open and reachable from the internet. You enter a port number (it can prefill your current IP address), and it reports whether that port responds. Its main practical use is verifying that port forwarding on your router actually works, and diagnosing why an application can't connect.

What it actually does

  • Checks a single port at a time against an IP address you specify — typically your own public IP, which the page offers to fill in automatically.
  • Confirms port forwarding rules. If you forwarded a port on your router but the check still shows it closed, the rule, the firewall, or your ISP is likely the problem.
  • Helps with connection troubleshooting. The site frames this around cases like email or chat clients failing to connect because a required port is blocked by a router firewall or ISP.
  • Doubles as a basic exposure check. If you didn't intend a port to be open to the internet, seeing it respond is a signal worth investigating.

Common ports it lists for quick selection

The page includes shortcuts for well-known services, including FTP (21), SSH (22), SMTP (25), DNS (53), HTTP (80), POP3 (110), IMAP (143), HTTPS (443), SMB (445), MySQL (3306), Remote Desktop (3389), VNC (5900), Redis (6379), and Minecraft (25565). These are conventions defined by IANA, not guarantees about your machine.

A concrete scenario

You're hosting a Minecraft server for friends. You set up port forwarding for 25565, but nobody can join. Run the check against your public IP on port 25565. If it reports closed, work through the chain: is the server process actually running and listening, does your OS firewall allow it, is the router rule pointing at the right internal IP, and does your ISP block inbound connections? If it reports open, the problem is more likely on the server configuration or the players' side.

Trade-offs to keep in mind

  • It tests reachability from outside, not whether a service is healthy or correctly configured — an open port can still host a broken service.
  • A "closed" result can also come from a firewall that silently drops packets, so it doesn't always distinguish "nothing listening" from "blocked."
  • It checks one port per run, so auditing many services means repeating the process.

Useful next step

Before checking, confirm your public IP hasn't changed (many home connections use dynamic addresses), then test the exact port your application uses. For broader port scanning of your own host, a dedicated scanner is more efficient; for reference on port assignments, see IANA or the port list on Wikipedia.

How do I use Port Checker to test if port forwarding is set up correctly on my router?

Use Port Checker to test port forwarding from the outside in: enter the port you configured in your router, run the check against your current public IP, and see whether the tool reports the port as open or closed. Open means something on your network accepted a connection on that port from the internet; closed or filtered means the request never reached a listening service.

Port Checker is built for exactly this task. Its page describes it as a free online tool for checking open ports and verifying port forwarding on a router, and it fills in your current IP automatically so you can test without looking it up yourself.

A practical test sequence

  1. Confirm the service is actually running on the target device. Port forwarding only exposes a port that something is already listening on.
  2. Note the exact port. The tool lists common ones such as 25565 for Minecraft, 3389 for Remote Desktop, 5900 for VNC, 80 for HTTP and 443 for HTTPS, but you can enter any number from 1 to 65535.
  3. Keep the default "use current IP" setting if you are testing your own network from inside it, or type your public IP if you are checking from elsewhere.
  4. Run the check. Repeat it once or twice, since a single failed attempt can be a transient timeout rather than a real block.
  5. If it reports closed, work backwards: service running, correct local IP reserved, router rule enabled for the right protocol (TCP or UDP), then ISP-level blocking.

Reading the result

Result Likely meaning Next step
Open The router forwards the port and a service answered Test the application itself from outside your network
Closed The request reached your network but nothing accepted it Check the service, local IP and whether the rule targets the right protocol
No response / filtered Often a firewall or ISP block Check router firewall rules and whether your ISP permits inbound connections

Common traps

Testing from inside your own network can give misleading results, because some routers do not support NAT loopback. If the check fails at home but a friend connects fine, that is usually the cause rather than a forwarding error.

Also match the protocol. A rule opened for TCP will not help a UDP-only game server, and the tool's port list is a naming aid, not a guarantee of which protocol your application uses.

For a second opinion, you can compare with Can You See Me or check what your public address currently is via What Is My IP Address, since a changed IP from your ISP will silently break a working forward.

Why is a specific port blocked by my router or ISP and how can Port Checker help diagnose it?

A port can be blocked at several points between your device and the internet, and the reason usually depends on where the block sits. Common causes include:

  • Your router's firewall or NAT rules — the port isn't forwarded to your device, or a firewall rule rejects it.
  • Your operating system firewall — the service is running, but the OS refuses incoming connections.
  • Your ISP — many residential ISPs block inbound ports (commonly 25, 80, 443, and others) to reduce abuse, or place you behind carrier-grade NAT so inbound connections never reach your router.
  • Nothing is listening — the application isn't running or is bound only to localhost.

Port Checker helps you narrow this down because it tests from the outside in. You enter your public IP and a port number, and it reports whether that port accepts a connection from the internet. If the tool says the port is open, the path from the internet to your device is working. If it says closed or filtered, the block is somewhere along that path — your router, your ISP, or a service that isn't listening.

A practical way to use it:

  1. Confirm the service is running locally and listening on the expected port (check your app or use a local port scan).
  2. Run the check against your current public IP and that port.
  3. If it fails, verify the port-forwarding rule in your router points to the correct internal IP and port.
  4. Temporarily disable the OS firewall rule for that port to see if it's the culprit.
  5. If it still fails after forwarding is correct, your ISP is the likely blocker — try a different port or ask about CGNAT.

For a concrete scenario: someone hosting a Minecraft server on port 25565 can use the checker to confirm friends can reach it. If the check fails while the server runs locally, the forwarding rule or ISP is the problem, not the game.

As a next step, test a second port that you know is intentionally open (or one you set up specifically) to distinguish a single misconfigured rule from a broader ISP-level block. If every inbound port fails, suspect CGNAT or ISP filtering rather than your router.

What are the most common ports and their associated services that I should check?

Start with the handful of ports that map to services you actually run or connect to. Checking those first catches most firewall, ISP-blocking and port-forwarding problems.

Ports worth checking first

Port Service Typical use
21 FTP Legacy file transfer; often blocked or replaced by SFTP
22 SSH Remote server administration and secure file transfer (also SFTP)
25 SMTP Sending mail; frequently blocked by ISPs to stop spam
53 DNS Name resolution; useful when websites fail to load but ping works
80 HTTP Unencrypted web traffic
110 POP3 Older mail retrieval
143 IMAP Mail retrieval across devices
443 HTTPS Encrypted web traffic; the port to test if a site won't load
465 / 993 / 995 SMTPS / IMAPS / POP3S Encrypted mail sending and retrieval
3306 MySQL Database access; should not be exposed to the internet
3389 RDP Remote Desktop; a common target for attackers if left open
5900 VNC Remote screen access
25565 Minecraft Game server hosting and port forwarding

How to use this

Port Checker checks whether a port on your connection is reachable from outside, which is what matters for port forwarding. A concrete example: you host a Minecraft server and friends cannot join. Test port 25565; if it shows closed, the problem is usually the router's forwarding rule or a firewall, not the game itself. The same logic applies to an email client that won't send (test 25 or 465) or a web server that isn't reachable (test 80 or 443).

Keep two cautions in mind. First, an open port is not automatically a good thing: RDP (3389), VNC (5900) and database ports (3306) should generally stay closed to the internet and be reached through a VPN instead. Second, a "closed" result can come from your ISP blocking the port rather than your own configuration, so test a port you know should be open before concluding anything.

For a fuller reference list, the page points to Wikipedia's list of TCP and UDP port numbers.

How can I use Port Checker to secure my network by identifying open ports?

Use Port Checker as an external reachability test: it checks whether a specific port on your public IP accepts connections from the internet. It does not scan your whole network or tell you which program owns a port, so treat it as one step in a wider review.

A practical workflow

  1. Find your public IP. The page shows your current IP address, which is the address the checker tests.
  2. Enter one port at a time. Test only ports you expect to be reachable, such as 443 for a web server or 25565 for a Minecraft server.
  3. Read the result in context. "Open" means something on your network answered from the outside; "closed" or filtered usually means a firewall, router rule or ISP is blocking it.
  4. If a port is open and you did not intend it to be, close it at the source: disable the port-forwarding rule, turn off the service, or block it in the router or host firewall.
  5. Re-test after each change. Repeat for every port you care about.

Which ports deserve attention

The page lists common ports, which is a useful starting point for deciding what to test. High-risk ones to check first include remote-access services such as 22 (SSH), 23 (Telnet), 3389 (RDP), 5631 (PC Anywhere) and 5900 (VNC), plus database ports like 3306 (MySQL), 5432 (PostgreSQL), 6379 (Redis) and 11211 (Memcached). File-sharing ports such as 445 (SMB) and mail ports like 25 (SMTP) are also worth verifying. These should normally not be reachable from the open internet unless you have deliberately set up secure remote access.

What the tool cannot tell you

Question Port Checker What you need instead
Is this port reachable from outside? Yes, for the port you enter —
Which app is listening on this port? No Local command such as netstat or ss
Are other ports open? No A port scanner or router's own device list
Is the service itself secure? No Configuration review of that service

A concrete scenario

You run a home server and want remote desktop access. You test 3389 and it reports open. That is a finding, not a fix: RDP exposed directly to the internet is a common target for brute-force attempts. A safer next step is to disable the router's port-forward rule for 3389 and reach the machine through a VPN or a tunnelled remote-access tool instead. Then re-test 3389 to confirm it is no longer reachable.

For a fuller picture, compare with a dedicated scanner or your router's administration page, and use the port list on Port Checker to decide which numbers to test rather than testing all 65,535.

What steps should I take if Port Checker shows a port as closed when I need it open for a game server or application?

A closed result from Port Checker means the checker could not reach that port from the outside. It does not tell you where the block is: the application may not be listening, the router may not be forwarding, or a firewall or ISP may be filtering the traffic. Work through the layers in order.

H3. Check from the inside first Confirm the service is actually running and bound to the right interface on the host machine. From another device on the same local network, try connecting to the host's local IP and the port. If that fails, the problem is the application or a local firewall, not port forwarding. If it succeeds, move outward.

Verify the router's port forwarding rule

  • The rule should point to the host's current local IP address. A DHCP lease change can silently break it, so set a static local IP or a DHCP reservation.
  • Protocol matters: some games and services need both TCP and UDP, and many routers require separate rules.
  • Check for a double NAT, e.g. a modem/router combo plus your own router. Forwarding on the inner router does nothing if the outer one does not pass the traffic through.
  • Some routers have separate firewall or "port filtering" settings that override forwarding rules.

H3. Test the right address Make sure you are checking your public IP, not a local one, and that the service is reachable from outside your network. Testing from inside your own network can give misleading results because of NAT loopback behaviour. Use a phone on mobile data or ask someone outside your network to try.

H3. Consider ISP blocking and CGNAT Many residential ISPs block common inbound ports such as 25, 80 and 443, and some place customers behind carrier-grade NAT, where you have no public IP of your own and forwarding cannot work at all. Compare the public IP the checker reports with the WAN address shown in your router's status page; if they differ, you are likely behind CGNAT. Ask your ISP, or use a tunnel or relay service instead.

H3. Pick a different port if needed If the application supports it, try a high port in the 49152-65535 range, which is less likely to be blocked or already in use. Remember that anyone connecting must use the same port, and update the game or app configuration to match.

H3. Practical example A Minecraft server on port 25565 shows closed. You confirm a friend on the same LAN can connect, so the server is fine. You check the router rule and find it points to an old local IP from before the machine rebooted. You set a DHCP reservation, re-add the rule for both TCP and UDP, and retest from mobile data. If it still shows closed and your router's WAN IP differs from the checker's reported public IP, CGNAT is the likely cause.

Next step: change one thing at a time and retest after each change, starting with the local connection test. That way you know which layer actually fixed it.

Related questions

More questions →
What is portchecker.co?
Port Checker is a simple tool to check for open ports and test port forwarding setup on your router. Verify and diagnose connection errors on your computer.
Does portchecker.co offer paid content?
Unknown.
What languages does portchecker.co support?
Primary language: English.
How can I visit portchecker.co?
Use the Visit website link to open the website in a new tab.
What are some alternatives to portchecker.co?
Related websites include zperiod.app, zoneless.tools, zerobounce.net, zen.unit.ms, zamzar.com, yt5s.com. Compare their features and pricing for your needs.

Website Overview

Identifiable technologies and additional version or configuration signals make the service easier to fingerprint, which may help targeted scanners narrow their checks. An established domain and managed infrastructure suggest continuity of operations and may support dependable delivery, although neither guarantees service quality.

Domain and Registration

Registered in 2014, this domain has about 12 years of history. That suggests continuity, although ownership and purpose may have changed. Transfer-protection status is present, helping reduce the risk of unauthorized domain transfers. The registrar is NameCheap, Inc., a widely used domain service provider. The domain uses the common .co extension, which is not an independent safety signal.

DNS and Email

Nameservers are provided by DigitalOcean, indicating managed DNS hosting. No CNAME was found; the observed records resolve directly to addresses. No MX record was found. A conventional explicit inbound-mail route is not configured. DNSSEC signatures were not detected, so this additional DNS authenticity protection is not confirmed. The lowest observed DNS TTL is 578 seconds.

TLS and Certificates

The certificate uses an RSA 2048-bit public key, offering broad client compatibility. The server supplied a complete certificate chain. No organization name is present in the certificate; the available fields are consistent with domain validation. The certificate was issued by Let's Encrypt, commonly associated with automated certificate services. The certificate's total validity is about 89 days, consistent with a short renewal cycle.

HTTP and Browser Security

The Server header exposes the software version: nginx/1.20.2 + Phusion Passenger(R) 6.0.15. This makes version-targeted checks easier, but is not proof of an exploitable vulnerability. X-Powered-By exposes backend information: Phusion Passenger(R) 6.0.15. The response lacks these common security headers: CSP, Referrer-Policy, Permissions-Policy. No obvious internal addresses or debug information were found in the headers. Cookie security attributes are unknown.

Technology Stack Analysis

The public page identifies Google Analytics, nginx 1.20.2, with exact versions exposed for 1 technologies. These details can narrow vulnerability checks, although exposure alone is not a vulnerability.

Search and Social Sharing

No homepage canonical URL was detected. If duplicate URLs exist, consolidation may be less explicit. No Open Graph metadata was detected, so social previews may depend on platform inference. The title has 38 characters, within a common display range. A meta description is present, with 158 characters. The observed directives allow indexing and link following.

Hosting and Email

DNSDigitalOcean
HostingAkamai Connected Cloud
EmailUnknown
Approximate IP geolocation (inferred; a CDN or proxy may differ from the origin server) United States flagFremont, California, United States Inferred 45.33.50.110

Registration details

RDAP / WHOIS

RegistrarNameCheap, Inc.
Registered2014-08-22
Expires2030-08-21
Domain statusclientTransferProhibited https://icann.org/epp#clientTransferProhibited
Nameserversns1.digitalocean.com、ns2.digitalocean.com、ns3.digitalocean.com
DNSSECunsigned

DNS records

DNS

TypeNameValueTTLPriority
Aportchecker.co45.33.50.110578—
NSportchecker.cons1.digitalocean.com1357—
NSportchecker.cons2.digitalocean.com1357—
NSportchecker.cons3.digitalocean.com1357—
TXTportchecker.cobrave-ledger-verification=b0b89b9ad32b04f92a4a581f85d4580c7c6233ad560e1183347bbc03a65a56903600—

TLS and certificates

TLS / SSL

AssessmentNormal configuration
Supported protocolsTLSv1.2
Negotiated protocolTLSv1.2
Certificate subjectportchecker.co
IssuerLet's Encrypt
Valid until2026-12-04T23:16 · Remaining when checked: 71 days
Verification detailsCertificate trust: Passed · Hostname match: Passed

HTTP response headers

HTTP

HeaderValue
content-typetext/html;charset=utf-8
servernginx/1.20.2 + Phusion Passenger(R) 6.0.15
strict-transport-securitymax-age=15768000
x-frame-optionsSAMEORIGIN
x-content-type-optionsnosniff
set-cookieRedacted

Identified technologies

Google Analyticsnginx 1.20.2

Pages, Search and Sharing

Meta descriptionPort Checker is a simple tool to check for open ports and test port forwarding setup on your router. Verify and diagnose connection errors on your computer.
Canonical URLNot detected
LanguageEnglish (default)
Twitter CardNot detected

Unknown

All bots 0 allowed · 2 disallowed
  • Disallow/privacy-policy
  • Disallow/privacy-policy.html

No sitemaps found

User reviews (0)

  • No reviews yet.