Built for agencies and B2B sales teams.

Start free →

Free Port Checker

Test whether a public TCP port on a host is open, closed or filtered from outside your network.

Single TCP portPublic hosts onlyClear result states
Port CheckerFreeExample result
Public targets only
1 to 65535

Authorized testing only. Private, local, link-local, multicast and metadata-style targets are blocked.

OPEN

Port 587 is open

TCP port587
Common serviceSubmission
Connect time84 ms
Target hostsmtp.acme-mail.com
Resolved endpoint203.0.113.25:587
ReachabilityReachable
Checked fromDevBoxy server
The hostname resolved to a public address
The TCP handshake completed
Open means something accepted the connection. It does not prove the service is secure
How it works

How to use the Port Checker

  1. 01

    Enter a public host

    A hostname, domain or public IP.

  2. 02

    Choose a TCP port

    Pick a common port or type any port from 1 to 65535.

  3. 03

    Read the result

    Open, closed or filtered, with connect time.

What it checks

What the Port Checker checks

Verify service exposure

Is a service reachable from outside?

Audit firewall rules

See what your firewall actually allows.

Check NAT and port forwarding

Confirm a forwarded port arrives.

Reading results

Open, closed and filtered

The result state tells you where in the path to look.

StatusWhat it usually meansWhere to look
OpenSomething accepted the connectionConfirm the service is the one you expect
Closed / refusedA host actively refused the connectionIs the service running and bound correctly?
Filtered / timeoutA firewall or network device silently dropped itFirewall, cloud rules, NAT

Common TCP ports

PortServiceUsed for
22SSHRemote administration
25SMTPServer-to-server mail
80HTTPWeb traffic
443HTTPSEncrypted web traffic
587SubmissionAuthenticated mail submission
993IMAPSEncrypted mailbox access
3389RDPRemote desktop
Step by step

Why is my port closed?

  1. 01

    Confirm the service

    Is it running?

  2. 02

    Check the bind address

    A service bound to localhost is not reachable from outside.

  3. 03

    Inspect firewall and cloud rules

    Look for a rule that blocks the port.

  4. 04

    Verify NAT, forwarding and DNS

    Make sure the public address reaches the right host.

Common issues

Common problems and how to fix them

Service not running

A closed port often means nothing is listening.

Bound to localhost

The service only listens on the local machine.

Firewall or cloud rule

A silent timeout usually means filtering.

NAT or DNS mismatch

The public address points somewhere else.

Authorized testing only

Check only systems you own or have permission to test. Open or closed is reachability evidence, not a vulnerability verdict, and a registered port number does not confirm what software is running there. The checker tests TCP only, not UDP.

Use cases

When to run this check

Web and APIs

Check that 80 and 443 are reachable.

Email infrastructure

Test 25, 587 and 993 before you connect accounts.

Remote administration

Confirm that admin ports are not open to the internet.

Cloud and DevOps

Verify security-group changes.

FAQ

Port Checker FAQ

Still unsure? Read the DevBoxy blog or contact the team.

What is a port checker?

A tool that tests whether a specific TCP port on a public host is reachable from outside.

How do I check if a TCP port is open?

Enter a public hostname or IP, choose a port and run the check.

What does an open port mean?

Something accepted the connection. It does not prove the service is secure or correctly configured.

Why does my port show as closed?

The service may not be running, may be bound to localhost, or may be blocked by a firewall, cloud rule, NAT or DNS issue.

What is the difference between closed and filtered?

Closed usually means an active refusal. Filtered usually means a silent timeout from a firewall or network device.

Can it check UDP ports?

No. It is designed for TCP only.

Can I scan a private IP address?

No. Private and other non-public ranges are blocked.

Which ports should be public?

It depends on the service. HTTPS, and sometimes HTTP, for websites, and port 25 for servers that receive mail. Admin and database ports should usually be restricted.

Why does it work locally but not externally?

Local access skips parts of the public path, such as firewalls, NAT and DNS.

Does an open port mean my server is vulnerable?

No. Reachability is not a vulnerability finding.

Pair DNS checks with list verification.

Healthy authentication protects your domain. Clean contacts protect your sender reputation. Cleaner outreach starts with better data.