Security - https://www.hornbach.se BeaverCheck Audit

D

Subresource Integrity Adoption

Action

20% SRI adoption (1/5 third-party resources)

FIX

20% SRI adoption (1/5 third-party resources)

SRI adoption: 1/5 third-party resources protected (20%)

Of 5 third-party `<script>` / `<link rel=stylesheet>` resources, 1 (20%) declare a Subresource Integrity hash via the `integrity=` attribute. SRI binds the page to the exact bytes of the third-party resource: if the CDN is compromised, attacker-modified bytes won't match the declared hash and the browser refuses to execute the resource. Missing SRI on (first 4 examples): - https://cdn.trkkn.com/tracking-extension/4.1/gtmext.min.4.1.1.js?pid=trial_hornbach - https://www.googletagmanager.com/gtm.js?id=GTM-WWSVZZV&gtm=4e6562 - https://www.googletagmanager.com/gtm.js?id=GTM-54PRXDGS - https://cdn.ablyft.com/s/22895057-657_prd_client_hornbach_se.js Fix: add `integrity="sha384-..."` and `crossorigin="anonymous"` attributes. Generators: srihash.org, or in-browser via `await crypto.subtle.digest('SHA-384', bytes)`. Cache-bust the resource URL when you change versions, since the integrity hash will mismatch with old cached bytes.

Got: 20% (1/5)

F

Permissions-Policy Granularity

Action

0% high-risk feature coverage (0/10)

FIX

0% high-risk feature coverage (0/10)

Permissions-Policy covers 0/10 high-risk features (0%)

The Permissions-Policy header explicitly declares policies for 0/10 high-risk features. Covered: Not declared (default-allow): camera, microphone, geolocation, payment, usb, serial, midi, accelerometer, gyroscope, magnetometer The non-declared features fall back to their spec-default policy (usually `self`), which means an XSS-injected or compromised iframe could request them. For features the page genuinely doesn't use, declare `feature=()` to fully close them.

Got: 0% (0/10)

D

Source Map Exposure

Action

2 publicly-accessible source map(s) -- full source code leaked

FIX

2 publicly-accessible source map(s) -- full source code leaked

2 publicly-accessible JavaScript source map(s)

Source maps (.js.map files) reveal the original source code -- variable names, comments, file structure, and sometimes secrets that were stripped from the bundled output. They're shipped to production by mistake almost universally; the standard fix is a build-tool config flag (Webpack: `devtool: false` or `'hidden-source-map'`; Vite: `build.sourcemap: false`; Next.js: `productionBrowserSourceMaps: false`). Once removed, audit your CDN/edge cache to evict any previously-cached .map URLs. Sample accessible URLs: https://www.hornbach.se/header/js/header.8e528c6a434cf3702354.js.map, https://www.hornbach.se/autocomplete/assets/autocomplete.79c197ddf69e3992ed42.js.map.

D

Subresource Integrity

Action

1 of 5 external resources have SRI

FIX

1 of 5 external resources have SRI

External script from cdn.trkkn.com lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: https://cdn.trkkn.com/tracking-extension/4.1/gtmext.min.4.1.1.js?pid=trial_hornbach

External script from www.googletagmanager.com lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: https://www.googletagmanager.com/gtm.js?id=GTM-WWSVZZV&gtm=4e6562

External script from www.googletagmanager.com lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: https://www.googletagmanager.com/gtm.js?id=GTM-54PRXDGS

script from dok.js-cdn.dynatrace.com has SRI protection

External script from cdn.ablyft.com lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: https://cdn.ablyft.com/s/22895057-657_prd_client_hornbach_se.js

SRI Coverage 1 / 5 of external resources have integrity hashes

Tag	Domain	Integrity
<script>	cdn.trkkn.com	✗ Missing
<script>	www.googletagmanager.com	✗ Missing
<script>	www.googletagmanager.com	✗ Missing
<script>	dok.js-cdn.dynatrace.com	✓ Protected
<script>	cdn.ablyft.com	✗ Missing

F

Email Security

Action

no DMARC, no SPF

FIX

no DMARC, no SPF

No DMARC record found

Without DMARC, email receivers have no policy for handling authentication failures. Add a TXT record at _dmarc.<domain> starting with v=DMARC1.

No SPF record found

