Skip to main content

Security report for heidschnuckenweg.de

Lüneburger Heide GmbH · Hospitality · Germany

High risk. 10 critical or high findings in GDPR outside view, Email security and 2 other checks.

Security score

49/100

Risk levelHigh

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

The website www.heidschnuckenweg.de serves as a comprehensive tourism portal dedicated to the Heidschnuckenweg hiking trail in the Lüneburger Heide region of Germany. It provides detailed information about the trail's 13 stages, accommodation options, seasonal hiking tips, and related services. The site is professionally designed with consistent branding and targets hikers, nature enthusiasts, and tourists seeking outdoor experiences in northern Germany. The business behind the site is Lüneburger Heide GmbH, a regional tourism organization, positioning itself as a key promoter of this popular hiking destination. Technically, the website is built using modern web technologies including React and Next.js, hosted on Hetzner servers. It demonstrates good mobile optimization, SEO practices, and moderate performance. The site employs HTTPS with strong SSL configuration but lacks explicit security headers, which could be improved. Privacy and cookie policies are present and GDPR compliant, with a cookie consent mechanism implemented. Contact information is available via a dedicated contact page, though no direct emails or phone numbers are embedded in the main HTML. From a security perspective, the site shows a solid posture with no visible vulnerabilities or exposed sensitive data. However, it lacks dedicated security or incident response policies and does not provide a vulnerability disclosure or security.txt file. The domain registration is consistent with the hosting provider and business purpose, indicating legitimacy. No WAF or blocking mechanisms interfere with content access. Overall, the website is a trustworthy, well-maintained tourism information platform with good content quality and technical implementation. Strategic recommendations include enhancing security headers, publishing explicit security policies, and improving accessibility features to further strengthen the site's security and compliance posture.

Scanned

NIS2 and GDPR posture

GDPR outside view
28/ 100 · High
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

10 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

      EU business without adequate privacy measures

      EU businesses are subject to strict GDPR requirements

      What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures

  2. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

  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 heidschnuckenweg.de

This scan found 31 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. The full timeline opens with your unlock code.

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
52
Security headers
15
Email security
40
DNS health
60
Network security
100
GDPR outside view
28
Average
49

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 heidschnuckenweg.de, from OffSeq Breach.

No leaked records found

Breach holds no records for heidschnuckenweg.de right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

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

The business operates in the hospitality and tourism sector, focusing on promoting the Heidschnuckenweg hiking trail. Its market positioning is strong within the regional tourism ecosystem, leveraging partnerships with recognized entities like Top Trails of Germany and Wanderbares Deutschland. The business model centers on providing comprehensive trail information, accommodation listings, and related services to hikers and tourists. Revenue streams likely include partnerships, advertising, and possibly booking commissions. The target audience includes outdoor enthusiasts, families, and nature tourists. Growth indicators include active blog content and seasonal updates. The partnership ecosystem includes regional tourism boards and funding from European and metropolitan sources, enhancing credibility and reach.

Security posture

The website demonstrates a mature security posture with HTTPS enforced and no exposed sensitive data. However, it lacks several security best practices such as security headers (CSP, HSTS, X-Frame-Options) and dedicated security policies. There is no visible incident response or vulnerability disclosure mechanism, which could limit responsiveness to security incidents. Privacy compliance is well addressed with GDPR-aligned policies and cookie consent. The absence of vulnerable libraries or insecure forms is positive. Overall, the security maturity is good but could be improved by formalizing security governance and enhancing technical controls.

Recommendations

  1. Implement comprehensive security headers including Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), and X-Frame-Options to mitigate common web attacks.
  2. Publish a dedicated security policy and incident response plan on the website to improve transparency and preparedness.
  3. Introduce a vulnerability disclosure program or security.txt file to facilitate responsible reporting of security issues.
  4. Enhance accessibility features to improve usability for all users, including those with disabilities.
  5. Regularly audit and update third-party libraries and dependencies to prevent vulnerabilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Lüneburger Heide GmbH
Description
Wandern auf dem Heidschnuckenweg, schönster Wanderweg Deutschlands. 13 Etappen auf 222 km durch die Lüneburger Heide
Key services
Hiking trail information, Accommodation listings, Tourist information, Blog and news updates
Content quality
good
Branding
consistent

Technology

Stack
React, Next.js, JavaScript, CSS
Frameworks
Next.js
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Use of modern frameworks

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
good

Advertising

Transparency
poor

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
high

Key observations

  1. Website is a professional tourism portal for the Heidschnuckenweg hiking trail in Germany.
  2. Content is comprehensive with multiple sections including blog, accommodation, service, and route information.
  3. No signs of malicious content or security blocking.
  4. Use of modern web technologies and responsive design.
  5. Privacy and cookie policies are present and accessible.
  6. No direct contact emails or phone numbers found in the HTML; contact is via external contact page.
  7. No explicit security or incident response policies found on site.
  8. No vulnerability disclosure or security.txt file detected.
Technical notes

Notes

The website is built on a modern React and Next.js stack, enabling server-side rendering and good SEO performance. Hosting is provided by Hetzner, a reputable German hosting provider. The site uses optimized images with responsive loading and preloading strategies. Performance is moderate, with room for improvement in loading speed and caching. The site is mobile-optimized with a responsive design and basic accessibility features. SEO is supported by proper meta tags and structured navigation. There is no evidence of a traditional CMS; the site appears custom-built or statically generated with Next.js. Technical risks include missing security headers and potential technical debt in accessibility and performance optimization.
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

Reviews of this site

Share your experience with heidschnuckenweg.de. 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 heidschnuckenweg.de.

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.