Skip to main content

Security report for triax.com

TRIAX · Telecommunications · United Kingdom

High risk. 6 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

37/100

Risk levelHigh

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

TRIAX is a UK-based manufacturer and distributor specializing in multimedia equipment for the trade sector, focusing on signal reception, TV distribution, and IP network solutions primarily for the hospitality and telecommunications industries. The company has a strong market presence with over 75 years of history and a wide distributor network. Their website is built on WordPress with WooCommerce, leveraging modern themes and plugins such as Divi and Yoast SEO to provide a professional and user-friendly experience. Despite the comprehensive content and good privacy compliance, the absence of a valid SSL/TLS certificate is a critical security gap that exposes users to potential risks. The site includes active cookie consent mechanisms and detailed privacy policies, reflecting a commitment to GDPR compliance. Overall, the business demonstrates solid digital maturity but requires urgent security improvements to protect user data and enhance trust.

Scanned

NIS2 and GDPR posture

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

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

    • 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 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 triax.com

This scan found 18 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
0
Security headers
15
Email security
50
DNS health
85
Network security
40
GDPR outside view
33
Average
37

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

TRIAX operates as a specialized B2B supplier in the multimedia and connectivity sector, targeting trade customers in hospitality, healthcare, and residential markets. Their business model centers on providing innovative hardware and software solutions that enable efficient video, audio, and data signal distribution. The company maintains a strong partnership ecosystem, including regional distributors and service providers, and actively communicates through news updates and social media channels. Their ISO 9001:2015 certification underscores a commitment to quality management. The website's content and structure support their market positioning as a reliable and innovative provider, though the lack of direct company email contacts on the site suggests a preference for contact via forms or phone.

Security posture

The website's security posture is currently weak due to the lack of HTTPS support, which is a critical vulnerability that undermines data confidentiality and integrity. No advanced security headers or mechanisms such as HSTS or OCSP stapling are implemented. However, there are no signs of exposed sensitive data or vulnerable libraries. The site uses standard WordPress security practices but would benefit from enhanced security configurations and regular audits. The presence of a cookie consent mechanism and privacy policy indicates awareness of privacy regulations, but the absence of incident response contacts or security policies is a gap in comprehensive security governance.

Recommendations

  1. Implement a valid SSL/TLS certificate to enable HTTPS across the entire site immediately.
  2. Configure security headers including HSTS, Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Enable OCSP stapling and support modern TLS protocols (TLS 1.2 or 1.3) to improve encryption strength and performance.
  4. Add explicit security and incident response policies accessible on the website, including dedicated security contact channels.
  5. Regularly update all plugins, themes, and WordPress core to mitigate vulnerabilities and maintain compliance.

Contact details published on the site

Addresses
Legal name
TRIAX UK
Technical notes

Notes

The website is built on a robust WordPress platform using the Divi theme and WooCommerce for e-commerce capabilities. It integrates several modern technologies including jQuery, Google Analytics, and GTranslate for multilingual support. The site is well-structured with comprehensive metadata, Open Graph tags, and JSON-LD structured data for SEO optimization. Performance data is unavailable, but the site appears optimized for mobile with responsive design elements. Hosting is provided via DigitalOcean with Cloudflare DNS, indicating a reliable infrastructure. However, the absence of SSL/TLS is a significant technical risk. The site uses multiple JavaScript libraries and plugins, which should be regularly audited for security and performance.
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 triax.com. 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 triax.com.

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.