TCP reachability
Port Checker
Test whether a public TCP port is open, refused, timed out, or otherwise unreachable from Russia and Finland, with explicit latency and attempt details.
Use this page when you need a safe, bounded TCP connection test that shows whether reachability differs between Russia and Finland without turning the backend into an unrestricted proxy or port scanner.
The result tells you whether the remote side accepted the connection, rejected it immediately, or never answered before the timeout.
If a hostname resolves to more than one address, the report keeps the individual attempts visible so you can see what happened.
Successful TCP handshakes return an approximate latency from the responding probe location to the target port.
Host or IP
Port Checker
Report
ReadySummary
Server-side diagnostic report
Run a check to generate a structured report with status, timings, technical details, and raw output where available.
01
What this tool checks
Open vs refused vs timeout
The result tells you whether the remote side accepted the connection, rejected it immediately, or never answered before the timeout.
Attempt transparency
If a hostname resolves to more than one address, the report keeps the individual attempts visible so you can see what happened.
Latency where possible
Successful TCP handshakes return an approximate latency from the responding probe location to the target port.
02
How to use it
Enter the public host or IP and select the TCP port you care about.
Use the quick presets for common service ports when you want a fast check without typing.
If the port is open but the site still fails, switch to Website Checker or SSL Checker next.
03
How to read the result
Refused means a fast negative
A refused result proves the path reached the host and the remote side closed the attempt quickly instead of silently dropping it.
Timeout is less specific
A timeout can mean filtering, packet loss, or a very slow path. It does not confirm whether the service is definitely closed.
Open does not guarantee a healthy app
A TCP handshake only proves the port answered. The HTTP or TLS layer above it can still be broken or misconfigured.
Guides that help you get more from this tool
Interpret the output, understand common failure modes, and choose the next diagnostic step without leaving the product.
Port Checker FAQ
Is this a full port scanner?
No. It performs one bounded TCP check against the port you ask for and rate-limits the public endpoint for safety.
Why block private targets?
Because this is a public tool. The backend rejects localhost, RFC1918 ranges, metadata endpoints, and other reserved networks to avoid SSRF abuse.
Which tool should I use after a timeout?
Usually Ping or Traceroute for path visibility, and Website Checker if the target is meant to serve HTTP or HTTPS.