Port Scanner
Fast, accurate and free online port scanner tool running directly in your browser.
-
1Enter data
Enter content, paste text or load a file from disk. -
2Click the button
The tool will immediately process your data in the browser. -
3Get the result
Copy the finished text or save the file to your device.
return "Result ready in 0.1s";
}
Port scanner
Check which of the selected TCP and UDP ports are reachable on the specified host or IP address. The tool is only used to test the security of systems to which you have permission.
Port scan results
No scan results. Change the port range or parameters and try again.
Rate this tool:
Related tools
Other tools you may find usefulPort Scanner online - check open TCP and UDP ports for a selected host
Port Scanner in the Webp toolkit is an easy-to-use online tool that allows you to check selected TCP and UDP ports for a selected host or IP address, without installing additional programs and without entering complicated commands in the console. You enter the host name or IP, select whether you want to scan popular ports, add your own list and with one click you run the scan, and after a while you can see whether the ports appear to be open, closed or filtered, along with the approximate response delay.
Port Scanner in Webp is designed for everyday users, website owners and administrators who want to check the basic port status of your servers or services in just a few seconds and make sure that only those services that really should be available are visible externally. This tool does not require technical knowledge of protocols or low-level network functions, but at the same time it gives a clear overview of whether selected ports are responding and what their response looks like from the perspective of a simple test.
Why do you need Port Scanner and when is it worth using it
For many people, the term port scanning is associated only with advanced security testing, and in practice, Port Scanner can also be very useful in everyday, completely ordinary tasks, such as checking whether the web server is actually listening on port 80 or 443, whether the database is not accidentally exposed to the world or whether the administration panel is visible only from the internal network. One short scan of selected ports can save a lot of frustration when configuring services, redirections and firewalls, because you can immediately see whether the network connection has a chance to work or whether traffic is blocked before it even reaches the application.
Useful scenarios for the website owner
- Checking if a website is actually responding on port 80 or 443 when everything seems to be configured correctly but the browser still shows a connection error.
- Quickly verify that your mail server has SMTP, IMAP or POP3 ports open before you start looking for errors in your mail client or panel settings.
- Ensure that no ports are exposed to the internet for services that should only be accessible locally, such as old admin panels or old test environments.
Scenarios for administrators and technical people
- Preliminary control of which popular TCP ports are open on a newly launched server, which speeds up firewall configuration and organizing incoming traffic rules.
- Scans basic UDP ports, such as DNS or NTP, to check whether web server services are missing access on the correct ports.
- Quick verification of response on non-standard ports entered in the own list field, for example when testing new microservices or unusual applications in the company network.
What does the Port Scanner form look like and what options can you set
The Port Scanner form in Webp has been designed so that, on the one hand, it remains as simple and visually friendly as possible, and on the other hand, it gives the user real control over which ports will be examined and how aggressive the scanning itself should be. All the most important options are described in Polish, so even a less technical person will easily understand what each field and switch is responsible for after a short reading.
The most important fields in Port Scanner
- Host or IP address- the main place where you enter the hostname, for example
example.com, or the direct IP address, for example1.2.3.4, so that Port Scanner knows where to try to make connections. - Scan popular TCP ports- a convenient switch that, when selected, tells the tool to scan a set of most frequently used TCP ports, such as 22, 80, 443, 3306, 5432, 6379, 8080 and others, giving you a quick picture of the most popular services on the server.
- Scan basic UDP ports- the second option, which allows you to add a few key UDP ports to the scan, for example DNS and NTP, which are very common, but work a little differently than classic TCP connections.
- Custom Port List- a field where you can manually enter port numbers to check, for example as a comma-separated list or a range like
21,22,80,8000-8010, which is useful when testing custom services or specific environments.
Additional port scanning parameters
- Maximum number of ports in the scan- allows you to limit the number of port combinations that will be checked, which is especially useful when you combine popular ports with your own list and want to make sure that the scan will not be too broad.
- Single connection timeout- defines how many seconds Port Scanner waits for a response when trying to connect to a given port, which affects the speed of the entire scan and how slow responding services are treated.
- Scan ports button- after clicking this button, Port Scanner starts sending connection attempts to the selected ports and, after the entire process is completed, displays the results in a clear table, so you do not have to refresh the page or track the progress elsewhere.
How to read Port Scanner results and what the statuses mean
After the scan is completed, Port Scanner presents the data in a clear table with several columns that describe each port individually, so that even a person without extensive network experience is able to figure out which ports appear to be open and which ones do not accept connections or are filtered by the firewall. This facilitates both the initial diagnosis of service availability problems and an overview of what is actually exposed to the outside world in your infrastructure.
| Column | What | represents How to interpret it in practice |
|---|---|---|
| Protocol | Information whether a given entry concerns a TCP port or a UDP port, which is important for the operation of the service itself. | If you see TCP, it usually means classic connections such as a website or database, while the UDP entry may mean, among others, DNS or NTP services, which do not build a full connection but respond with single packets. |
| Port | The port number that has been checked on the specified host or IP address, for example 80, 443, 22, 3306 or 8080. | The overview will quickly show you which standard ports are active and which are not, making it easier to adjust the service configuration to the expected state and compare it with firewall rules. |
| Status | An assessment of the port status, such as open, closed, or filtered open, based on the responses received from Port Scanner. | An open port usually means something is listening on it, a closed status indicates no response, and a filtered status suggests that there may be a firewall blocking or modifying traffic along the way. |
| Delay | Approximate response time in milliseconds, i.e. how long the attempt to contact a given port took. | Low latency may indicate a well-functioning service or local server, while higher latency values may be due to load, distance, or network filters, so it's worth looking at this parameter in a broader context. |
| Notes | Additional text information about the entry, for example a comment related to the method of detection or the specific response of the port. | The attention field can be used as a notebook for further analysis, marking ports that require additional examination, configuration changes, or consultation with the security team. |
Security and responsible use of Port Scanner
Port scanning is a natural element of taking care of security, because it allows you to see which server services are visible from the outside, but at the same time it requires common sense and responsibility so as not to violate other people's privacy or service regulations. Therefore, Port Scanner in Webp is presented as a supporting tool for checking your own servers, corporate projects and systems for which you have explicit permission to conduct tests.
Things to remember before scanning
- Always scan only hosts, servers and addresses that belong to you or your organization, or for which you have written consent to security testing.
- Do not use Port Scanner as a tool for mass scanning of random addresses on the network, as it may violate Internet service regulations and local regulations in your country.
- Remember that scan results are approximate and depend on the configuration of networks, firewalls and systems along the way, so it is always worth comparing them with logs, server configuration and other sources of information.
How to put the results into practice
- If you see open ports that you don't recognize, check carefully what service is behind them and whether it should actually be accessible from the Internet before you decide to leave it that way.
- Ports that are open but not currently being used by any needed applications should be considered for closure at the server or firewall level to reduce the potential attack surface.
- Response time and status information can be used as a basis for further performance testing and monitoring, making it easier to spot sudden changes in service behavior in the future.
Online port scanner - which ports should be checked first?
When you use a tool likeonline port scanner, you do not have to scan all 65,535 ports - in practice, the server's security is determined by the dozen or so most popular services. The cheat sheet below shows where to start a port scan and what an open result means:
| Port | Service | Open = ? |
|---|---|---|
| 21 | FTP | outdated file transfer - if you don't use it, close it (passwords are in plain text) |
| 22 | SSH | remote server access - OK, but only with a key and preferably with an IP limit |
| 25 | SMTP | mail sending - open without the need to facilitate spamming from your IP |
| 80 / 443 | HTTP / HTTPS | website - normal for a web server |
| 3306 | MySQL/MariaDB | database - should NOT be visible from the Internet |
| 3389 | RDP | remote desktop Windows - favorite target for brute force attacks |
| 5432 | PostgreSQL | database - as above, only for internal network |
| 8080 | alternative HTTP | often forgotten administration panels and proxies |
Good practice: scan your server with our port scanner after each firewall configuration change and compare the result with the list of services that you consciously expose. Any open port that you can't assign to a specific service is a potential backdoor - close it in your firewall or limit it to trusted IP addresses.
Frequently asked questions about Port Scanner in Webp
Does Port Scanner work fully online and without installing additional applications
Port Scanner in Webp works as a web tool, so you operate it directly from the browser, without having to install programs on your computer and without configuring additional modules. All you need to do is go to the tool's website, enter the host or IP address, select the port range and click scan, and the rest happens on the server side, which returns a clear table with the results.
Why am I getting an invalid host or IP address message?
If you see information about an invalid host, make sure you have entered only the domain or IP address only, without prefixes likehttp://or additional paths in the address, because Port Scanner verifies the basic data format and does not accept full URLs. After correcting the entry and removing unnecessary characters, try running the scan again and the tool will check the hostname in DNS again.
Will Port Scanner always show the exact status of all ports
The result of each scan depends on many factors, such as firewall configuration, ISP network filtering, server load and the way applications handle connections, so Port Scanner should be treated as a helpful diagnostic tool, not as the sole source of truth. If you see a result that seems unusual to you, it is worth confirming it with other methods, such as server logs or additional tests performed by the administrator.
Can I save the port scan results for further analysis
The easiest way is to select the entire table of results directly in the browser, copy it to the clipboard, and paste it into a spreadsheet or document where you are working with your team on infrastructure analysis. This allows you to later add your own comments, mark ports for closure, or leave notes for others responsible for maintaining the server.
Is it legal to scan ports on other people's servers
The question of legality depends on the jurisdiction and the regulations of specific services, but it is good practice to limit scanning only to your own systems or those where you have explicit permissions to perform security tests, for example as part of an audit or bug bounty program. Webp's Port Scanner is designed to help you keep your services secure, so always use it in accordance with the law and fair use principles.
Check selected ports of your server in seconds
Instead of guessing which services are visible from the Internet, run Port Scanner in Webp, enter the host or IP address, select popular TCP and basic UDP ports, add your own numbers and with one click see a practical list of results with information about status and latency. This is the fastest way to gain basic knowledge about how your server responds to traffic and which ports should be secured, closed or subject to additional monitoring.
Run Port Scanner and check your ports