Skip to main content

Security report for conversations.im

Daniel Gultsch · Technology · N/a

Medium risk. 7 critical or high findings in Security headers, GDPR outside view and 2 other checks.

Security score

52/100

Risk levelMedium

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

Conversations.im is a specialized technology business offering an open source Jabber/XMPP client for Android devices, emphasizing secure, private, and reliable instant messaging. The project is led by Daniel Gultsch and targets privacy-conscious users seeking end-to-end encrypted communication. The business model combines open source distribution with paid app sales on Google Play and professional support services. The website is well-structured, content-rich, and demonstrates a consistent brand identity focused on security and privacy. Technically, the website uses modern web technologies including Bootstrap and jQuery, with a mobile-optimized responsive design. The platform supports advanced XMPP extensions and encryption protocols such as OMEMO and OpenPGP. Hosting is managed via INWX nameservers, and the domain registration is consistent with the business's history and claims. However, the site lacks explicit privacy and cookie policies, and no security headers were detected in the HTML content. From a security perspective, Conversations.im shows strong adherence to secure communication standards, including TLS encryption and support for multiple XMPP security extensions. The absence of published security policies and incident response contacts is a gap. No vulnerabilities or suspicious content were found. Overall, the site is trustworthy and professional but could improve transparency and compliance documentation. The overall risk is low, with recommendations to publish privacy and cookie policies, implement security headers, and provide incident response information to enhance trust and compliance.

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

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

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

Keep watching conversations.im

This scan found 27 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
62
Security headers
15
Email security
70
DNS health
70
Network security
40
GDPR outside view
53
Average
52

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

Conversations.im occupies a niche in the secure instant messaging market, leveraging the federated XMPP protocol and open source development to appeal to privacy-focused Android users. Its competitive advantage lies in its comprehensive support for modern encryption standards and mobile optimizations. Revenue streams include app sales on Google Play and professional support/customization services offered by the lead developer. The project benefits from a strong community presence on Codeberg and transparent development practices. Partnerships with hosting and code repository providers support its operations. Growth potential exists in expanding user base and enterprise adoption through professional services.

Security posture

The security posture of Conversations.im is robust in terms of encryption and protocol support, utilizing TLS for all communications and offering state-of-the-art end-to-end encryption via OMEMO and OpenPGP. The use of XMPP extensions like Stream Management and Client State Indication enhances reliability and privacy. However, the website lacks published security policies, incident response contacts, and security headers, which are important for comprehensive security governance and compliance. No exposed sensitive data or vulnerabilities were detected. The site demonstrates a security-aware culture but should improve transparency and formal documentation to meet higher compliance standards.

Recommendations

  1. Publish a comprehensive privacy policy and cookie policy with GDPR compliance details.
  2. Implement standard security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Provide clear incident response contact information including security@ or abuse@ email addresses.
  4. Enhance website accessibility features to improve user experience for all users.
  5. Consider adding analytics with privacy-respecting configurations to better understand user engagement.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Daniel Gultsch
Description
Conversations is a Jabber/XMPP client for Android 5.0+ smartphones optimized for mobile experience, supporting end-to-end encryption, group chats, media transfer, and open source development.
Key services
Instant messaging client, End-to-end encryption (OMEMO, OpenPGP), Group chat and media sharing, XMPP server account registration, Professional support and custom development
Content quality
excellent
Branding
consistent

Technology

Stack
HTML5, Bootstrap CSS, jQuery, JavaScript, XMPP protocol, OMEMO encryption, OpenPGP
Frameworks
Bootstrap
Platforms
Android
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • TLS encryption for client-server and server-server communication
  • Support for end-to-end encryption (OMEMO, OpenPGP)
  • XEP-0198 Stream Management for session resumption
  • XEP-0352 Client State Indication to reduce unnecessary traffic

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Ad networks
Flattr
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with rich content and no blocking mechanisms.
  2. No explicit privacy, cookie, or terms of service policies found on the main page.
  3. Contact information is limited to a link to the maintainer's personal website; no direct emails or phone numbers found.
  4. Strong emphasis on open source, security, and privacy features.
  5. Use of modern web technologies and mobile optimization is evident.
  6. No visible analytics or tracking scripts detected except Flattr for donations.
  7. No security headers detected in the HTML content; server headers unknown.
  8. WHOIS data shows domain is registered with INWX nameservers and expires in 2026.
  9. No signs of suspicious or malicious content.
Technical notes

Notes

The website is built on a solid technical foundation using Bootstrap for responsive design and jQuery for interactivity. It supports modern web standards and is optimized for mobile devices. The use of XMPP protocol extensions and encryption technologies indicates a mature technical infrastructure for the core product. Hosting via INWX is stable and appropriate. Performance is moderate with no major issues detected. However, the absence of security headers and privacy policies indicates some technical debt in compliance and security best practices. Opportunities exist to modernize security configurations and improve accessibility and SEO further.
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

Earlier scans of this domain

  1. 50/100Medium36 findingsView report
Reviews of this site

Share your experience with conversations.im. 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 conversations.im.

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.