Sada Files
  1. 1Choose file
  2. 2Adjust
  3. 3Download

Check a public page

Enter a URL in the settings and run the check. Our server fetches the page through an SSRF-safe fetcher, analyses it in memory and stores nothing.

Port Reachability Checker online, free

Probe public IP or domain ports to verify service reachability safely.

  • Encrypted server job — auto-deleted in 24 h
  • Free, no sign-up, no watermark
  • TXT
How to use Port Reachability Checker · Port Reachability Checker — frequently asked questions

How to use Port Reachability Checker

  1. 1

    Add your TXT file

    Drop a file on the page, paste it, or click Select Files.

  2. 2

    Fine-tune the settings

    The defaults already suit most files; change them only if you need to.

  3. 3

    Run Port Reachability Checker

    Press the start button. The file is processed on an encrypted, auto-deleting server job.

  4. 4

    Download the result

    Save the finished file, or continue with another tool without downloading in between.

What Port Reachability Checker can do

  • Encrypted server processing; files are deleted automatically within 24 hours
  • Free with no sign-up, no watermark and no daily limit

Port Reachability Checker — frequently asked questions

How does the Port Reachability Checker work?

The Port Reachability Checker initiates a non-intrusive TCP handshake probe from our edge nodes to the specified hostname or public IP address on requested port numbers.

Which standard ports can I test?

You can test common application ports including HTTP (80), HTTPS (443), SSH (22), FTP (21), SMTP (25), MySQL (3306), PostgreSQL (5432), and HTTP-Alt (8080), or enter custom comma-delimited ports.

Does a closed port mean my service is broken?

A closed or filtered port might indicate that the service daemon is not running, or that a cloud security group or local firewall (e.g. iptables, ufw) is blocking external inbound connections.

Can I probe private or internal IP addresses?

No. In accordance with SSRF protection policies, attempts to probe private subnets (RFC 1918), loopback addresses (127.0.0.1), or link-local endpoints are rejected.

Are my scanned hosts or port queries stored or logged?

No. Probes run strictly in volatile memory. Sada Files logs zero IP addresses, hostnames, or scan results.