tool / ports
Port Scan
Check common open ports.
try
Real resolvers
Every gap labelled.
Each result shows its source and what was not tested.
How Port Scan works
A port checker tries to reach well-known ports on a host. Open ports that you did not mean to expose are a common security gap.
Enter a domain or IP.
See which ports answer.
Close or firewall any port you do not need public.
Troubleshooting & Remediation
How to Read & Fix Results
How to read the result
- ProblemA port you did not mean to expose (for example a database or remote desktop) answers from the internet.
- WarningA management port such as SSH answers from anywhere. It may be intended, but restrict it if you can.
- PassOnly the ports you intend to serve (usually 80 and 443) answer. Ports shown as not tested were not checked.
How to fix issues
- 1List what each open port is for. Close anything you cannot explain.
- 2Block unused ports in the host firewall or your cloud provider security group.
- 3Restrict SSH and databases to known IP addresses or a VPN instead of the whole internet.
- 4Re-run the check afterwards from the same tool.
Common mistakes to avoid
- •Binding a database to 0.0.0.0 with no firewall in front.
- •Blocking a port in one firewall while another layer still allows it.
- •Assuming IPv6 is covered by IPv4 rules.
- •Testing hosts you do not own. Only check systems you own or have permission to test.
Example UFW Firewall Rules
ufw default deny incoming ufw allow 443/tcp ufw allow from 203.0.113.5 to any port 22 proto tcp ufw enable
We try a TCP connection from our Cloudflare edge to the port. Some outbound ports are blocked there, so they show as not tested instead of guessed. A firewall can answer differently for your network.
Next checks:Check the certificateCheck security headersFull domain audit
Specifications & Scope
About Port Scan
- 01 / What it does
- A port checker tries to reach well-known ports on a host. Open ports that you did not mean to expose are a common security gap.
- 02 / How to use
- 1. Enter a domain or IP. 2. See which ports answer. 3. Close or firewall any port you do not need public.
- 03 / Good to know
- Our servers run at the network edge and cannot open raw connections to every port. Ports that could not be tested are shown as "not tested", never as closed.
Got Questions?
Frequently Asked Questions
Knowledge Base
Technical Guides & Reference
Explore More
More in Security & Web
Tool Details & Usage Guide
RFC specifications, input expectations, outputs, and edge limitations.
Overview
Performs basic HTTP/HTTPS connectivity probes against standard web ports on a target IP or domain.
Inputs
- Target: IP or Domain
Output Interpretation
- Results: Lists explicitly probed web ports as Open or Closed/Filtered. Ports not probed by the tool are labeled as Not Tested.
Examples & Limitations
- Example Use Case: Quickly verifying if a web server is responding on ports 80 and 443.
- Limitation: This is a lightweight probe, not an Nmap-style TCP/UDP scanner. Unprobed ports are untested, not guaranteed safe.
Recommended Troubleshooting Deep Dives
Authoritative SRE implementation tutorials related to this tool.
Detecting Email Spoofing with DMARC Reports
Email spoofing is the digital equivalent of a forged signature—attackers send messages that appear to come from a trusted domain, hoping recipients will click a...
Read guideWhy Is My DMARC Policy Set to “none” and How to Change It
---...
Read guideReading Raw Email Headers in Outlook Web App: A Step‑by‑Step Guide
When a message lands in your inbox, most of its journey is hidden from view. The raw email header is the “passport” that records every hop, verification check, ...
Read guideRelated tools
View all toolsTCP Latency
Free TCP latency test. Time five TCP handshakes to a host from our edge servers and see min, average, slowest and packet loss.
SSL Certificate
Free SSL certificate checker. See the issuer, validity dates and days until expiry for any domain, taken from public Certificate Transparency logs.
CAA Policy
Free CAA record validator and generator. Audit published RFC 8659 CAA DNS records, restrict authorized Certificate Authorities, and generate Cloudflare, BIND, and Route 53 policies.