Skip to main content

Security report for protekta.ch

ProtektaFe · Other · Switzerland

Medium risk. 6 critical or high findings in Security headers and GDPR outside view.

Security score

63/100

Risk levelMedium

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

Protekta.ch appears to be a website with minimal publicly accessible content, primarily serving as a frontend application titled 'ProtektaFe'. The lack of visible business descriptions, contact information, or policy documents suggests the site is either under development or intended for internal or limited use. The technical infrastructure includes an Express backend and Angular frontend, hosted behind Cloudflare with modern TLS protocols enabled, indicating a baseline level of digital maturity. However, the absence of SEO metadata, structured data, and comprehensive content limits its public engagement and discoverability. Security posture is moderate with HTTPS enforced and OCSP stapling active, but lacks critical security headers such as HSTS and Content-Security-Policy, and does not provide privacy or cookie policies, which are essential for compliance and user trust. Overall, the site presents a low risk but also low transparency and trustworthiness due to minimal information exposure.

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

6 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 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';…
  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

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

Keep watching protekta.ch

This scan found 17 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
82
Security headers
15
Email security
50
DNS health
90
Network security
100
GDPR outside view
40
Average
63

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 absence of explicit business information, it is not possible to ascertain Protekta.ch's market positioning, business model, or target audience. The domain is registered and uses Swiss-based DNS and mail infrastructure, suggesting a Swiss entity. The use of modern web technologies and Cloudflare hosting indicates an intent to maintain a secure and performant platform. No partnerships, certifications, or trust signals are evident. The minimal content and lack of contact details limit insights into revenue streams or customer segments. The site may be in early stages or designed for a niche internal audience.

Security posture

The website enforces HTTPS with TLS 1.3 and 1.2 protocols and uses Cloudflare as a CDN and security provider. OCSP stapling is enabled and successful, enhancing certificate validation performance. Cookies are set with HttpOnly and Secure flags, but the SameSite attribute is set to None, which requires careful review to avoid CSRF risks. No HSTS header is present, which is a missed opportunity for enforcing strict transport security. Security headers such as Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options are absent, reducing defense-in-depth. No known vulnerabilities or exposed sensitive data were detected. The site lacks privacy and cookie policies, which is a compliance gap. Incident response and vulnerability disclosure mechanisms are not found, indicating limited security transparency.

Recommendations

  1. Enable HTTP Strict Transport Security (HSTS) with includeSubDomains and preload to enforce HTTPS.
  2. Implement comprehensive security headers including Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, and Referrer-Policy.
  3. Publish clear privacy and cookie policies with user consent mechanisms to improve compliance and trust.
  4. Add security.txt and vulnerability disclosure information to facilitate responsible reporting.
  5. Enhance website content with business information, contact details, and SEO metadata to improve credibility and user experience.
Technical notes

Notes

The website uses an Express.js backend and Angular frontend framework, indicating a modern JavaScript-based stack. Hosting is via Cloudflare, providing CDN and security features. TLS configuration supports modern protocols but lacks advanced security headers. Performance data is unavailable, but resource counts and page size are zero, indicating minimal or placeholder content. The site is mobile responsive at a basic level but lacks accessibility and SEO optimizations. DNS configuration is standard with Swisscom mail servers and multiple authoritative nameservers, but DNSSEC is disabled and CAA records appear misconfigured. Overall, the technical infrastructure is sound but underutilized due to minimal content and missing 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 protekta.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 protekta.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.