Skip to main content

Security report for trigo.at

TRIGO GmbH · Technology · Austria

High risk. 7 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

TRIGO GmbH is a specialized technology company focused on delivering tailored software solutions that bridge user-centric design with technical expertise. Their market position is that of a cloud-native expert, offering key services such as Data System Development (notably Exosphere), OpenShift consulting and migration, and Single Sign-On solutions leveraging Keycloak. The company targets businesses seeking to scale IT infrastructure, integrate applications, and leverage data effectively. Technically, the website is built on modern frameworks like Next.js and Chakra UI, hosted on Vercel, but lacks HTTPS which is a critical security shortfall. The absence of SSL/TLS exposes the site to risks and undermines trust. Security headers are present but insufficient without HTTPS. Privacy compliance is partial, with a privacy policy present but no cookie consent mechanism detected. Overall, the site is professional and content-rich but requires urgent security improvements to meet modern standards.

Scanned

NIS2 and GDPR posture

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

7 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

    • 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 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 trigo.at

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
0
Security headers
30
Email security
75
DNS health
85
Network security
100
GDPR outside view
0
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

Technical appendix

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

Business context

Business profile

TRIGO GmbH operates in the technology sector with a small company size and a focus on IT consulting and software development. Their business model revolves around providing customized cloud-native solutions, particularly in Kubernetes/OpenShift environments and identity management via Keycloak. The company maintains partnerships with notable organizations such as Loxone and several Austrian enterprises, enhancing their market credibility. Their digital presence includes social media and a professional website with clear service offerings. Revenue streams likely derive from consulting, managed services, and software development projects. Growth indicators include a modern tech stack and active partner ecosystem. Strategic observations suggest a focus on scalability and integration challenges faced by clients, positioning TRIGO as a niche specialist in cloud and identity solutions.

Security posture

The current security posture of the website is weak due to the lack of HTTPS and SSL certificate, which is a critical vulnerability. While some security headers are present, the absence of TLS protocols and cipher suites means data transmitted is not encrypted, exposing users to interception and man-in-the-middle attacks. No vulnerability disclosure or incident response policies are publicly available, and no security.txt file is found. The site does not implement cookie consent mechanisms, which may impact GDPR compliance. The DNS setup is standard with no DNSSEC or CAA records, but no suspicious patterns are detected. Overall, the security maturity is low, and immediate remediation is required to secure communications and improve trust.

Recommendations

  1. Install and configure a valid SSL/TLS certificate to enable HTTPS across the entire website.
  2. Implement and enforce HSTS with includeSubDomains and preload flags to enhance transport security.
  3. Add a cookie consent mechanism to comply with GDPR and improve privacy transparency.
  4. Publish a security policy and incident response contact information to demonstrate security maturity.
  5. Enable OCSP stapling and session resumption to improve SSL performance and security.
Technical notes

Notes

The website uses a modern technology stack including React, Next.js, and Chakra UI, hosted on Vercel, which supports scalability and performance. However, performance metrics are missing or zero, indicating a lack of monitoring or optimization data. The site is mobile optimized and SEO friendly with proper meta tags and Open Graph data. Accessibility is basic but could be improved. The DNS configuration is standard with Google MX records and DigitalOcean nameservers. No CMS is detected, indicating a custom or static site generation approach. Technical risks include the lack of HTTPS and missing security best practices, which could impact business operations and user trust if not addressed promptly.
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 trigo.at. 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 trigo.at.

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.