Auto-detect your public IP address to pre-fill the target field?

Free Bulk Port Scanner — Check Multiple Ports at Once

Scan up to 50 ports in one go — enter a hostname or IP address, list the ports you want to check in the Port Configuration box (comma-separated like 22,80,443, as a range like 1-1024, or one per line), or hit a preset button (Web, Database, Remote Access) to load a common set. Click Scan and the Results Table shows each port's open/closed status, service name, response time in milliseconds, and risk level. Export the full bulk port scan to CSV in one click.

IPv4, IPv6, or domain

Max 50 ports. Supports comma-separated, ranges (80-443), or one per line.

Quick Presets

Multi-Port Scanning

Scan up to 50 ports at once with configurable timeouts and preset profiles.

Service Detection

Identifies the service behind each port, with banner grabbing for extra detail.

Risk Assessment

Each open port is tagged with a risk level — Critical, High, Medium, or Low.

CSV Export

Download your full scan results as a CSV file for reporting or further analysis.

What Is a Bulk Port Scanner?

A bulk port scanner tests multiple ports on a host in a single operation — reporting the status, service name, response time, and risk level for each port in one results table. This is fundamentally different from a basic port checker, which tests one port at a time and only tells you open or closed.

When you deploy a new server, update firewall rules, or need to audit what's exposed on an IP, checking ports one by one is impractical. A bulk scan lets you verify your full attack surface in seconds.

How It Differs from a Single-Port Check

Single-port checker

  • Tests one port per scan
  • Returns open or closed
  • Good for quick one-off verifications
  • No service or risk context

Bulk port scanner (this tool)

  • Tests up to 50 ports simultaneously
  • Returns status, service, response time, risk level
  • Designed for audits and deployment checks
  • Exportable results (CSV)

Supported Port Input Formats

The Port Configuration field accepts several formats — you can mix and match them in a single scan:

Format Example Result
Comma-separated22,80,443,3306Scans exactly those 4 ports
Range1-1024Scans ports 1 through 1024
Mixed22,80,8000-8090Combines individual ports with a range
One per line22
80
443
Each line is treated as a separate port
Preset buttonsWeb, Database, Remote Access…Loads a curated set automatically

How to Read Your Bulk Scan Results

Each row in the results table gives you four data points per port. Here's what they mean and how to act on them.

Port Status

OPEN

A service is actively listening and accepted the connection. This port is reachable from the internet.

CLOSED

The host is reachable but no service is listening — it actively rejected the connection with a RST packet.

FILTERED

A firewall is silently dropping packets. No response came back — the scanner timed out waiting.

Risk Level Ratings

Risk levels apply only to open ports and indicate the security exposure of the service listening on that port.

Level Criteria Examples Action
CriticalUnencrypted, default credentials, legacy protocolTelnet (23), plain FTP (21)Remediate immediately — close or replace
HighKnown attack targets, frequently brute-forcedSSH (22), RDP (3389), VNC (5900)Restrict access to trusted IPs only
MediumStandard services requiring regular patchingHTTP (80), HTTPS (443), SMTP (25)Keep patched and monitor
LowWell-configured necessary servicesHTTPS (443) with HSTS, DNS (53)Maintain posture — no immediate action

Exporting Results to CSV

After the scan completes, click Export to CSV to download a spreadsheet with all port results. Each row contains the port number, status, service name, response time in milliseconds, and risk level. Use this for audit reports, sharing with your team, or tracking port exposure changes over time.

When to Use a Bulk Port Scanner

A bulk scan is the right tool whenever you need to verify multiple ports at once — whether you're checking a newly deployed server, testing firewall rules, or diagnosing why certain services are unreachable.

Security Audits and Firewall Testing

Verify that your firewall rules are actually enforced from the outside. After applying a new security group rule or iptables change, run a bulk scan of the ports you expect to be blocked. If any show as open, the rule is misconfigured. This is the fastest way to confirm your intended vs actual exposure.

Server Deployment Verification

When you bring up a new server or container, scan the expected service ports to confirm everything started correctly and is reachable. Check that database ports (3306, 5432, 27017) are not open to the internet, and that your web ports (80, 443) are open. One scan replaces a dozen individual checks.

ISP Port Blocking Diagnosis

Some ISPs block specific ports on residential or business connections — commonly port 25 (SMTP), 80 (HTTP), and 443 (HTTPS). If you're running a home server or game server and connections aren't reaching it, scan your public IP against multiple candidate ports to determine whether it's an ISP block, a router config issue, or a local firewall problem.

Game Server and Home Network Setup

Hosting a Minecraft, Valheim, ARK, or other game server requires specific ports to be open and forwarded through your router. Use the Remote Access or custom port preset to scan your public IP for all the ports your game uses simultaneously — much faster than checking each one individually and immediately shows which port forwarding rules are missing or broken.

