Web security
Your website, tested the way attackers look at it
Most breaches of small and mid-size sites do not need anything clever: an outdated plugin, a forgotten backup file, a weak TLS setting. Automated testing finds those before someone else does.
What a penetration test covers
Encryption
TLS versions and ciphers, certificates, HSTS and redirects to HTTPS.
Browser defences
Security headers, cookie flags, framing and content-type protection.
Known vulnerabilities
Software versions matched against published vulnerabilities (CVEs), rated with CVSS.
Exposed content
Backups, config files, admin panels and directory listings left public.
Attack surface
Open ports, services and subdomains that answer from the internet.
Change over time
Each run is compared with the last: new, fixed and returning findings.
Why once is not enough
A penetration test is a snapshot. The day after it, a new version of your CMS is released, a plugin gets a published vulnerability, someone changes the server configuration. None of that shows up in last month's report.
Continuous testing re-runs the full test every month on your verified domains, with the newest tests added. You see what is new, what you fixed, and what came back after an update.
Testing needs permission. That is why it only runs on domains you have verified: see how verification works.