Vorpsel / Platform / Exposure
Network Scan
See your servers the way an attacker on the internet sees them: every open port, the program and version behind it, and the known flaws that program has, tested from the outside and reported only when the evidence holds.
At a glance
- Every TCP port from 1 to 65535, plus the UDP services that matter when exposed
- Services and versions and the operating system, found on each address
- Safe by default nothing built to take a service down ever runs
- Written permission confirmed by our team before the first scan
From an address to a finding
You give a domain, an address or a range. The scan walks the same path an attacker would, one step after the other, and keeps what each step learned for the next one.
Resolve
A domain is scanned on every address it points to at that moment. Private and cloud metadata addresses are refused.
Ports
Every TCP port is checked, and the UDP services that are dangerous to leave open.
Services
Each open port is identified: the protocol, the program, its version and the operating system.
Tests
Only the tests that apply to what was found run, so a web server is not tested as a mail server.
Findings
Each flaw comes with its severity, the CVEs, the evidence and how to fix it.
Every port, not the usual thousand
Many scans stop at the first 1,024 ports. Databases, admin panels and forgotten test servers usually listen much higher, and that is where exposures hide. Vorpsel checks the whole range by default.
- 3306 database
- 8443 admin panel
- 11211 cache
- 27017 document database
- 50000 application server
The green strip is where most scans stop. The UDP services checked by default:
Choose how deep it goes
Each scan has a profile. Start with a quick map of what answers, or go all the way to every test on every port.
Hosts and ports
Which addresses answer and which ports are open. Nothing else.
Discovery
Open ports, services, programs and versions, and the operating system. No vulnerability tests.
Full
The usual choice
Every external test that applies to what was found on each port.
Full and deep
Every external test against every open port, even where the service was not recognized. Finds services on unusual ports and takes several times longer.
Made to run against production
A scan of your own servers should never become the incident. The limits below are built into the scanner, not left to a setting someone may forget.
Always
- Safe checks on by default. Tests that could disrupt a service run in a form that does not. Turning this off needs an explicit confirmation.
- Permission first. No scan runs before our team confirms your written permission for the targets.
- A time limit. From 1 to 24 hours. A run that reaches it stops and keeps what it found.
Never
- Denial of service. Tests that exist only to take a service down are not part of the scanner.
- Password guessing with lists. No brute force against your logins, ever.
- Private networks. Private, local and cloud metadata addresses are refused when the scan is created and again when it runs.
- Addresses you left out. Exclusions inside a range are respected on every run.
70The minimum reliability a result needs to become a finding, by default.
Fewer findings you have to doubt
Every result carries a reliability score that says how it was reached. You choose the floor, and anything below it never reaches your list.
- 70
Reliable
Confirmed by a test, or by a version the vendor lists as vulnerable. The default.
- 80
Strict
Leaves out findings inferred only from indirect signs.
- 95
Confirmed only
Only what a test proved by checking the flaw itself.
Written permission, checked by a person
Scanning an address you do not own is an attack. So before the first run, our team confirms that you are allowed to scan the targets you entered.
You
- Enter the domains, addresses and ranges, up to /24 per range.
- Confirm that you have written permission to scan them.
- Change the targets whenever you need. The scan goes back to review.
Vorpsel
- Checks the permission and records its reference.
- Sets how long it is valid, up to one year.
- Or refuses it, with the reason, so you know what to send.
After the first scan
Schedules
Run on demand, every few hours, daily, weekly or monthly.
Findings that close themselves
When a complete run no longer finds a flaw, it is marked as fixed. A run cut short by its time limit never closes older findings.
An inventory of what answers
Every address with its open ports, services, versions and operating system, kept up to date by each run.
Websites on shared addresses
Names found for an address, in its certificate for example, are tested too.
Frequently asked questions
Can it scan my internal network?
No. Network Scan looks at what is exposed to the internet. For the inside of each machine, the Vulnerability Management agent reads the software directly, without a network scan.
Will it slow down or break my servers?
Safe checks are on by default and nothing built to take a service down ever runs. Every scan also has a time limit you set.
Why do I need to give written permission?
Because a scan of an address you do not control is an attack on someone else. The check protects the owners of those addresses and protects you.
How long does a scan take?
It depends on the number of addresses, the open ports and the profile. A single server with the full profile usually takes well under an hour; every scan has a time limit you set.
How is it priced?
By the number of addresses scanned in the month. Talk to our team for a quote.
Related modules
Find out what your servers show the internet
Enter your public addresses and confirm the permission. The first scan runs as soon as our team checks it.