Security

Website security analysis
what’s reviewed and why it matters

A website’s security is everything that protects the people who visit it and your business: an encrypted connection, nobody able to pass themselves off as you, and a website that doesn’t give away more than it should. Wakaris reviews it with 30 checks and explains every finding in plain language.

  • 30 checks
  • 10 possible findings
  • 10 guides
What’s reviewed

What Wakaris checks
in your website’s security

That’s 30 checks grouped into 10 blocks. Each block is a finding that can show up in your report.

Finding01/ 10

Blocks6 checks

HTTPS secure connection

It’s the only thing on this list visitors see for themselves: a “not secure” warning in the browser bar kills the sale before anyone reads anything.

What it checks

  • Valid SSL certificate + expiryChecks that the TLS certificate is valid and how long until it expires. Limits if it’s close to expiring; blocks if it’s expired, invalid or the connection isn’t trustworthy.
  • Trusted certificateChecks that it belongs to a chain recognized by mainstream browsers. Blocks if it isn’t trusted or the chain is invalid.
  • HTTP to HTTPS redirectChecks what happens when the same address is requested over HTTP. No finding if it redirects straight to HTTPS; limits if it gets there through an unnecessary chain of redirects; blocks if it stays on HTTP.
  • Consistent www redirectChecks that the www and non-www variants lead to a single consistent version. Blocks if both remain reachable inconsistently or one fails.
  • Mixed contentChecks whether an HTTPS page loads images, scripts, CSS or other resources over HTTP. Blocks if there’s active mixed content.
  • TLS versionsChecks which protocol versions the server supports. Limits if it keeps an old one for compatibility; blocks if it supports obsolete protocols considered insecure.
Read the guide: HTTPS secure connection 

Finding02/ 10

Blocks2 checks

PHP vulnerability 2026 (PHP2Shell)

PHP is the language many websites run on. A version with security flaws that have already been fixed leaves a door open, and there’s a way to close it: updating.

What it checks

  • PHP versionIf the server says which PHP version it uses, we check that it includes the security fixes already published.
  • How to find out your PHP versionIf the version can’t be seen from outside, the report gives you the steps to check it or to ask your hosting provider. It doesn’t count against you.
Read the guide: PHP vulnerability 2026 (PHP2Shell) 

Finding03/ 10

Blocks2 checks

nginx vulnerability 2026 (NGINX2Root)

nginx is one of the most widely used programs for serving websites. A version with security flaws that have already been fixed leaves a door open, and there’s a way to close it: updating.

What it checks

  • nginx versionIf the server says which nginx version it uses, we check that it includes the security fixes already published.
  • How to check your nginxIf the version can’t be worked out from outside, the report gives you the steps to check it. It doesn’t count against you.
Read the guide: nginx vulnerability 2026 (NGINX2Root) 

Finding04/ 10

Limits7 checks

Security headers

They’re defenses that cost nothing and that almost no website has in place. They don’t fix a specific flaw: they limit what can be done with one when it shows up.

What it checks

  • HSTSChecks whether the server forces the browser to use HTTPS on later visits. Limits if it exists but is misconfigured; blocks if it’s missing.
  • Content Security PolicyChecks whether there’s a policy limiting which origins resources can be loaded or run from. Limits if it’s too permissive or incomplete; blocks if it’s missing.
  • Framing protectionChecks whether third parties are prevented from embedding the page in a frame, which reduces the risk of clickjacking. Limits if the protection is partial or outdated; blocks if there’s none.
  • MIME sniffingChecks X-Content-Type-Options: nosniff, which stops the browser from interpreting a file as a type other than the one declared. Blocks if it’s missing.
  • Referrer PolicyChecks which part of the URL is sent to other sites in the Referer header. Limits if the policy is overly permissive; blocks if it’s clearly insecure.
  • Permissive CORSChecks whether the CORS policy lets any origin read the server’s responses. Limits if it’s broadly open but bounded; blocks if any origin is allowed together with credentials.
  • Permissions PolicyChecks whether access to browser capabilities like camera, microphone or geolocation is controlled. Limits if the policy is partial; blocks if it leaves sensitive capabilities open for no reason.
Read the guide: Security headers 

Finding05/ 10

Limits3 checks

Technical information exposure

Knowing you use WordPress is no use to anyone. Knowing you use version 6.1.1 is: with that, someone can look up the list of known flaws for that version and try only what works.

What it checks

  • Exposed CMS and versionChecks whether the HTML, headers or other public signals reveal the CMS and especially its version. Limits if the CMS is identifiable without a version; blocks if the specific version is needlessly exposed.
  • Exposed server and versionChecks whether responses reveal the server software and its version. Limits if it only reveals the generic technology; blocks if it exposes specific versions.
  • Exposed framework or technologyDetects public information that identifies frameworks or other components. Limits if the technology is identifiable; blocks if it exposes needless versions or specific details.
Read the guide: Technical information exposure 

Finding06/ 10

Limits1 check

Sensitive information exposure

A server error printed on the page isn’t just ugly. It says what language the site is built in, which file and line failed and where that file lives on disk. It’s the usual starting point for anyone looking for a way in.

What it checks

  • Exposed debug informationLooks for publicly visible errors, traces, internal paths or debug messages. Limits if it’s minor technical information; blocks if it exposes relevant traces, paths or internal configuration.
