How it works
Check your website with a free, passive Safe Scan, or a paid Deep / Active Scan once you have proved you own the domain, or keep it protected every day with Security Care.
The three ways to check your site
Free Safe Scan
US$0 · freePassive checks of headers, TLS, cookies, DNS and recent-CVE surface. A safety score in about a minute, nothing attacked.
Run it freeDeep / Active Scan
US$45 · one-offOwnership-verified multi-module scan: nuclei across discovered URLs, TLS & JS-secret checks, CORS/CSP depth, subdomain intel, and an OWASP-mapped fix-first report. Automated — not a human pentest.
Order Deep ScanSecurity Care
US$35 / monthStay safe at all times. We keep watching your site after the first scan: a Safe Scan every day, a Deep Scan every week, and our checks updated every 24 hours, so new threats are covered as they appear.
- Daily safe checks and weekly deep scans of your verified site
- Always up to date: scanner templates and threat list refreshed daily
- A friendly alert when something new appears, plus a monthly report
From your address to a locked-down site
Enter your site
Type the address and confirm you own it or are authorized to test it.
Safe Scan
Gentle, read-only checks: headers, TLS, cookies, exposed paths, DNS and known-CVE surface.
Clear risk report
A score and every finding ranked, explained in plain English with a fix.
Deep Scan & lock down
Verify your domain, and the paid active scan probes deeper so you can close the gaps.
Safe Scan (free)
- You enter a public URL and confirm you are authorized.
- Bro fetches the page (SSRF-safe), checks TLS, headers, cookies, a short list of sensitive paths via GET only, DNS email records, and known-CVE surface from advertised versions.
- You get a scored HTML report. No account required.
We check against the latest critical CVEs we track, currently PHP2Shell and eMudhra compromised CAs. Our list updates every day: see all current threats.
Deep / Active Scan (paid)
- You order and pay.
- We give you a unique token. Publish it as a DNS TXT at _lordevo-verify.yourdomain or as a file at /.well-known/lordevo-verify.txt.
- Open /verify (or we check from admin). The scan will not start until verification succeeds.
- We run the Safe Scan baseline, lightly discover same-host URLs (robots/sitemap/links), then nuclei (critical→low; dos/fuzz/intrusive excluded) across that URL list — plus a targeted pass when a CMS/framework is detected. Deep-only modules then check TLS depth, public JS for secrets (redacted), CORS/CSP, open redirects, and passive subdomain intel. Optional nikto / ZAP / light nmap when installed.
- You receive the report by email (PDF plus an HTML copy), usually within about 1 hour of verification: executive summary with fix-first items, OWASP Top 10 mapping, scan inventory, severities, remediation, nuclei version/template date, and recent-threat coverage. Automated scanners only — not a human penetration test.
Security Care (monthly)
- You subscribe (US$35 a month) and verify your domain once, the same DNS TXT or file check as the Deep Scan. We keep the verification on file for the subscription.
- Every 24 hours we refresh our knowledge base: nuclei templates, our list of recent CVEs (such as PHP2Shell) and incident data (such as the eMudhra CA list), plus the public list of vulnerabilities known to be exploited.
- Every day your site gets a Safe Scan; every week, a Deep / Active Scan (only on the verified domain).
- We compare each result with the last one. If a new vulnerability or exposure appears, we email you a short, plain-English alert with the fix.
- Once a month you get a security report: what changed, what was fixed, and what is still open.
Optional: code security review (included)
With a Deep Scan or Security Care you can also connect one GitHub repository, at no extra cost. It is optional and separate from the domain check.
- After payment, open the code review page from your order (or /code-review) and paste a GitHub fine-grained token limited to that one repository with Contents: Read-only. We only read; we never push, open pull requests or change settings. The token must come from an account that maintains the repository, so nobody can order a review of someone else's code.
- We download one commit, check it for committed secrets on our own server, then an AI model (Anthropic Claude or OpenAI Codex) reviews the most security-relevant files for flaws that cross a real trust boundary: injection, broken access control, auth and session bugs, SSRF, unsafe file handling, crypto and secret mistakes, risky CI workflows. A different model then tries to disprove each finding, and we check every cited file and line exists.
- Findings are added to your report with severity, the exact file and line, and the smallest fix. Leads that depend on something we can't see in the code (your hosting, a proxy) are listed separately without a severity.
Be clear on what it is: a single-pass, source-only review. We do not build, run or attack your code, larger repositories are only partly covered (the report lists every file reviewed and not reviewed), and AI reviews can miss issues or be wrong. Reviews run in a queue, so connect the repository before you verify your domain if you want it in the same report; otherwise it follows separately. The method is adapted from Cloudflare's open-source security-audit skill (MIT licence); Lordevo is not affiliated with Cloudflare. For one-off orders we delete your token as soon as the review finishes; you can disconnect at any time.
What “active” means
Automated vulnerability scanners send crafted requests to detect known issues. We do not run exploits against your data, brute-force logins, or flood your site. Still, scanners can occasionally trigger application errors, so only scan systems you are allowed to test.
Our scanner identity
Requests identify as LordevoPentestBot/1.0 (+https://pentest.lordevo.com/how-it-works).