Without SPF (Sender Policy Framework), receivers can't tell which servers are authorized to send mail for your domain. Add a TXT record at the apex starting with v=spf1, ending in -all.

No DKIM detected via common selectors

DKIM signs outbound mail to prove origin. We probed common selectors (default, google, selector1, etc.) without finding a record. If you use a non-standard selector, this is a false negative.

MTA-STS not configured

MTA-STS forces inbound mail to use TLS, preventing downgrade attacks. Requires both a TXT record at _mta-sts.<domain> and a policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt.

TLS-RPT not configured

TLS-RPT (RFC 8460) lets MTAs report TLS-handshake failures, so you can detect and fix MTA-STS misconfigurations. Add a TXT record at _smtp._tls.<domain>.

BIMI not configured

BIMI (Brand Indicators for Message Identification) lets supporting clients (Gmail, Apple Mail, Yahoo) display your verified logo next to your messages. Optional but raises trust signals. Requires DMARC at p=quarantine or p=reject to be honored.

DMARC

No DMARC record found

Without DMARC, email receivers have no policy for handling authentication failures from your domain.

Without DMARC, email receivers have no policy for handling authentication failures. Add a TXT record at _dmarc.<domain> starting with v=DMARC1.

Why this matters

Without DMARC, anyone can send phishing emails using your domain name.

Learn more ▾

DMARC tells receiving mail servers what to do with email that fails SPF/DKIM checks for your domain. With a strict 'p=reject' policy, spoofed emails get bounced; without it they reach the inbox. Domains used in phishing campaigns lose deliverability and brand trust fast.

Source: DMARC.org / NIST

Without SPF (Sender Policy Framework), receivers can't tell which servers are authorized to send mail for your domain. Add a TXT record at the apex starting with v=spf1, ending in -all.

Why this matters

Security gaps expose your site and users to attacks, eroding trust.

DKIM signs outbound mail to prove origin. We probed common selectors (default, google, selector1, etc.) without finding a record. If you use a non-standard selector, this is a false negative.

Why this matters

No DKIM signature on outbound mail — receivers can't cryptographically prove the message came from your domain.

Learn more ▾

DKIM signs outbound mail with a private key whose public half lives in DNS at <selector>._domainkey.<domain>. Without DKIM, DMARC alone can't tell legitimate mail from spoofs, and large mailbox providers (Gmail, Yahoo) increasingly require DKIM for inbox placement. Note: this check probes a curated list of common selectors; non-standard selectors produce a false negative.

Source: RFC 6376 / Google + Yahoo 2024 sender requirements

MTA-STS forces inbound mail to use TLS, preventing downgrade attacks. Requires both a TXT record at _mta-sts.<domain> and a policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt.

Why this matters

Without MTA-STS, inbound mail can be silently downgraded to plain SMTP by a network attacker.

Learn more ▾

MTA-STS (RFC 8461) tells sending mail servers to use TLS and to refuse delivery if TLS fails. Requires both a TXT record at _mta-sts.<domain> AND a policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt. Without it, an active attacker on the network path can strip STARTTLS and read the email in plaintext.

Source: RFC 8461

TLS-RPT (RFC 8460) lets MTAs report TLS-handshake failures, so you can detect and fix MTA-STS misconfigurations. Add a TXT record at _smtp._tls.<domain>.

Why this matters

Without TLS-RPT, you have no visibility into inbound TLS failures — MTA-STS misconfigurations stay hidden until users complain.

Learn more ▾

TLS-RPT (RFC 8460) is the feedback channel for MTA-STS: senders post aggregate reports of TLS-handshake failures to the URI in your _smtp._tls TXT record. Without it, an MTA-STS misconfiguration silently rejects mail and you find out only when someone notices missing email.

Source: RFC 8460

BIMI (Brand Indicators for Message Identification) lets supporting clients (Gmail, Apple Mail, Yahoo) display your verified logo next to your messages. Optional but raises trust signals. Requires DMARC at p=quarantine or p=reject to be honored.

Why this matters

Security gaps expose your site and users to attacks, eroding trust.

B

Security Headers

6 of 10 headers properly configured

REVIEW

6 of 10 headers properly configured

HSTS is missing includeSubDomains

Without includeSubDomains, subdomains can still be accessed over HTTP.

