Skip to main content

Security report for communi5.com

Communi5 · Telecommunications · Austria

High risk. 8 critical or high findings in GDPR outside view, SSL/TLS and 2 other checks.

Security score

31/100

Risk levelHigh

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

Communi5 is a medium-sized Austrian software manufacturer specializing in communications solutions for service providers, focusing on UCaaS and Cloud PBX offerings. The company demonstrates a mature market position with a future-oriented approach, integrating modern collaboration tools such as MS Teams. The website reflects a professional and consistent brand image with comprehensive content targeting service providers and business customers. Technically, the site is built on WordPress with Elementor and uses modern UI components like Smart Slider 3, but lacks a valid SSL certificate and modern TLS support, which significantly impacts its security posture. Privacy compliance is well addressed with clear cookie and privacy policies and consent mechanisms. However, the absence of explicit security policies and incident response information is noted. Overall, the site is functional and professional but requires urgent security improvements to protect user data and enhance trust.

Scanned

NIS2 and GDPR posture

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

8 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 communi5.com

This scan found 19 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
20
GDPR outside view
18
Average
31

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

Communi5 operates in the telecommunications sector, offering unified communications and collaboration solutions tailored for service providers. Its business model revolves around software manufacturing and service provision, with key services including Cloud UC platforms, SIP trunking, voice network transformation, and MS Teams integration. The company leverages a partnership ecosystem and maintains active social media channels to engage with its audience. The website content and structured data indicate a well-established company with a focus on innovation and customer-centric development. The absence of detailed financial or registration data limits deeper business intelligence insights.

Security posture

The current security posture of the website is weak due to the lack of a valid SSL certificate and disabled TLS protocols, exposing users to potential data interception risks. While no critical vulnerabilities like Heartbleed or POODLE are detected, the absence of HTTPS and security headers such as HSTS and OCSP stapling are significant gaps. The site uses secure forms for contact but lacks explicit security or incident response policies. The overall security score is low, and immediate remediation is recommended to implement HTTPS and enhance security headers to protect both the company and its users.

Recommendations

  1. Install and maintain a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Enable modern TLS protocols (TLS 1.2 and 1.3) and disable outdated versions.
  3. Implement HTTP Strict Transport Security (HSTS) with includeSubDomains and preload options.
  4. Enable OCSP stapling and session resumption to improve SSL performance and security.
  5. Publish a clear security policy and incident response plan accessible from the website.
  6. Enhance privacy compliance by providing explicit data retention policies and DPO contact information.
Technical notes

Notes

The website is built on a WordPress CMS platform using PHP 8.2 and Apache 2.4. It employs Elementor for page building and Smart Slider 3 for interactive content. The site uses jQuery and Font Awesome for UI elements. Hosting is provided by rzone.de with mail services via Microsoft Outlook. Performance metrics are missing, indicating potential slow loading or measurement issues. The site is mobile-optimized with responsive design but has basic accessibility features. SEO is well addressed with proper meta tags, Open Graph, and JSON-LD structured data. Technical debt is moderate due to missing SSL and security enhancements, which should be prioritized to reduce operational risks.
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 communi5.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 communi5.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.