Skip to main content

Security report for lodur-so.ch

Other · N/a

Medium risk. 7 critical or high findings in Security headers, GDPR outside view and 2 other checks.

Security score

67/100

Risk levelMedium

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

The website lodur-so.ch currently presents only minimal content, consisting solely of the domain name text with no additional information or metadata. This suggests the site is either a placeholder or under construction, lacking any visible business description, services, or contact details. The absence of privacy, cookie, or terms of service policies further indicates a low level of digital maturity. Technically, the site does not reveal any frameworks, CMS, or hosting details, and no security headers or SSL configuration data are available, implying a lack of basic security measures such as HTTPS. The WHOIS data is privacy protected, which limits transparency about the registrant and reduces trustworthiness. Overall, the security posture is weak due to missing HTTPS and absence of security best practices. The site does not contain any adult or explicit content and is safe for general audiences. Given these factors, the overall risk is elevated due to poor content quality, lack of security controls, and minimal business credibility. Strategic recommendations include implementing HTTPS, publishing privacy and cookie policies, adding contact information, and enhancing website content and technical SEO to improve trust and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
40/ 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

7 findings rated critical or high. Fix these first.

  1. 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 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';…
  2. GDPR outside view

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

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • High

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

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

Keep watching lodur-so.ch

This scan found 22 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
77
Security headers
30
Email security
85
DNS health
70
Network security
100
GDPR outside view
40
Average
67

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

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 extremely limited website content and privacy-protected WHOIS data, no meaningful business intelligence can be derived. There is no indication of company name, sector, market position, or business model. The lack of contact details and policies suggests the entity behind the domain is either very small, inactive, or in early development stages. No partnerships or subsidiaries are identifiable. The absence of branding and trust indicators further limits competitive analysis or growth insights.

Security posture

The security posture of lodur-so.ch is currently very weak. The site lacks HTTPS, exposing visitors to potential interception risks. No security headers are present to mitigate common web attacks. There is no evidence of vulnerability disclosure or incident response policies. The absence of privacy and cookie policies indicates non-compliance with GDPR and related regulations. The privacy-protected WHOIS data reduces transparency but is not uncommon for small or new businesses. Overall, the site does not demonstrate adherence to security best practices, increasing risk exposure.

Recommendations

  1. Implement a valid SSL certificate and enforce HTTPS across the website.
  2. Develop and publish comprehensive privacy and cookie policies to ensure GDPR compliance.
  3. Add clear contact information including email and phone to improve business credibility and user trust.
  4. Incorporate security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  5. Enhance website content with meaningful business information, metadata, and SEO optimization to improve user experience and search visibility.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Content quality
poor
Branding
inconsistent

Technology

Performance
moderate
Mobile
poor
Accessibility
poor
SEO
poor

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

Design
poor
User experience
poor
Content relevance
poor
Navigation
poor
Professionalism
poor
Trustworthiness
low

Key observations

  1. Website content is extremely minimal, consisting only of the domain name text.
  2. No metadata, no SEO tags, no structured data, no forms, no contact information.
  3. No external links or social media links present.
  4. No scripts or technologies detected from the HTML content.
  5. No security headers or SSL configuration data available.
  6. WHOIS data is privacy protected, limiting transparency.
  7. No privacy, cookie, or terms of service policies found.
  8. No business or security policies disclosed.
  9. Website appears to be a placeholder or under construction.
Technical notes

Notes

The website's technical implementation is minimal, with no detectable CMS, frameworks, or third-party technologies. The HTML content is extremely sparse, lacking metadata, scripts, or structured data. No performance or accessibility features are evident. The absence of HTTPS and security headers indicates outdated or incomplete technical configuration. The site likely has moderate loading speed due to minimal content but scores poorly on mobile optimization and SEO. Modernization opportunities include adopting a CMS, improving metadata, and implementing security best practices.
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 lodur-so.ch. 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 lodur-so.ch.

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.