Create account

Methodology

What the scanner checks and how the score comes about

This page is generated from the same code that scores every scan. The groups, categories, points and checks below are the ones in use right now.

Scan a website

01 Scope

What is checked

6 of 20 categories are active with 93 individual checks. Active groups: Security, Accessibility. The remaining categories are built but dormant: they are not checked and do not count towards any score.

Scoring version 102. Every change to the categories, points, factors or checks raises this number, and stored scans are scored again under it the next time they are opened.

Security

Counts twice in the website score 66.7 % of the website score

Security = (2 × Transport security + 2 × Protective headers + Cookie attributes + Domain & mail security + Information exposure) / 7

Transport security

Counts twice in the group 28.6 % of the group score 17 checks in 6 bundles, 100 points
HTTPS available and enforced
24 points
  • Site reachable over HTTPS 16 points
    Tests whether the site opens over an encrypted connection at all, so that what visitors send and receive cannot be read on the way.
  • Redirect from HTTP to HTTPS 8 points
    Tests whether a request over unencrypted HTTP is moved onto an encrypted connection.
Certificate
24 points
  • Certificate validity 6 points
    Tests whether the certificate is valid right now and not about to expire.
  • Certificate host name 6 points
    Tests whether the certificate is actually issued for the host name that was scanned.
  • Certificate trust chain 6 points
    Tests whether the certificate can be verified against the public trust store.
  • Certificate key strength 4 points
    Tests whether the key in the certificate is long enough to still count as safe.
  • Certificate signature algorithm 2 points
    Tests whether the certificate is signed with an algorithm that still counts as safe.
HSTS
16 points
  • Strict-Transport-Security header 6 points
    Tests whether the site tells browsers to use HTTPS for every later request, so a connection cannot fall back to an unencrypted channel.
  • Effect of the transport security policy 4 points
    Tests whether the transport security policy reaches the browser at all: it only takes effect on the encrypted final page, not on an unencrypted response or on the redirect alone.
  • Lifetime of the HSTS policy 4 points
    Tests whether the declared lifetime of the transport security policy is long enough to have an effect.
  • HSTS preload state 2 points
    Tests whether the domain is on the browser preload list and whether the header agrees with that state.
TLS version and encryption
16 points
  • Negotiated TLS version 6 points
    Tests which TLS version the browser actually agreed with the server while loading this page.
  • Outdated TLS versions 4 points
    Tests whether the server still accepts TLS 1.0 or TLS 1.1, versions that count as broken.
  • Cipher strength 4 points
    Tests whether the server accepts a connection that uses ciphers which count as weak.
  • Current TLS version 2 points
    Tests whether the server offers TLS 1.3, the current version of the protocol.
Forms encrypted
10 points
  • Form submission over HTTPS 10 points
    Tests whether the forms on the pages checked send their data to an encrypted address instead of to plain HTTP.
No mixed content
10 points
  • Mixed content 10 points
    Tests whether an encrypted page loads any of its own resources over an unencrypted connection.

Protective headers

Counts twice in the group 28.6 % of the group score 23 checks in 5 bundles, 100 points
Content Security Policy
42 points
  • Content-Security-Policy 14 points
    Tests whether the page sends a content security policy at all. How far the policy limits which scripts, styles and frames the page may load is judged under "Strength of the content security policy".
  • Content security policy enforced 14 points
    Tests whether the policy is enforced or only reported, because a report-only policy blocks nothing.
  • Strength of the content security policy 8 points
    Tests whether the policy really constrains scripts, instead of letting everything through a broad directive.
  • Delivery of the content security policy 6 points
    Tests whether the policy arrives as an HTTP header, which covers more cases than a policy placed in the page markup.
Framing and content types
17 points
  • X-Frame-Options header 5 points
    Tests whether other sites are kept from embedding the page in a frame, a common clickjacking indicator.
  • Value of the X-Frame-Options header 3 points
    Tests whether the framing rule uses a value that current browsers still honour.
  • X-Content-Type-Options header 5 points
    Tests whether the response pins the content types it declares, so a browser does not guess a different one.
  • Value of the X-Content-Type-Options header 4 points
    Tests whether the header carries nosniff, the only value that has any effect.
Referrer and permissions
13 points
  • Referrer-Policy header 4 points
    Tests whether the site limits which address information is passed on when a visitor follows a link to another site.
  • Strength of the referrer policy 3 points
    Tests whether the chosen referrer policy really withholds the address instead of passing the full URL on.
  • Permissions-Policy header 4 points
    Tests whether access to powerful browser features such as camera, microphone and location is explicitly restricted.
  • Coverage of the Permissions-Policy 2 points
    Tests whether the policy actually names the sensitive browser features instead of staying empty.