Got: max-age=157680000; Expected: max-age=31536000; includeSubDomains

X-Content-Type-Options is properly configured

Got: nosniff

X-Frame-Options header is missing

This header prevents clickjacking by controlling who can embed your page in a frame. Set it to DENY or SAMEORIGIN.

Expected: DENY

Referrer-Policy is properly configured

Got: strict-origin-when-cross-origin

Permissions-Policy is set

Got: ch-ua=(self "https://*.hornbach.se"), ch-ua-full-version-list=(self "https://*.hornbach.se"), ch-ua-model=(self "https://*.hornbach.se"), ch-ua-mobile=(self "https://*.hornbach.se"), ch-ua-platform=(self "https://*.hornbach.se"), ch-ua-platform-version=(self "https://*.hornbach.se")

Content-Security-Policy is present

Got: frame-ancestors 'self' http://customer-hornbach.loop21.net https://customer-horn…

Cross-Origin-Opener-Policy header is missing

COOP isolates your browsing context, preventing cross-origin side-channel attacks. Set to 'same-origin'.

Expected: same-origin

Cross-Origin-Embedder-Policy header is missing

COEP prevents loading cross-origin resources without explicit permission. Required for SharedArrayBuffer and high-resolution timers.

Expected: require-corp

X-Powered-By header is not present

Server header is not present

Domain is not in the Chrome HSTS preload list (status: unknown)

Submit your domain to hstspreload.org to close the trust-on-first-use gap. Requires a preload-ready HSTS header (max-age=31536000+, includeSubDomains, preload).

Got: unknown

Without includeSubDomains, subdomains can still be accessed over HTTP.

Expected: max-age=31536000; includeSubDomains

Why this matters

Without includeSubDomains, a forgotten dev subdomain over HTTP can set malicious cookies that ride to the apex.

Learn more ▾

HSTS without includeSubDomains protects only the exact domain. Cookies set on a non-HSTS subdomain can ride to the apex via cookie-scope attacks. The fix is one directive append. Verify all subdomains support HTTPS first — adding includeSubDomains to a domain with HTTP-only subdomains breaks them.

Source: RFC 6797

This header prevents clickjacking by controlling who can embed your page in a frame. Set it to DENY or SAMEORIGIN.

Expected: DENY

Why this matters

Without frame protection, your site can be embedded in a hostile page and used for clickjacking.

Learn more ▾

Clickjacking overlays your site under a transparent malicious page so users click invisible buttons. Setting X-Frame-Options: DENY (or a modern frame-ancestors CSP directive) blocks the embedding entirely. There's almost never a legitimate reason to allow it.

Source: OWASP / MDN

COOP isolates your browsing context, preventing cross-origin side-channel attacks. Set to 'same-origin'.

Expected: same-origin

Why this matters

COOP isolates your top-level browsing context from cross-origin windows — without it, popup-based side-channel attacks remain possible.

Learn more ▾

Cross-Origin-Opener-Policy: same-origin prevents cross-origin pages from sharing a browsing-context group with yours. This blocks cross-window references that enable Spectre-style timing attacks and tab-nabbing. Required if you want to enable SharedArrayBuffer.

Source: MDN / web.dev

COEP prevents loading cross-origin resources without explicit permission. Required for SharedArrayBuffer and high-resolution timers.

Expected: require-corp

Why this matters

COEP enforces that all embedded resources opt-in to cross-origin embedding — required for cross-origin isolation features.

Learn more ▾

Cross-Origin-Embedder-Policy: require-corp ensures every embedded resource (script, iframe, image) explicitly allows being loaded cross-origin. Combined with COOP, this enables the cross-origin-isolated context that unlocks SharedArrayBuffer, high-resolution timers, and other powerful APIs.

Source: MDN / web.dev

Submit your domain to hstspreload.org to close the trust-on-first-use gap. Requires a preload-ready HSTS header (max-age=31536000+, includeSubDomains, preload).

Why this matters

Not in the Chrome preload list — first-time visitors over plain HTTP can be downgraded by a network attacker before HSTS kicks in.

Learn more ▾

The HSTS header only protects users who have already visited the site (TOFU window). Adding your domain to the Chrome preload list closes that gap so HSTS is enforced from the very first connection. Requires a preload-ready header (max-age=31536000+, includeSubDomains, preload) then submission at hstspreload.org. Inclusion ships in the next Chrome release after acceptance.

