Website security · Raksha guide

How to Check Your Website Security for Free

Start with a read-only check of the public website, then review what was actually observed. Raksha’s free website security scanner is a first look at public exposure—not proof that every part of your application is secure.

By Raksha · Reviewed 16 November 2026

How to run a security scan in six steps

  1. 1.

    Confirm the target and your permission

    Use the exact website you control, including the intended hostname. Do not scan an unrelated business, customer or production system without explicit permission. Review any restrictions from your hosting provider.

  2. 2.

    Enter the address in Raksha

    Open the free scanner, enter an HTTPS address and confirm authorisation. No card is needed for the free check. Sign in and confirm your email if prompted; free usage and safety limits still apply.

  3. 3.

    Verify ownership when requested

    In Projects and assets, add the target and select Verify. Choose a DNS TXT record, an HTTP file or an HTML meta tag, place the supplied proof and check verification. Ordinary staff-admin scans may bypass this; pentest ownership proof is still mandatory.

  4. 4.

    Run the passive check

    Follow progress in Scans. Raksha reads public responses to inspect HTTPS behaviour, security headers, cookies and signs of exposed files or secrets. Scan duration varies with response times, queueing and coverage; there is no guaranteed 60-second completion.

  5. 5.

    Read the evidence, not only the score

    Review the affected resource, observed response, severity, confidence and proposed fix. A missing header alone is not proof of data theft. Search and AI visibility belong in Web Health, not the security finding count. The free view is limited; check Pricing for full-report access.

  6. 6.

    Fix the cause and check again

    Make the relevant application or hosting change, then run a new scan or a supported issue re-check. Compare the evidence and the checks that actually ran. If a check failed or was skipped, investigate it rather than assuming the target passed.

Worked example: a missing HSTS policy

Imagine a site you own redirects HTTP to HTTPS but its HTTPS response does not include Strict-Transport-Security. This is an illustrative example, not a Raksha live result. The observation describes a missing browser protection; it does not establish that an attacker accessed an account.

Check whether all affected subdomains support HTTPS before choosing a policy. Apply the appropriate header, verify the served response and scan again. Do not enable subdomain coverage or preload blindly: those choices can affect services that are not ready for HTTPS.

What a free check cannot see

  • Private database rules, source code or cloud permissions without a separately connected review.
  • Logged-in workflows or whether one user can access another user’s records.
  • All JavaScript-rendered pages, vulnerable execution paths or container-layer packages.
  • Complex business-logic attacks or every compromise on a host.

Raksha does not provide malware removal. A clean public scan is not a replacement for incident response if you suspect a compromise.

When should you go deeper?

Use connected code and database reviews when the question concerns permissions, secrets or internal controls. Arrange authorised testing for active probes, and a human-led assessment for complex workflows. Paid access does not automatically remove technical coverage limits.

Compare vulnerability scanning with penetration testing

Common questions

Is the free check unlimited?

No. Free usage limits and ownership requirements apply; it is not an unlimited active-testing service.

Does a high score mean the site is safe?

No. A score summarises the observations included in that run. Review coverage and separately assess login, data access and private systems.

Start with a site you are authorised to test

A free passive check needs no card. Sign-in, email confirmation, ownership rules and usage limits apply. It is not an unrestricted penetration test.