A scan is a photo.Monitoring is the film.
We scan your domains, servers and web applications for known vulnerabilities and misconfigurations, without exploiting them. You can buy one scan, or monitored scanning that also checks every vulnerability published each day against your assets.
- Medium TLS 1.0 still accepted
- Low HSTS header missing
- Medium Admin login reachable from the internet
- High Web server version with published CVEs
What one asset means
The price is per asset. An asset is one domain or one subdomain. A domain does not include its subdomains: each subdomain is an extra asset.
So a shop at northwind.example with shop. and app. subdomains is three assets.
- northwind.examplethe domain
- shop.northwind.examplea subdomain, counted on its own
- app.northwind.exampleanother subdomain
One scan, or a scan that keeps watching
Choose how often we look at your asset.
- One full scan of the asset
- Report with evidence and fix steps
- One retest after you fix
- Vulnerabilities published after the scan
Prices per asset, before VAT. Monitoring is sold for 1 or 3 years, paid up front.
Why monitoring is worth more than a scan
A scan shows your asset on the day it ran. New vulnerabilities are published every day, your team deploys, a certificate gets closer to expiry. The report stays the same. Your exposure does not.
Between full scans, monitored scanning checks every newly published vulnerability against your assets. You choose how often the full scan runs: monthly, weekly or daily, per asset. The more often it runs, the less each scan costs you.
Before VAT. The daily check of new vulnerabilities, alerts and rescans after a fix are included.
Eight weeks of one asset
- Medium Outdated JavaScript library
- Low HSTS header missing
- Week 1
First scan: 2 findings
- Medium Outdated JavaScript library
- Low HSTS header missing
- Week 2
Rescan, nothing new
- Medium Outdated JavaScript library
- Low HSTS header missing
- Week 3
A CVE is published for your web server. Alert sent the same day.
- Medium Outdated JavaScript library
- Low HSTS header missing
- High New CVE for the web server version
- Week 4
The High is still open. Reminder sent.
- Medium Outdated JavaScript library
- Low HSTS header missing
- High New CVE for the web server version
- Week 5
A deploy exposes the admin login. Alert sent.
- Medium Outdated JavaScript library
- Low HSTS header missing
- High New CVE for the web server version
- Medium A deploy exposes the admin login
- Week 6
You patch the server. The rescan confirms the fix.
- Medium Outdated JavaScript library
- Low HSTS header missing
- High New CVE for the web server version
- Medium A deploy exposes the admin login
- Week 7
Rescan, nothing new
- Medium Outdated JavaScript library
- Low HSTS header missing
- High New CVE for the web server version
- Medium A deploy exposes the admin login
- Week 8
Rescan, nothing new
- Medium Outdated JavaScript library
- Low HSTS header missing
- High New CVE for the web server version
- Medium A deploy exposes the admin login
Sample data. Names, addresses and values are fictional.
What one scan looks at
- Known vulnerabilities
- Versions of web servers, frameworks, CMS and plugins, matched against public vulnerability databases.
- Misconfigurations
- Open ports, default admin panels, directory listing, missing security headers and weak TLS settings.
- Web application flaws
- Injection points, exposed files and unsafe cookie or redirect settings that can be confirmed without exploiting them.
- Certificates and DNS
- Certificates close to expiry and DNS records that leave the domain open to abuse.
How it runs
- 1AuthorizeYou confirm in writing which assets we may scan. Nothing runs without it.
- 2ScanThe scan runs against production. Nothing is exploited and nothing is changed.
- 3FilterResults are filtered for false positives before they reach you.
- 4ReportFindings land in your 4Tify dashboard with a CVSS score, evidence and fix steps.
What you get back
- Every finding in your dashboard, with severity and CVSS score
- Evidence and fix steps your IT team can act on
- A report you can export for management or an auditor
- One retest included; with monitoring, a rescan after every fix
Questions we get asked
What is the difference between a vulnerability scan and a pentest?
A scan checks your assets for known vulnerabilities and misconfigurations, without exploiting them. A pentest is manual: a specialist links weaknesses into a real attack path. Many companies keep monitoring all year and add a pentest once a year.
Will the scan affect my website?
The scan looks for known issues and does not exploit what it finds, so it does not change your data. It runs on production, because that is what attackers see.
What counts as one asset?
A domain is one asset, and each subdomain is counted on its own. A company with its site, a shop and a client portal on three subdomains has three assets to scan.
What happens when a new vulnerability is published?
With monitoring, every vulnerability published each day is checked against your assets. A one-off scan only shows what was true on the day it ran.
Do I have to prove I own the domain?
Yes. We only scan assets you have verified with a DNS record or authorised in writing. Nobody can point our scanner at a site that is not theirs.
Where to next
Tell us what you run. We will scope it with you.
Request a scan