Read the guide: Sensitive information exposure 

Finding07/ 10

Limits3 checks

XSS risk

XSS is how a third party gets their code to run inside your website, with the permissions of whoever is viewing it: it can read what’s on screen, act on the visitor’s behalf or send them somewhere else.

What it checks

  • Parameter reflection in the HTMLEnters a harmless, unique string into parameters or forms and checks whether it comes back reflected unencoded. Limits if it’s reflected in a sensitive context without execution; blocks if it reaches an executable context and is confirmed.
  • Dangerous DOM sinksDetects use of innerHTML, outerHTML, document.write or insertAdjacentHTML with data from a controllable source. Limits if the function exists but its source isn’t shown to be controllable; blocks if the full flow is confirmed.
  • CSP protection against scriptsReuses the Content Security Policy result as mitigation context. It isn’t scored separately and doesn’t replace the two previous checks.
Read the guide: XSS risk 

Finding08/ 10

Limits2 checks

Email security

Without these records, anyone can send email with your domain as the sender. They don’t need to access anything: email works that way by design, and SPF and DMARC are what close it off.

What it checks

  • SPFQueries DNS. No finding with a single valid SPF record and a restrictive policy; limits if valid with ~all or ?all; blocks if missing, there’s more than one, the syntax is invalid or it uses +all.
  • DMARCQueries _dmarc.domain. No finding with a valid record and a quarantine or reject policy; limits with p=none; blocks if missing or invalid.
Read the guide: Email security 

Finding09/ 10

Limits1 check

Unverified third-party resources

Every script you load from another domain runs on your page with the same permissions as your own: it can read what the visitor types, change what they see and make requests on their behalf. You’re trusting that file to always be the same.

What it checks

  • Subresource IntegrityChecks scripts and stylesheets loaded from other domains and whether they declare the integrity attribute. No finding if all declare it or there are no external resources; limits if it’s missing on some; blocks if it’s missing on all.
Read the guide: Unverified third-party resources 

Finding10/ 10

Affects3 checks

Form protection

An unprotected form doesn’t get spam now and then: it gets hundreds of automated submissions a day, and the inbox where the notifications land stops being checked. The damage isn’t the spam, it’s the real message that gets lost in it.

What it checks

  • Forms presentDetects forms that let people enter and submit information, excluding simple search boxes. It’s context for applying the following checks and doesn’t create a problem on its own.
  • Anti-spam protectionChecks whether forms include a CAPTCHA, honeypot or other identifiable mechanism. Limits if the mechanism is doubtful or partial; blocks if the form can be automated with no detectable protection.
  • Secure form submissionChecks that the data isn’t sent to an insecure HTTP destination. Limits if the behavior is inconclusive; blocks if it’s explicitly sent over HTTP.
Read the guide: Form protection 

The label tells you how much each finding weighs: Blocks critical,Limits important,Affects could be better.

Why it matters

Why your website’s security
matters

Security isn’t only about attacks: it’s about your website staying a place people can trust.

  • Protects your visitors

    Anyone who fills in a form or buys on your website is trusting you with their data. If the website doesn’t look after it, they take the risk and you carry the responsibility.

  • Upholds your reputation

    A browser warning or a website that behaves oddly gets noticed on the very first visit. Trust that takes years to earn can be lost in a moment.

  • Spares you costly scares

    Keeping your website up to date usually costs far less than recovering it after a problem: hours offline, sales that never arrive and explanations to your customers.

To understand it

Security guides
one for each finding

Each guide explains one finding from this area in plain language: what it is, how it’s measured, why it matters to you and how to fix it. The technical part is kept separate, for whoever looks after your website.

10guides on security

See the 10 guides
Frequently asked questions

Common questions
on security

Does Wakaris try to break into my website to analyse its security?

No. The analysis is passive: it only reads what your website already makes public, such as its certificate, the headers the server sends, the page’s code or your domain’s records. It doesn’t try passwords, it doesn’t send anything that could affect your server and it doesn’t need you to give it access.

How is it different from a penetration test?

In a penetration test, a person tries to get into your system with your permission and also reviews what can’t be seen from outside. Wakaris looks at what anyone can see without permission, which is where you start: it helps you close the obvious gaps and know what to ask of whoever looks after your website. If you handle sensitive data, it doesn’t replace an in-depth review.

My website already has the padlock. Is it secure?

The padlock only says that the connection to your website is encrypted. It says nothing about security headers, about whether your website reveals the version of its software, about whether your forms are protected or about whether someone can send email in your name. That’s why the secure connection is one of the 10 blocks and not the only one.

My website is small. Would anyone really be interested in it?

A person, maybe not. But a good share of attacks are launched by automated programs that go through websites one by one looking for known flaws, without caring whose they are. A small website with out-of-date software is just as reachable as a big one.

Who has to fix whatever comes up?

Usually whoever looks after your website or your hosting provider. Every finding comes explained, with the evidence that proves it and a ready-made prompt to fix it with an AI, and you can share it with a link. Several are solved with a settings change, without touching the website’s content.

How much does the security analysis cost?

Nothing. Analysing a page is free, asks for no sign-up or card and gives you the result in a few seconds. Security is reviewed alongside the other eight areas in the same analysis.