Is Port Scanning Legal?

Port scanning is a standard network diagnostic technique — but legality depends entirely on authorization. Scanning your own infrastructure or systems you have written permission to test is legal in virtually all jurisdictions. Scanning systems you don't own without permission is not.

What You Can Scan

  • Your own servers and VMs — any IP address or domain you own or control
  • Infrastructure you're paid to test — with a signed scope-of-work or written authorization from the system owner
  • Your home network — your router's public IP, your home lab servers, your NAS or game server
  • Cloud instances you own — AWS, GCP, Azure VMs and load balancers under your account (check provider terms — most allow it for owned resources)

What You Cannot Scan

  • Third-party servers without permission — even a simple port scan of someone else's IP can violate the Computer Fraud and Abuse Act (US), the Computer Misuse Act (UK), or equivalent laws in your country
  • Shared hosting or CDN IPs — scanning a shared IP affects other customers on the same infrastructure
  • Any system where you're unsure of ownership — when in doubt, don't scan

This tool is provided for legitimate network diagnostics and security testing of systems you have the right to test. Always obtain written authorization before scanning any infrastructure that isn't yours.

Frequently Asked Questions

How many ports can I scan at once?
You can scan up to 50 ports per scan. Enter them as a comma-separated list (22,80,443), as a range (1-1024), or a combination (22,80,8000-8090). The preset buttons load curated port groups automatically — Web, Database, Remote Access, Mail, and more.
What formats can I use to enter ports?
The Port Configuration field accepts comma-separated ports (22,80,443,8080), ranges (1-1024), mixed formats (22,80,443,8000-8090), or one port per line. You can also use the preset buttons to load common service port groups — they populate the field automatically so you can modify them if needed.
What is the difference between a port checker and a port scanner?
A port checker tests a single specific port and returns open or closed — good for a quick one-off verification. A port scanner tests multiple ports simultaneously and provides richer data: service name, response time, and risk level for each port. This bulk tool is a port scanner. Use the single port checker when you only need to verify one port; use this page when you need to audit multiple ports at once.
What do the risk levels (Critical, High, Medium, Low) mean?
Risk levels apply to open ports and reflect the security exposure of the service on that port. Critical: unencrypted or legacy protocols dangerous to expose publicly (Telnet 23, plain FTP 21). High: common brute-force targets (SSH 22, RDP 3389, VNC 5900) — restrict to trusted IPs. Medium: standard services needing regular patching (HTTP 80, HTTPS 443). Low: well-configured necessary services with minimal immediate risk.
Why is a port showing as closed when I know the service is running?
Three common causes: (1) The service is bound to 127.0.0.1 (localhost only) instead of 0.0.0.0 (all interfaces). (2) A firewall — cloud security group, OS firewall (iptables, ufw, Windows Defender Firewall), or network appliance — is blocking the port before the connection reaches the service. (3) The service crashed or failed to start. Run netstat -ano on Windows or ss -tuln on Linux to confirm the service is listening on the right interface.
Can I export bulk scan results?
Yes. After a scan completes, click the Export to CSV button to download a spreadsheet containing each port's status, service name, response time in milliseconds, and risk level. This is useful for sharing results with your team, pasting into security audit reports, or comparing scan results over time to detect changes in your exposed attack surface.
What port presets are available?
The preset buttons load curated port groups: Web (80, 443, 8080, 8443), Database (1433, 3306, 5432, 6379, 27017), Remote Access (22, 23, 3389, 5900), Mail (25, 110, 143, 465, 587, 993, 995), DNS & Network (53, 67, 68, 123, 161), and Common (a combined set of the most frequently scanned ports). Presets populate the Port Configuration field — you can edit the port list after loading a preset.
How do I scan a range of ports?
Enter the range in the Port Configuration field using a hyphen — for example 1-1024 to scan the first 1024 ports, or 8000-8090 for a specific application range. You can combine ranges with individual ports: 22,80,443,8000-8090. Keep the total port count under 50 for a single scan.
Is it legal to scan someone else's server?
Scanning IPs or domains you own or have explicit written permission to test is legal. Scanning systems you don't own without authorization may violate the Computer Fraud and Abuse Act (US), the Computer Misuse Act (UK), or equivalent laws in your jurisdiction. This tool is designed for legitimate network diagnostics — always get written permission before scanning any infrastructure that isn't yours.
Why do some ports show as filtered instead of closed?
Filtered means a firewall or network device is silently dropping packets — no response comes back, and the scanner times out. Closed means the host actively rejects the connection with a RST packet. Filtered is harder to diagnose because it looks the same as a downed host. Check firewall rules at the OS level (iptables, ufw, Windows Defender Firewall) and at the cloud or network level (security groups, ACLs).

Comments & Feedback

Share your experience or ask questions about this tool