Source: hstspreload.org

B

Content Security Policy

2 of 10 CSP checks passed

REVIEW

2 of 10 CSP checks passed

Raw CSP policy

Got: frame-ancestors 'self' http://customer-hornbach.loop21.net https://customer-hornbach.loop21.net http://public-location-hornbach.loop21.net https://public-location-hornbach.loop21.net

default-src directive is missing

default-src provides a fallback for other directives. Set it to restrict default resource loading.

Expected: default-src 'self'

No script-src or default-src to check for 'unsafe-inline'

No script-src or default-src to check for 'unsafe-eval'

No script-src or default-src to check for wildcard

object-src falls back to default-src

base-uri directive is missing

Without base-uri, attackers can inject a <base> tag to hijack relative URLs. Set it to 'self' or 'none'.

Expected: base-uri 'self'

frame-ancestors directive is set

Got: frame-ancestors 'self' http://customer-hornbach.loop21.net https://customer-hornbach.loop21.net http://public-location-hornbach.loop21.net https://public-location-hornbach.loop21.net

form-action directive is missing

form-action restricts where forms can submit data, preventing form hijacking.

Expected: form-action 'self'

upgrade-insecure-requests is not set

This directive upgrades HTTP resources to HTTPS automatically, preventing mixed content.

Expected: upgrade-insecure-requests

default-src provides a fallback for other directives. Set it to restrict default resource loading.

Expected: default-src 'self'

Why this matters

Security gaps expose your site and users to attacks, eroding trust.

Without base-uri, attackers can inject a <base> tag to hijack relative URLs. Set it to 'self' or 'none'.

Expected: base-uri 'self'

Why this matters

Missing base-uri in CSP leaves a base-tag injection attack path open even on otherwise strict policies.

Learn more ▾

A common omission: developers add CSP for script-src and frame-ancestors but forget base-uri. The result is a CSP that looks strict but lets an attacker rewrite every URL on the page via <base href>. Add `base-uri 'self'` to close the gap.

Source: MDN CSP

form-action restricts where forms can submit data, preventing form hijacking.

Expected: form-action 'self'

Why this matters

Security gaps expose your site and users to attacks, eroding trust.

This directive upgrades HTTP resources to HTTPS automatically, preventing mixed content.

Expected: upgrade-insecure-requests

Why this matters

Without upgrade-insecure-requests, any HTTP subresource link survives as a mixed-content warning instead of auto-upgrading.

Learn more ▾

Adding `upgrade-insecure-requests` to your CSP turns every http:// subresource fetch into https:// at the browser layer. One-line defense against accidental mixed content from legacy links or third-party widgets.

Source: MDN CSP

Parsed Policy

frame-ancestors 'self'http://customer-hornbach.loop21.nethttps://customer-hornbach.loop21.nethttp://public-location-hornbach.loop21.nethttps://public-location-hornbach.loop21.net

C

Cookie Security

Action

5 cookies analyzed, 9 checks passed

REVIEW

5 cookies analyzed, 9 checks passed

Cookie 'hbMarketSession' is missing the Secure flag

Without the Secure flag, this cookie can be sent over unencrypted HTTP, exposing it to interception.

Cookie 'hbMarketSession' is missing the HttpOnly flag

Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.

Cookie 'hbMarketSession' has SameSite=Lax

Cookie 'hbMarketCookie' has the Secure flag

Cookie 'hbMarketCookie' has the HttpOnly flag

Cookie 'hbMarketCookie' has no SameSite attribute

Without an explicit SameSite attribute, browser default behavior varies. Set SameSite=Lax or Strict.

Cookie 'hbUserSession' has the Secure flag

Cookie 'hbUserSession' is missing the HttpOnly flag

Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.

Cookie 'hbUserSession' has SameSite=Lax

Cookie 'dtCookieo26m5unv' has the Secure flag

Cookie 'dtCookieo26m5unv' is missing the HttpOnly flag

Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.

Cookie 'dtCookieo26m5unv' has SameSite=None

Cookie 'absearchvariant' has the Secure flag

Cookie 'absearchvariant' is missing the HttpOnly flag

Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.

Cookie 'absearchvariant' has SameSite=None

5 cookies analyzed 1 critical 5 warnings

