Skip to main content

Security report for digt.ch

Digt AG · E-commerce · Switzerland

Medium risk. 5 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

67/100

Risk levelMedium

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

Digt AG is a Swiss-based company specializing in community building, brand creation, and product promotion within the e-commerce sector. Their website presents a professional and modern digital presence, targeting businesses seeking to grow their communities, create brands, and promote products in the Swiss market. The company appears to be relatively new, founded around 2021, with a clear focus on service provision in e-commerce and brand distribution. Technically, the website is built on WordPress with a solid tech stack including Bootstrap, jQuery, and SEO tools like Yoast. It is mobile-optimized and uses Google Analytics and Tag Manager for tracking, indicating a moderate level of digital maturity. Security-wise, the site enforces HTTPS and avoids exposing sensitive data, but lacks some security headers and explicit policies, which could be improved. Overall, the site is trustworthy and professional, with minor gaps in privacy compliance and security transparency.

Scanned

NIS2 and GDPR posture

GDPR outside view
53/ 100 · Medium
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

5 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 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

  3. 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.

    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching digt.ch

This scan found 24 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
75
Security headers
25
Email security
70
DNS health
80
Network security
100
GDPR outside view
53
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

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 digt.ch, from OffSeq Breach.

No leaked records found

Breach holds no records for digt.ch 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 company positions itself as a niche service provider in the Swiss e-commerce ecosystem, offering tools and services to activate and grow customer communities, create and distribute brands, and promote products effectively. Their business model revolves around B2B services, leveraging partnerships and digital platforms to extend market reach. The presence of multilingual support (English and German) and a supplier login portal suggests a growing and structured operation. The company’s website content and structure indicate a focus on quality service delivery and brand trust. However, the absence of detailed certifications or security policies may limit appeal to highly regulated sectors.

Security posture

The website demonstrates a baseline security posture with HTTPS enabled and no visible exposure of sensitive information. However, it lacks advanced security headers such as Content-Security-Policy and X-Frame-Options, which are recommended to mitigate common web attacks. There is no published security policy or incident response contact, which reduces transparency and preparedness perception. The use of third-party scripts like Google Analytics and Tag Manager is standard but requires ongoing monitoring for vulnerabilities. GDPR compliance is partially addressed via a privacy policy, but the absence of a cookie consent mechanism is a compliance gap. Overall, the security posture is moderate but can be enhanced with additional controls and transparency.

Recommendations

  1. Implement comprehensive security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  2. Add a cookie consent banner/mechanism to comply fully with GDPR and ePrivacy regulations.
  3. Publish a dedicated security policy and provide clear incident response contact information.
  4. Regularly audit and update third-party scripts to minimize vulnerability exposure.
  5. Consider establishing a vulnerability disclosure program or security.txt file to enhance trust.

Contact details published on the site

Addresses
Legal name
Digt AG
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Digt AG
Description
We create & distribute
Key services
Community activation and growth, Brand creation and distribution, Product and service promotion and sales
Content quality
good
Branding
consistent

Technology

Stack
WordPress, Yoast SEO, jQuery, Bootstrap, Font Awesome, Google Analytics, Google Tag Manager, Bellows Accordion Menu, Site Kit by Google, WPML Multilingual CMS
Frameworks
Bootstrap
Platforms
WordPress
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Use of Google Tag Manager and Analytics with async loading

Analytics and tracking

Services
Google Analytics, Google Tag Manager
Tracking level
moderate
Privacy practices
basic

Advertising

Marketing tools
Yoast SEO
Transparency
basic

Site quality

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

Key observations

  1. Website is professionally designed and well-structured
  2. Content is business-focused and relevant to e-commerce and brand promotion
  3. No signs of malicious or suspicious activity
  4. Use of modern web technologies and SEO best practices
  5. Lacks explicit cookie consent mechanism
  6. No visible security policy or incident response information
Technical notes

Notes

The website is built on a modern WordPress platform with a well-integrated tech stack including Bootstrap for responsive design, jQuery for interactivity, and Yoast SEO for search optimization. Google Analytics and Tag Manager are used for user tracking and marketing insights. The site loads scripts asynchronously to improve performance. Mobile optimization is good, with specific background images and video content tailored for mobile devices. Accessibility features are basic but present. The site uses multilingual support via WPML, enhancing reach. Performance is moderate, with room for optimization in script loading and caching. Overall, the technical implementation supports a professional and scalable web presence.
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 digt.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 digt.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.