Cross-origin isolation
10 points
  • Cross-Origin-Opener-Policy header 2 points
    Tests whether the page separates its browsing context from windows it opens and from windows that open it.
  • Value of the Cross-Origin-Opener-Policy 2 points
    Tests whether the value actually separates the browsing context instead of naming the browser default under a header name.
  • Cross-Origin-Resource-Policy header 2 points
    Tests whether the site states which other origins may embed its resources.
  • Value of the Cross-Origin-Resource-Policy 2 points
    Tests whether the value restricts who may embed the response instead of allowing every origin.
  • Cross-Origin-Embedder-Policy header 1 point
    Tests whether the page requires embedded resources to opt in before they are loaded.
  • Enforcement of the Cross-Origin-Embedder-Policy 1 point
    Tests whether the embedder policy is in force or only reports what it would have blocked.
Further protective headers
18 points
  • CORS configuration 7 points
    Tests whether the site opens its responses to any origin, in particular together with credentials.
  • Security headers beyond the start page 5 points
    Tests whether a second page of the same site answers with the same security headers as the start page.
  • Subresource integrity 3 points
    Tests whether scripts loaded from other sites carry an integrity hash, so an altered file is not executed.
  • X-XSS-Protection header 2 points
    Tests whether the site still sends the retired XSS filter header, which current browsers ignore and which used to cause problems of its own.
  • Reporting-Endpoints header 1 point
    Tests whether the site names an endpoint that browsers can report policy violations to.

Cookie attributes

Counts once in the group 14.3 % of the group score 4 checks in 2 bundles, 100 points
Secure and HttpOnly
71 points
  • Secure attribute on cookies 32 points
    Tests whether cookies are marked so that they are only ever sent over an encrypted connection.
  • HttpOnly attribute on cookies 39 points
    Tests whether cookies are withheld from scripts in the page, which limits what injected script code can read.
SameSite
29 points
  • SameSite attribute on cookies 10 points
    Tests whether cookies state whether they may travel on requests that start on another site.
  • SameSite=None without Secure 19 points
    Tests whether a cookie that allows cross-site use is at least limited to encrypted connections.

Domain & mail security

Counts once in the group 14.3 % of the group score 16 checks in 5 bundles, 100 points
Reputation
33 points
  • Reputation of the domain 33 points
    Tests whether Google Safe Browsing lists the domain as dangerous, which makes browsers warn visitors before the site opens.
No subdomain takeover
22 points
  • Names pointing at an unused hosting account 22 points
    Tests whether the scanned address or its www counterpart is directed by CNAME at a hosting platform whose target is free to be claimed, because it resolves nowhere or the platform answers with the page it shows for an unclaimed name. A CNAME onto such a platform is normal by itself and is not reported; only these two observations are.
Mail authentication
15 points
  • SPF record (mail domain) 7 points
    Tests whether the domain names in DNS which servers are allowed to send mail on its behalf.
  • DMARC record (mail domain) 5 points
    Tests whether the domain states in DNS how a receiving mail server should treat messages that fail authentication.
  • DKIM key (mail domain) 3 points
    Tests whether a DKIM key can be found under one of the common selector names, so outgoing mail can be signed and a forged sender is recognisable, and whether an RSA key there has at least 2048 bits. Only when no name exists under _domainkey at all is the key reported as missing; if something is published there under a selector of your own, the check stays unresolved.
Mail transport
10 points
  • Mail servers in the MX records exist 4 points
    Tests whether every mail server named in the MX records of the domain exists in DNS. A name the DNS answers with "does not exist" cannot receive mail; a mail server whose DNS gives no answer at all leaves the check unmeasured.
  • MTA-STS policy (mail domain) 3 points
    Tests whether the domain publishes a policy that requires encrypted transport for incoming mail.
  • TLS-RPT record (mail domain) 1 point
    Tests whether the domain names a place that receives reports about failed mail transport encryption.
  • DANE/TLSA record (mail domain) 1 point
    Tests whether the mail servers of the domain publish a TLSA record, which lets a sending server verify the certificate through DNSSEC. A TLSA record in a zone without DNSSEC fails the check, because no sending server uses a record it cannot validate. A missing record counts only where the zone of the mail server is signed; a mail server in an unsigned provider zone is out of reach for the site owner.
  • Mail servers over IPv6 1 point
    Tests whether at least one mail server of the domain publishes an AAAA record. Without a mail server in DNS the question does not arise and stays unmeasured.