Name	Secure	HttpOnly	SameSite	Size	Issues
hbMarketSession	✗	✗	Lax	18 B	2
hbMarketCookie	✓	✓	—	17 B	1
hbUserSession	✓	✗	Lax	49 B	1
dtCookieo26m5unv	✓	✗	None	109 B	1
absearchvariant	✓	✗	None	16 B	1

B

WAF / Bot Protection

No WAF detected via response headers

REVIEW

No WAF detected via response headers

No WAF detected

Response headers don't match any known WAF or bot-management product. Sites exposed to abuse (login, signup, payment) typically benefit from a WAF such as Cloudflare, Akamai, AWS WAF, or Imperva.

B

CSP Inline-Style Readiness

8 inline style attribute(s) detected

REVIEW

8 inline style attribute(s) detected

Each `style=""` attribute forces `style-src 'unsafe-inline'` in any Content-Security-Policy, which negates most of CSP's XSS-mitigation value. 8 inline style(s) is low. Affected element types include: html, span, cms-hero-teaser, cms-project-module, cms-current-topic. Move styles to a stylesheet; use CSS custom properties for runtime-dynamic values; or adopt a nonce/hash CSP policy. Most teams take the stylesheet path because it's also a maintainability win.

B

Trusted Types (XSS Sink Hardening)

Trusted Types not enabled

REVIEW

Trusted Types not enabled

Trusted Types (CSP3) is a Chrome 83+ defense that requires DOM-XSS sinks (innerHTML, document.write, eval, ...) to receive a typed-and-sanitized value rather than a raw string. Adding `Content-Security-Policy: require-trusted-types-for 'script'; trusted-types default` neutralizes most DOM-XSS even when a payload reaches a sink. Adoption is currently ~0.1% of pages so this is informational; a roll-out usually starts in report-only mode.

B

Open Redirect Surface

1 link(s) carry redirect-shaped query parameter(s)

REVIEW

1 link(s) carry redirect-shaped query parameter(s)

Heuristic flag -- whether each endpoint actually permits an arbitrary redirect target depends on server-side validation. Audit the listed paths' redirect-target handling: the endpoint should either (a) restrict to a relative path, (b) restrict to an allowlisted host set, or (c) sign the target. Open redirects power phishing flows (the attacker's URL begins with your trusted domain) and bypass some SSRF-mitigation cookie scoping. Common parameter names flagged: redirect, redirect_uri, redirect_url, redirecturl, return, returnto, return_to, returnurl, return_url, next, nexturl, next_url, continue, goto, dest, destination, forward, target.

Got: https://login.hornbach.com/auth/realms/hornbach/protocol/ope…?redirect_uri=...

C

Permissions-Policy

Action

6 directives, 5 missing

REVIEW

6 directives, 5 missing

ch-ua=(self "https://*.hornbach.se")

ch-ua-full-version-list=(self "https://*.hornbach.se")

ch-ua-model=(self "https://*.hornbach.se")

ch-ua-mobile=(self "https://*.hornbach.se")

ch-ua-platform=(self "https://*.hornbach.se")

ch-ua-platform-version=(self "https://*.hornbach.se")

camera not restricted

Consider adding camera=() to block camera access from embedded content.

microphone not restricted

Consider adding microphone=() to block microphone access from embedded content.

geolocation not restricted

Consider adding geolocation=() to block geolocation access from embedded content.

payment not restricted

Consider adding payment=() to block payment access from embedded content.

usb not restricted

Consider adding usb=() to block usb access from embedded content.

Raw Header

ch-ua=(self "https://*.hornbach.se") ch-ua-full-version-list=(self "https://*.hornbach.se") ch-ua-model=(self "https://*.hornbach.se") ch-ua-mobile=(self "https://*.hornbach.se") ch-ua-platform=(self "https://*.hornbach.se") ch-ua-platform-version=(self "https://*.hornbach.se")

Feature Permissions

Blocked Self Only Unrestricted Not Set

ch-ua (self "https://*.hornbach.se") (1 origins)

ch-ua-full-version-list (self "https://*.hornbach.se") (1 origins)

ch-ua-model (self "https://*.hornbach.se") (1 origins)

ch-ua-mobile (self "https://*.hornbach.se") (1 origins)

