Security
Port Scanning — Ethics and Responsible Use
Understand what PingThat's HTTP port check reports, its limits, and how to approach testing responsibly.
What this tool checks
PingThat sends an HTTP HEAD request over HTTP or HTTPS from a remote server to the domain you enter. It accepts domain names, not IP addresses. It is not a raw TCP or UDP scanner, and it does not read service banners or identify the software behind a response.
The result is one of four states:
- Open: an HTTP response arrived on a port intended for HTTP.
- Closed: the connection was refused.
- Filtered: another connection error or timeout occurred. This does not confirm that a firewall caused it.
- Unverifiable: a response arrived on a port not intended for HTTP, so the check cannot verify its service.
The port-label column shows typical names associated with port numbers, such as SSH for port 22. These are labels, not detections. The request comes from a remote server, so routing and network rules may make its result differ from a check inside your network.
Use a clear, authorised scope
Before testing, confirm that the domain is within the scope you are allowed to check. Review any relevant written authorisation, engagement scope, bug-bounty rules, contracts, and hosting-provider policies. Rules differ by situation and location; this guide does not give a legal determination.
Use a protocol-specific tool from an appropriate network location when you need to verify SSH, databases, UDP, or another non-HTTP service. Avoid broad or repeated checks that could create unnecessary traffic. If a system owner or provider asks you to stop, stop and follow their reporting instructions.
Further reading on PingThat
- /docs/http-status-codes-in-monitoring/ — understand HTTP response codes
- /docs/ssl-certificate-monitoring-basics/ — review a TLS certificate after confirming an HTTP(S) endpoint responds
- /docs/dns-propagation-explained/ — understand how a domain resolves
Related tools
Frequently asked questions
Does PingThat perform a raw TCP scan?
No. It sends an HTTP HEAD request over HTTP or HTTPS from a remote server. It does not inspect TCP flags, test UDP, identify software, or verify non-HTTP services.
What does an SSH label mean in the results?
It is the typical label associated with port 22. The tool does not detect or verify an SSH service.
Can I scan a domain without permission?
Only use the tool for domains you are authorised to test. Check the applicable laws, contracts, and provider policies for your situation; this guide does not determine whether a particular test is legally permitted.