Registration and DNS
20 points
  • Remaining registration period 10 points
    Tests how long the registration of the domain still runs, because an expired domain takes the website, the mail and every subdomain down at once. The date is only readable where the registry serves it over RDAP, which the generic domains do and the country code domains of this market do not; without it the check stays unmeasured and is never counted as a defect.
  • Nameserver redundancy 3 points
    Tests whether the zone is served by more than one nameserver, so a single failing server does not take the website, the mail and every subdomain down at once.
  • DNSSEC (web zone) 2 points
    Tests whether the DNS answers of the zone that serves the website are cryptographically signed. Where the website is an alias (CNAME) of another zone, that zone is tested and the chain is shown with the result.
  • CAA record (web zone) 2 points
    Tests whether the zone that serves the website limits in DNS which certificate authorities may issue certificates for it. Where the website is an alias (CNAME) of another zone, that zone is tested and the chain is shown with the result.
  • Website over IPv6 1 point
    Tests whether the scanned host publishes an AAAA record for visitors on an IPv6-only network. Whether a server answers at that address is the next check.
  • Website answers over IPv6 2 points
    Opens a connection to port 443 at up to three published IPv6 addresses of the scanned host until one of them answers. Without an AAAA record the question does not arise and the check stays neutral.

Information exposure

Counts once in the group 14.3 % of the group score 10 checks in 4 bundles, 100 points
Up-to-date software
40 points
  • Age of the software in use 24 points
    Tests whether the products the page names about itself, such as the content management system, the web server or a JavaScript library, are behind their current release. The check reads only what the page discloses of its own accord and reports nothing when no version is visible or the release reference is too old to judge against. A version built by a Linux distribution stays open, because the distribution brings security fixes into it without changing the number. The same holds for a build that another vendor, such as the content management system, has adapted and marked with a suffix behind the version number. A library loaded from a public CDN such as unpkg, jsDelivr or cdnjs is read off its address; where no release reference covers it and the vulnerability database lists nothing for its version, the check stays open as well. A self-hosted library is named by its file hash, its signatures, its licence head or the global it creates, whatever the file is called; one that is recognised but states no version keeps the check open, because its age cannot be judged.
  • Maintenance of the server platform 16 points
    Tests whether the server banner points to an operating system release or an OpenSSL line whose maintenance has ended. Only a banner that pins the release down is judged; where it names neither, the check reports nothing.
No leaks in the HTML
26 points
  • Internal information in the markup 24 points
    Tests whether the delivered markup contains error output, a directory of the server, an internal network address in a comment or a string with the shape of an access key. The check reads the markup that every visitor receives anyway and reports the kind of the find, never its wording.
  • Public source maps 2 points
    Tests whether the source maps of the own scripts of the page can be downloaded, which hand out the original source code and the server paths of the build.
Server configuration
24 points
  • Directory contents visible 8 points
    Tests whether a directory the page loads its own files from answers with a list of its contents instead of a page. Only directories derived from the resources of the page are asked, no addresses are guessed.
  • No directory contents visible on any page 8 points
    Runs only in the scan of a whole website and tests the directories of the files every scanned page loads. One directory that lists its files fails the website, because further pages bring further directories such as uploads or plugins.
  • Server version disclosed 3 points
    Tests whether the response names the exact version of the software that serves the site.
  • Technology disclosed in headers 3 points
    Tests whether the response names the software, framework or platform behind the site.
  • security.txt 2 points
    Tests whether the site publishes a contact point for security reports at the agreed address.
No suspicious content
10 points
  • Unusual content on the page 10 points
    Tests whether the delivered page contains elements that injected code typically leaves behind: an invisible frame that loads from another site, a script that decodes its own content before running it, or an automatic redirect to another site. Each of these has legitimate uses, so the check reports a pointer to look at rather than a verdict.

Accessibility

Counts once in the website score 33.3 % of the website score

Accessibility = (Accessibility (automated checks)) / 1

Accessibility (automated checks)