ch-ua-platform (self "https://*.hornbach.se") (1 origins)

ch-ua-platform-version (self "https://*.hornbach.se") (1 origins)

camera Not Set

microphone Not Set

geolocation Not Set

payment Not Set

usb Not Set

B

CORS Configuration

No CORS headers

REVIEW

No CORS headers

No CORS headers present — secure default

CORS Configuration ✓ Secure

No CORS headers detected.

Cross-origin requests are blocked by browser same-origin policy.

Origin reflection test

Some servers mirror the request Origin header, which can be exploited. Test manually:

curl -sI -H "Origin: https://evil.com" <url> | grep -i access-control

A+

TLS & Certificates

TLS 1.3, 7 checks passed

PASS

TLS 1.3, 7 checks passed

TLS 1.3 is used

Got: TLS 1.3

Strong cipher suite is used

Got: TLS_AES_128_GCM_SHA256

HTTP/2 is not negotiated

HTTP/2 provides multiplexing and header compression for better performance.

Got: http/1.1

OCSP stapling not enabled

Without stapling, the browser performs a separate OCSP roundtrip on first connection -- adding latency and leaking the visited host to the CA. Enable OCSP stapling on your TLS server.

Certificate is valid (expires in 72 days)

Got: 2026-07-22T17:38:26Z

Certificate chain has 2 certificates

Certificate uses modern signature algorithm

Got: SHA256-RSA

Certificate covers 2 domain(s)

Got: hornbach.se, www.hornbach.se

Certificate is issued by a trusted CA

Got: CN=R12,O=Let's Encrypt,C=US

HTTP/2 provides multiplexing and header compression for better performance.

Why this matters

HTTP/1.1 forces the browser to make sequential requests, multiplying latency on every page.

Learn more ▾

HTTP/2 (and HTTP/3) multiplex many requests over a single connection, eliminating head-of-line blocking. HTTP/1.1 forces the browser to either queue requests or open many parallel connections — both worse. Most modern web servers support HTTP/2 with one config line.

Source: MDN Web Docs

Without stapling, the browser performs a separate OCSP roundtrip on first connection -- adding latency and leaking the visited host to the CA. Enable OCSP stapling on your TLS server.

Why this matters

Without OCSP stapling, every first-time visitor pays an extra OCSP roundtrip — and the CA learns who's visiting your site.

Learn more ▾

OCSP stapling has the server fetch its own revocation status from the CA and attach the signed response to the TLS handshake. Without it, browsers contact the CA directly: extra latency for the user and a privacy leak (the CA sees who connected). Enable ssl_stapling on (nginx) / SSLUseStapling On (Apache) / OCSPStapling = on (Caddy auto-enables).

Source: RFC 6961 / Mozilla Server-Side TLS guide

Connection

Protocol

TLS 1.3

Cipher Suite

TLS_AES_128_GCM_SHA256

HTTP Version

HTTP/1.1

Certificate Chain

Leaf Certificate

Subject CN=hornbach.seIssuer CN=R12,O=Let's Encrypt,C=USValid 2026-04-23T17:38:27Z → 2026-07-22T17:38:26ZExpires in 72 days SANs hornbach.se, www.hornbach.seSignature SHA256-RSASerial 58cd381ebff4f292555b02ac64c7d7a930d

Intermediate (CA Certificate)

Subject CN=R12,O=Let's Encrypt,C=USIssuer CN=ISRG Root X1,O=Internet Security Research Group,C=USValid 2024-03-13T00:00:00Z → 2027-03-12T23:59:59ZExpires in 305 days Signature SHA256-RSASerial c212324b70a9b49171dc40f7e285263c

A+

Cookie Hygiene

All 5 cookie(s) pass hygiene checks

PASS

All 5 cookie(s) pass hygiene checks

A

security.txt

Vulnerability disclosure policy

PASS

Vulnerability disclosure policy

security.txt found

Got: https://www.hornbach.se/.well-known/security.txt

security.txt: Missing required 'Expires' field (RFC 9116)

security.txt

Contact: infosec@hornbach.com

A+

Cross-Origin Tab Safety

All 7 new-tab link(s) carry rel=noopener

PASS

All 7 new-tab link(s) carry rel=noopener

A+

Bot Challenge Detection

Scan reached real page content (no bot-protection interstitial)

PASS

