IP Tools
Local test ready · production pending

Port Checker

Create one bounded network job and inspect only validated worker evidence.

Method:
Same-origin API → isolated network worker; explicit create, refresh and cancel only
Status:
idle

Input

Result

Ready

No job has been created. Complete the bounded form to begin.

One target and one bounded operation per job. No URL fetch, port range, custom resolver or browser-side probe is available.

Tool guide

Clear input, result, and evidence boundaries

Check whether one public TCP port can be reached from the selected probe region.

01

Input and method

One public hostname or IP, exactly one TCP port from 1 to 65535, and a probe region.

02

Reading the result

Open, closed, filtered, and timeout states include resolved target IP, probe region, and connection time.

03

Boundary and privacy

Private targets, ranges, lists, UDP, scanning, and vulnerability claims are rejected; filtered is not guessed as closed.

FAQ

Frequently asked questions

What does Port Checker check?

Check whether one public TCP port can be reached from the selected probe region.

What input does Port Checker accept?

One public hostname or IP, exactly one TCP port from 1 to 65535, and a probe region.

How should I interpret Port Checker results?

Open, closed, filtered, and timeout states include resolved target IP, probe region, and connection time.

What can Port Checker not prove?

Private targets, ranges, lists, UDP, scanning, and vulnerability claims are rejected; filtered is not guessed as closed.

How does Port Checker handle input and results?

Input is used only for this explicit check. Private targets, ranges, lists, UDP, scanning, and vulnerability claims are rejected; filtered is not guessed as closed.

When should I run Port Checker again?

Run it again after the relevant network, address, browser environment, or target changes. Open, closed, filtered, and timeout states include resolved target IP, probe region, and connection time.

Continue checking