Counts once in the group 100.0 % of the group score 23 checks in 5 bundles, 100 points
Automated rules
15 points
  • Automatically detectable barriers 5 points
    Tests how many of the automated rules the page breaks, for example missing text alternatives, unlabelled controls or too little contrast. Each violation is a concrete place in the markup that can be repaired.
  • Automatically detectable barriers on a narrow screen 5 points
    Runs the automated rules a second time at a width of 320 pixels, where many sites switch to their mobile layout, and reports only what the desktop run did not already find. Collapsed menus and mobile controls often break the same WCAG rules as the desktop view, for example 4.1.2 (name, role, value).
  • Readable on a narrow screen 5 points
    Tests whether the content reflows into a narrow window instead of forcing the visitor to scroll sideways. People who enlarge the page or use a small screen otherwise lose part of the text on every line.
Keyboard
15 points
  • Keyboard focus visible 5 points
    Moves through the start page with the Tab key and compares each element with and without focus, and notes every element that receives the focus outside the visible area, for example in a closed menu. If nothing changes or the focus cannot be seen, keyboard users cannot see where they are (WCAG 2.4.7 focus visible); give every link and control a clear focus style.
  • No keyboard trap 5 points
    Tests whether the Tab key always moves the focus on. An element that keeps the focus locks keyboard users out of the rest of the page (WCAG 2.1.2 no keyboard trap).
  • Focused element not hidden 5 points
    Tests whether an element that receives keyboard focus within the visible area sits completely under a fixed header, a banner or another layer (WCAG 2.4.11 focus not obscured). An element that receives the focus outside the visible area is reported under "Keyboard focus visible".
Motion and overlays
14 points
  • Moving content can be paused 5 points
    Tests whether videos and animations that start on their own and run longer than five seconds can be paused or stopped. Constant motion makes it hard for many people to read the rest of the page (WCAG 2.2.2 pause, stop, hide).
  • Reduced motion respected 5 points
    Tells the page that the visitor prefers reduced motion and tests whether its animations stop. People who react to motion with dizziness set this preference in their system (WCAG 2.3.3 animation from interactions).
  • No accessibility overlay 4 points
    Tests whether the page loads an overlay widget that promises accessibility as an add-on. An overlay does not repair the markup, does not satisfy the accessibility act and can get in the way of the assistive technology visitors already use.
PDF documents
12 points
  • Linked PDFs are tagged 4 points
    Opens the PDF documents linked from the start page and tests whether they carry a tag structure. Without tags a screen reader cannot tell headings, lists and tables apart (WCAG 1.3.1 info and relationships).
  • Linked PDFs declare their language 4 points
    Tests whether the linked PDF documents declare their language, so that a screen reader pronounces them correctly (WCAG 3.1.1 language of page).
  • Linked PDFs show a title 4 points
    Tests whether the linked PDF documents have a title and tell the viewer to show it instead of the file name (WCAG 2.4.2 page titled).
Accessibility statement
44 points
  • Accessibility statement present 4 points
    Tests whether the site links to an accessibility statement. Public bodies and, since the accessibility act, many businesses have to publish one; if it is missing, add a page that names the state of conformity and a contact option for barrier reports.
  • Accessibility statement reachable from every page 4 points
    Runs only in the scan of a whole website and tests whether every scanned page links the accessibility statement. The statement has to be reachable from every page, not only from the start page.
  • Feedback option in the statement 4 points
    Tests whether the accessibility statement names a way of reporting a barrier, for example a mail address, a form or a telephone number. Name a contact person plainly in the statement.
  • State of conformity in the statement 4 points
    Tests whether the accessibility statement says how far the site meets the requirements, that is fully, partially or not at all, and against which standard. Without that sentence the statement does not say what visitors can expect.
  • Known barriers listed in the statement 4 points
    Tests whether the accessibility statement names the parts that are not accessible yet. Listing them honestly, together with the reason and an alternative, is part of a complete statement.
  • Reasons for the known barriers 4 points
    Tests whether the accessibility statement says why the parts it names are not accessible, for example a disproportionate burden, or offers an accessible alternative for them. A barrier listed without a reason leaves visitors without a way around it.
  • Date of the last review 4 points
    Tests whether the accessibility statement carries the date on which it was drawn up or last reviewed. Without a date nobody can tell whether it still describes the current site; review it regularly and record the date.
  • Enforcement procedure in the statement 4 points
    Tests whether the accessibility statement names the supervisory or arbitration body a visitor can turn to when a barrier report gets no answer. Name the body that is responsible for you, with its contact details.
  • Description of the service 4 points
    Tests whether the accessibility information describes the service the website offers and how it is carried out. The BFSG expects this general description as part of the accessibility information; a statement of a public body under the BITV does not need it, there the check does not apply.
  • How the requirements are met 4 points
    Tests whether the accessibility information describes how the service meets the accessibility requirements, with the standard and the measures behind it. The BFSG expects an explanation, not only a claim; a statement of a public body under the BITV does not need it, there the check does not apply.
  • Market surveillance authority named 4 points
    Tests whether the accessibility information names the market surveillance authority responsible for the provider, in Germany the MLBF. The BFSG expects it to be named; a statement of a public body under the BITV does not need it, there the check does not apply.