Scan reached real page content (no bot-protection interstitial)

No bot-protection interstitial detected -- the rest of the report reflects the real page

A+

Soft-404 Detection

No soft-404 patterns detected in page title or headings

PASS

No soft-404 patterns detected in page title or headings

A+

Empty Page Detection

Page has substantive body text and no placeholder / template-leak signals

PASS

Page has substantive body text and no placeholder / template-leak signals

A+

Geo-Restriction Detection

No geo-restriction signals detected -- scan reached the page from an allowed region

PASS

No geo-restriction signals detected -- scan reached the page from an allowed region

No geo-restriction detected

A+

Maintenance Mode Detection

No maintenance-mode signals detected -- scan reached a normal page

PASS

No maintenance-mode signals detected -- scan reached a normal page

No maintenance-mode signals detected

A+

CORS Depth

No CORS response headers -- the resource is same-origin-only by browser default

PASS

No CORS response headers -- the resource is same-origin-only by browser default

A+

Referrer-Policy Strictness

Referrer-Policy is `strict-origin-when-cross-origin` (modern default -- full URL same-origin, origin-only cross-origin)

PASS

Referrer-Policy is `strict-origin-when-cross-origin` (modern default -- full URL same-origin, origin-only cross-origin)

Referrer-Policy: `strict-origin-when-cross-origin` -- modern default -- full URL same-origin, origin-only cross-origin

The modern browser default (Chrome 85+, Firefox 87+, Safari 15+). Full URL Referer on same-origin; origin only on cross-origin; no Referer on HTTPS-to-HTTP downgrade. Privacy-safe and breaks no analytics. The recommended explicit value.

Got: strict-origin-when-cross-origin

A+

HTML Version Disclosure

No software-version disclosures in HTML

PASS

No software-version disclosures in HTML

A+

Auth Security

Page is not a login form -- auth-security checks are N/A

PASS

Page is not a login form -- auth-security checks are N/A

Page does not appear to be a login form

A+

Subdomain Inventory Exposure

No risky subdomain names in certificate SANs

PASS

No risky subdomain names in certificate SANs

A+

JS Library Vulnerabilities

No known vulnerabilities

PASS

No known vulnerabilities

No known JavaScript library vulnerabilities detected

No known JavaScript library vulnerabilities detected.

A+

Information Leakage

No exposures

PASS

No exposures

security.txt is present — good practice

No sensitive files exposed

No sensitive files exposed — all paths returned 404.

Path	Status	Category	Risk
/.git/HEAD	✓ Not found	Version Control	—
/.git/config	✓ Not found	Version Control	—
/.svn/entries	✓ Not found	Version Control	—
/.env	✓ Not found	Configuration	—
/.env.local	✓ Not found	Configuration	—
/.env.production	✓ Not found	Configuration	—
/wp-config.php	✓ Not found	Configuration	—
/.htaccess	✓ Not found	Configuration	—
/phpinfo.php	✓ Not found	Debug	—
/server-status	✓ Not found	Debug	—
/server-info	✓ Not found	Debug	—
/.well-known/security.txt	✗ Exposed	Security Policy	Info
/package.json	✓ Not found	dependency-manifest	—
/composer.json	✓ Not found	dependency-manifest	—
/Gemfile	✓ Not found	dependency-manifest	—
/Gemfile.lock	✓ Not found	dependency-manifest	—
/requirements.txt	✓ Not found	dependency-manifest	—
/pom.xml	✓ Not found	dependency-manifest	—
/.gitlab-ci.yml	✓ Not found	ci-config	—
/.travis.yml	✓ Not found	ci-config	—

A+

API Surface

No API specs or GraphQL introspection found (probed 11 candidate path(s))

PASS

No API specs or GraphQL introspection found (probed 11 candidate path(s))

No API specs or GraphQL introspection found (probed 11 path(s))

A+

Transport Security

HTTP/3, HSTS, and TLS version analysis

PASS

HTTP/3, HSTS, and TLS version analysis

HTTP/3 (QUIC) supported

The server advertises HTTP/3 via Alt-Svc for faster connections on mobile networks.

HSTS enabled (base policy)

HSTS missing includeSubDomains

Without includeSubDomains, HSTS only protects the exact domain.

TLS 1.3 in use (fastest handshake, 1-RTT)