Security · Compliance · AI visibility
Raksha security
Start with a free website security scanner. Raksha checks transport security, headers, cookies and public exposure. Search and AI visibility appear separately from security findings.
Raksha security scan: what it is
A passive scan inspects publicly accessible responses from a website you are authorised to test. It checks HTTPS, browser security protections, cookie settings and signs of exposed files. It does not sign in, exploit the site or inspect private code and databases. A missing safeguard is not, by itself, proof that someone can steal data.
Illustrative example — not a live scan result
From an observation to a fix
- You enter a site you control, shown here as https://example.com, and confirm authorisation.
- Suppose its HTTPS response has no Strict-Transport-Security header. That is hardening guidance, not proof of a compromised account. A reachable /api/health page alone is not a vulnerability either.
- Review the affected URL, response evidence and recommended change. The security summary reflects security results; search and AI visibility checks stay in the separate Web Health report.
- Apply an appropriate HSTS policy, then scan again or use a supported issue re-check to see whether the same observation remains. No score is claimed for this example.
Authorised penetration testing
Penetration testing sends controlled active probes to investigate weaknesses within an agreed scope. Guided runs use defined tests; autonomous runs follow leads and record their actions. Neither is an unrestricted attack or a guarantee that every weakness will be found.
Before a pentest, create and sign an engagement and prove ownership with a DNS TXT record, an HTTP verification file or an HTML meta tag. Ownership is rechecked before the run. Scope, blocked paths, request budgets and testing windows constrain requests; a stop control lets you interrupt testing. Staff-admin access does not remove pentest ownership checks.
Compare a scan with guided and autonomous pentests →40+
Passive checks
5
Severity levels
6
AI visibility metrics
<60s
Average scan time
What gets checked
Every check in the free scan is read-only. Raksha never fuzzes, exploits or attempts to bypass authentication on your target unless you sign an engagement for a pentest. See everything Raksha tests.
Transport & TLS
HTTPS reachability, redirect chain, HSTS strength.
Security headers
CSP, frame options, nosniff, referrer and permissions policy.
Cookies & CORS
Secure, HttpOnly, SameSite flags and cross-origin exposure.
Attack surface
Exposed .env, .git, robots, sitemap, security.txt.
Technology fingerprint
Stack, CDN and version banners leaking from responses.
AI visibility
llms.txt, structured data, GPTBot / ClaudeBot / PerplexityBot rules.
How the scores work
Your Security Score starts at 100 and drops by weighted penalties for every finding — critical issues cost the most, informational notes barely register. The same input always produces the same score, so you can track progress across scans.
Your AI Visibility Score blends citation coverage, answer-engine optimisation, generative-engine optimisation, classic SEO, entity coverage and content authority.
See the score calculation and worked example →Free scan vs full report
- Free — score, severity breakdown and your four most urgent findings.
- $19 — every finding with evidence, remediation and the full AI visibility report.
- From $29/month — monitoring, history, scheduled scans and alerts.
Website security guides
Compare free tools, understand testing costs and choose between a scan and an authorised penetration test.
Browse all five guides →