Free Open Ports Scan (Non-Intrusive)
Non-intrusive scan across 30+ critical ports (SSH, RDP, MySQL, Postgres, Redis, Mongo) to map your external attack surface in under a minute.
- Common port scan
- Non-intrusive
- Service banner hints

What you get for free
18 core security checks via this tool, passive scans, step-by-step remediation, security score on every result.
What Essential adds at $39/mo
+17 advanced checks, continuous monitoring, daily security score history, email alerts, GitHub SAST, board-ready PDFs, SOC 2 / ISO 27001 / PCI reports.
Security Risks of Open Ports
- Increases potential entry points for attackers
- Exposes services that may have vulnerabilities
- Provides reconnaissance information to attackers
- Enables service-specific attack techniques
- Service identification and version detection
- Outdated software versions with known exploits
- Misconfigured services and unnecessary features
- Unencrypted data transmission and storage
- Violates security best practices and standards
- May breach compliance requirements (PCI DSS, HIPAA)
- Increases audit findings and remediation costs
- Demonstrates poor security posture to stakeholders
How to reduce exposure
- Address Critical and High-risk ports first
- Follow port-specific security recommendations
- Use risk categorization to prioritize fixes
- Implement dynamic scoring to track improvements
- Implement firewall rules to block unnecessary ports
- Use network segmentation and VLAN isolation
- Configure load balancers and reverse proxies
- Implement IP whitelisting and access controls
- Disable unused services and unnecessary features
- Update software to latest secure versions
- Configure strong authentication and access controls
- Implement encryption for data in transit and at rest
What this scan checks
- Web services (80, 443, 8080, 8443)
- SSH and remote access (22, 3389, 5900)
- Database services (3306, 5432, 1433, 6379, 1521, 27017, 27018, 5984)
- Email services (25, 110, 143, 993, 995)
- File sharing (21, 22, 2049)
- Modern services (Docker, WinRM, and 30+ critical ports)
- 4-tier risk categorization (Critical, High, Medium, Low)
- Dynamic scoring with risk-based point deduction
- Port-specific security recommendations
- Attack surface mapping with risk prioritization
- External accessibility testing from external perspective
- Comprehensive attack surface mapping
- Service exposure analysis with security recommendations
- Parallel scanning with proper timeouts for efficiency
Across 1,095 recent network scans, 43.6% have at least one externally-reachable port that should be closed.
Implementation examples
Once you've identified the gap, applying the fix is straightforward. Here are the three configurations developers reach for most often to close an unwanted port.
Linux host firewall (ufw)
# Default-deny inbound, allow only what you need
sudo ufw default deny incoming
sudo ufw default allow outgoing
# Public web traffic
sudo ufw allow 80/tcp
sudo ufw allow 443/tcp
# SSH only from a trusted admin range
sudo ufw allow from 203.0.113.0/24 to any port 22 proto tcp
# Explicitly close a previously exposed database port
sudo ufw deny 3306/tcp
sudo ufw enableAWS Security Group (Terraform)
resource "aws_security_group" "web" {
name = "web-sg"
description = "Public web only; admin scoped to office IP"
vpc_id = var.vpc_id
ingress {
from_port = 443
to_port = 443
protocol = "tcp"
cidr_blocks = ["0.0.0.0/0"]
}
ingress {
from_port = 22
to_port = 22
protocol = "tcp"
cidr_blocks = ["203.0.113.10/32"]
}
egress {
from_port = 0
to_port = 0
protocol = "-1"
cidr_blocks = ["0.0.0.0/0"]
}
}GCP firewall rule (gcloud)
# Allow only HTTPS from anywhere
gcloud compute firewall-rules create allow-https \
--network=default \
--direction=INGRESS \
--action=ALLOW \
--rules=tcp:443 \
--source-ranges=0.0.0.0/0
# Restrict SSH to a known admin CIDR
gcloud compute firewall-rules create allow-ssh-admin \
--network=default \
--direction=INGRESS \
--action=ALLOW \
--rules=tcp:22 \
--source-ranges=203.0.113.0/24
# Deny direct access to the database tier
gcloud compute firewall-rules create deny-db-public \
--network=default \
--direction=INGRESS \
--action=DENY \
--rules=tcp:3306,tcp:5432,tcp:6379,tcp:27017 \
--source-ranges=0.0.0.0/0Tool-specific questions
Is this port scan intrusive or harmful?
Why do some ports appear open intermittently?
Which ports are most commonly targeted by attackers?
What's the difference between open and filtered ports?
How often should I scan for open ports?
What should I do if I find unexpected open ports?
Can I use this scan for compliance auditing?
What's the best way to secure database ports?
How does the risk categorization system work?
Built for the engineers who already have enough to fix.
Real-time results
Comprehensive checks
Step-by-step fixes
More free checks, for the rest of your surface.
Complete Security Scan
Pre-Pentest Security Scan
Security Compliance Checker
WAF Checker
Security Headers Test
TLS/SSL Security Checker
Frequently asked.
What is Barrion and how does it enhance website security?
How safe is Barrion to use for security testing?
What types of security issues does Barrion identify?
What specific security checks does Barrion perform?
What is Barrion's smart crawling?
How often does Barrion perform security scans?
Is Barrion suitable for security testing of all business sizes?
How does Barrion handle data security and privacy during security testing?
What if I'm not satisfied with Barrion's security testing service?
How does Barrion help with SOC 2, ISO 27001, NIS2, and other compliance frameworks?
Anything else? Email contact@barrion.io.
Run a full report on your site.
Free first scan covers every check, no signup needed. Sign up to save the report and turn on continuous monitoring.