Website score = (2 × Security + Accessibility) / 3

02 Scoring

How the score is calculated

Rule 1: 100 points per category

Every category gives up to 100 points. They are split into fixed bundles of checks that belong together, and within a bundle every check has its own share, all of them whole numbers, as listed above. The category score is the sum of the points its checks earn under rule 2.

Rule 2: all or nothing per check

A check has one verdict for the whole website. If it is violated on any page or any host, it earns 0 points; how many pages are affected is shown next to the check in the result. Uncertain, not confirmed (only read through the link to a page) and not measurable (the scanner could not get to it) earn 0 points as well, and a check that is not measurable on any page or any host earns 0 even where it passed elsewhere; the result names on how many pages it could not be measured. Where there is nothing to check, such as SPF on a domain without mail, the check earns its full points, and a category without any check that applies has 100.

Rule 3: means with a factor

A group is the mean of its categories and the website score the mean of the groups, each rounded to a whole number. The only weighting is the factor shown above next to every category and group: a category or group that counts twice is counted twice in the sum and in the count.

Score of a single page

The list of pages also shows a score for every single page. It follows the same rules and counts the checks of that page itself together with everything that holds once for the whole website: the domain, the host, the mandatory pages and the checks across all pages. The website counts the worst page for every check of a single page, so a page never scores below its website. A group score can be 0, the website score is the mean of the group scores as shown and at least 1, and a website without a single verdict has no score.

Unreachable pages

If the page itself cannot be opened, the scan shows no overall score. The DNS and mail findings measured without the page remain visible on their own.

03 Scale

Bands and ranks

Scores from 80 upwards are shown in green, from 50 to 79 in amber and below 50 in red.

100 Legendary 90-99 Excellent 80-89 Strong 65-79 Solid 50-64 Needs work 25-49 Weak 0-24 Critical

Trophy ladder

Badge and monitor mail show a trophy. Each rung presumes the one below it, so a site holds the highest trophy up to which every rung is met.

Bronze
  • overall score from 50
  • every group from 25
Silver
  • overall score from 65
  • every group from 50
  • no critical finding
Gold
  • overall score from 80
  • every group from 65
  • at most 2 high findings
Platinum
  • overall score from 90
  • every group from 80
  • no high finding
Diamond
  • overall score from 97
  • every group from 90
  • no finding above low

04 Not checked

Categories that are currently not checked

These categories exist in the code but are dormant. They are not checked, produce no findings and do not count towards any score, so a report says nothing about them.

Performance not checked SEO not checked Privacy policy & external fonts not checked Consent & Tracking not checked Legal / DACH Compliance not checked Third-Party Risk not checked Form consent & privacy notice not checked E-Commerce Compliance not checked Advertising Claims Risk not checked Trust & Transparency (heuristic checks) not checked Local & Hospitality Readiness not checked Sustainability not checked Images not checked AI Visibility not checked

05 Limits

What the scanner cannot tell you

Deliberately not checked

The scanner gives no legal advice and does not judge whether a site is compliant as a whole. It does not review the content of texts beyond the signals listed above, does not test business processes such as ordering or contract flows, and does not assess internal systems, servers or data handling that are not visible from outside.

Why results can differ between two scans

  • Network: timeouts, packet loss or a slow response can stop a check from running, and it then counts as not measurable and earns no points.
  • CDN and edge servers: a content delivery network can answer from a different server with different headers, cookies or certificates on each request.
  • Time: sites change, consent banners and third-party scripts load conditionally, and certificates or domains approach their expiry.
  • AI assessment: some checks, such as reading a privacy policy, are judged by a language model. Its answer can vary slightly between two runs on the same text.

Limits of the scanner

  • Only publicly visible signals: the scanner sees what any browser receives from the page and its DNS records, nothing more.
  • No penetration test: it does not try to exploit vulnerabilities, guess passwords or send attack traffic.
  • No authentication: pages behind a login, a paywall or a customer account are not scanned.

See the methodology applied to your website

The scan takes about a minute and shows every check with its result.

Scan a website

Product

Learn

Legal

Cancel contracts here Withdraw from contract © 2026 Erseni