Skip to main content

Security report for hornbach.com

Client Challenge · Other · N/a

High risk. 8 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

48/100

Risk levelHigh

0–100, higher is better. How it is calculated

The website hornbach.com is currently inaccessible beyond a client challenge page, which appears to be a security or bot mitigation mechanism blocking normal content access. Due to this, no meaningful business information, contact details, or policies are available for analysis. The domain DNS records indicate active management with multiple domain verification TXT records, suggesting legitimate ownership. However, the SSL configuration is critically lacking with no valid certificate and no HTTPS support, severely impacting security posture. The minimal security headers and absence of privacy or cookie policies further reduce compliance and trustworthiness. Overall, the site is not currently providing usable content or secure access, resulting in a low AI score and high risk from a security and compliance perspective.

Scanned

This is an earlier scan of hornbach.com. View the latest report

NIS2 and GDPR posture

GDPR outside view
15/ 100 · Critical
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (j) Multi-factor authentication and secured communications: Not visible from outside

This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.

GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.

Priority findings

8 findings rated critical or high. Fix these first.

  1. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • Critical

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

  2. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

  3. Security headers

    Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.

    • High

      Missing Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • High

      Missing X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • High

      Missing Content-Security-Policy header

      Controls resources the browser is allowed to load

      What to do: Implement a Content-Security-Policy appropriate for your application

      • ASVS V3.4.3
      • OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…

Need hands-on remediation? Email guard@offseq.com

Keep watching hornbach.com

This scan found 20 issues across 6 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.

Daily monitoring

Recommended

€25per month

  • TLS certificates and expiry
  • DNS records
  • SPF, DKIM and DMARC
  • Security headers
  • GDPR and NIS2 posture
  • Exposed services
  • Third-party trackers
  • Security score drift

Email alerts on material changes and an exportable JSON history of every change.

Billed monthly to your card. Cancel anytime. See sample alerts.

Full report

€39.90one-time

  • The complete analysis as a PDF you can cite
  • Email delivery with an unlock code
  • Lifetime access to this report

Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.

Results by check

Each check with its score, findings and the evidence it collected.

How this score is calculated

The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.

Counted in this score

SSL/TLS
0
Security headers
20
Email security
65
DNS health
90
Network security
100
GDPR outside view
15
Average
48

Not counted

  • NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
  • OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.

Findings that cap the score at 49

Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.

  • The certificate is not trusted by browsers
  • The website is not served over HTTPS
  • A database, remote desktop, file-sharing or Telnet service is reachable from the internet
  • The page loads a script from a compromised source
  • The domain registration has expired
  • SPF authorises every server to send mail as the domain

Partial scans

When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.

Risk levels

  • Critical0–25
  • High26–49
  • Medium50–75
  • Low76–100

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention hornbach.com, from OffSeq Breach.

Total records
6,298
Employees
12
Customers
6,271
Third parties
15
Weak passwords
5%

Latest record dated 2026-05-25 · 11 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for hornbach.com.

Select it in the checkout above.

Masked preview

  • –sts.hornbach.com2026-05-25
  • –sts.hornbach.com2026-05-22
  • –sts.hornbach.com2026-04-30
  • –.sts.hornbach.com2026-01-13
  • –sts.hornbach.com2026-01-05

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Open in Breach(opens in a new tab)Monitor on Breach(opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Due to the blocked content, no business intelligence data such as company name, market position, or services could be extracted. The domain appears registered and managed properly, but the lack of accessible content prevents assessment of business model, target audience, or competitive advantages. The presence of multiple domain verification TXT records indicates the domain is actively maintained, but no direct business insights are available from the provided data.

Security posture

The security posture is poor with no valid SSL certificate, no HTTPS protocols enabled, and minimal security headers beyond a Content-Security-Policy. There is no evidence of incident response or security policies published. The site lacks HSTS, OCSP stapling, and session resumption features. The client challenge page indicates some form of security control is in place, but it also blocks legitimate access and prevents further security evaluation. Overall, the site is vulnerable to interception and lacks modern security best practices.

Recommendations

  1. Obtain and deploy a valid SSL certificate to enable HTTPS and protect user data.
  2. Enable modern TLS protocols (TLS 1.2 or TLS 1.3) and disable insecure protocols.
  3. Implement comprehensive security headers including HSTS, X-Frame-Options, and X-Content-Type-Options.
  4. Publish clear privacy, cookie, and security policies to improve compliance and trust.
  5. Review and optimize the client challenge mechanism to avoid blocking legitimate users and enable full site access for analysis.
Technical notes

Notes

The website currently serves a minimal HTML client challenge page with inline scripts to load additional JavaScript resources. The page includes a strict Content-Security-Policy restricting resource loading to self and specific hashes. No external links, forms, or business content are present. The SSL configuration is invalid with no TLS protocols enabled. DNS records show standard A, MX, NS, and TXT records with multiple domain verification entries but no DNSSEC. Performance metrics are zero, indicating no real page load occurred. The technical stack is minimal, primarily JavaScript, with no detected CMS or frameworks. The site lacks mobile optimization and SEO features due to blocked content.
Standards and sources

Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.

Retrieved 2026-10-25

Earlier scans of this domain

  1. 77/100Low27 findingsView report
Reviews of this site

Share your experience with hornbach.com. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review hornbach.com.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.