Skip to main content

Security report for conversations.im

Daniel Gultsch · Technology · N/a

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

Security score

50/100

Risk levelMedium

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

Conversations.im is the official website for Conversations, an open source Jabber/XMPP client for Android devices. The project is led by Daniel Gultsch and targets users seeking secure, privacy-focused instant messaging solutions. The website provides comprehensive information about the app's features, security mechanisms including end-to-end encryption (OMEMO and OpenPGP), and technical details about XMPP protocol extensions supported. The business model revolves around open source software distribution with monetization through Google Play Store sales and professional support services. Technically, the website uses a modern tech stack including Bootstrap and jQuery, hosted on INWX nameservers, and is optimized for mobile devices with good SEO practices. Security posture is solid in terms of encryption and protocol use, but the website lacks published privacy policies, cookie consent mechanisms, and security headers, which are areas for improvement. No WAF or blocking mechanisms were detected, allowing full content access. Overall, the domain registration is consistent and trustworthy, supporting the legitimacy of the business.

Scanned

This is an earlier scan of conversations.im. View the latest report

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

8 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
52
Security headers
15
Email security
70
DNS health
70
Network security
40
GDPR outside view
53
Average
50

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

The Conversations project occupies a niche in the secure instant messaging market, focusing on the XMPP protocol and open source principles. Its competitive advantage lies in strong encryption support, multi-device synchronization, and a community-driven development model. Revenue streams include app sales on Google Play and paid professional support. The target customers are privacy-conscious Android users and organizations seeking secure communication tools. The project maintains partnerships with Codeberg for source hosting and uses Flattr for donations. The business operates as a small entity led by a single maintainer, with no parent or subsidiary companies. The website content and testimonials reinforce a professional and trustworthy image, supporting growth and user confidence.

Security posture

The security maturity of Conversations.im is moderate to good. The app itself supports state-of-the-art encryption and secure communication protocols. However, the website lacks several standard security best practices such as security headers and published incident response or vulnerability disclosure policies. No forms or sensitive data collection reduce attack surface on the website. The absence of privacy and cookie policies is a compliance gap, especially under GDPR. The domain registration is consistent and not privacy-protected, which adds to trust. Overall, the security posture is adequate but could be enhanced by publishing formal policies and implementing security headers.

Recommendations

  1. Publish a comprehensive privacy policy and cookie policy on the website to improve GDPR compliance and user trust.
  2. Implement standard security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to enhance website security.
  3. Provide clear incident response and vulnerability disclosure information, including security contact emails or forms.
  4. Add terms of service to clarify user rights and obligations when using the app and services.
  5. Consider integrating minimal analytics with privacy-respecting configurations to better understand user engagement while maintaining privacy.
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 a unique mobile experience. It is an open source instant messaging client supporting end-to-end encryption, group chats, media transfer, and synchronization across devices.
Key services
Instant messaging client for Android, End-to-end encryption (OMEMO, OpenPGP), Group chats and conferences, Media transfer, Message synchronization across devices, 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
70/100
Good practices seen
  • Use of TLS encryption for communication
  • Support for end-to-end encryption (OMEMO, OpenPGP)
  • No forms collecting sensitive data on the website

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 no blocking or WAF challenges.
  2. No explicit privacy, cookie, or terms of service policies found on the site.
  3. Contact information is limited to a mention of the maintainer's name and link to personal website; no direct emails or phone numbers provided.
  4. The site promotes an open source Android XMPP client with strong emphasis on security and privacy.
  5. Technical content is detailed and well-structured, targeting technically savvy users.
  6. No forms or data collection mechanisms detected on the website.
  7. External links mostly point to trusted domains related to the project or technology.
  8. No analytics or tracking scripts detected except Flattr donation script.
  9. No security headers detected in the HTML content; SSL status unknown from provided data.
  10. No vulnerability disclosure or incident response information published.
Technical notes

Notes

The website is built using modern web technologies including Bootstrap for responsive design and jQuery for scripting. It is hosted on INWX nameservers, indicating a stable hosting environment. The site is mobile-optimized and SEO-friendly with proper meta tags and Open Graph data. Performance is moderate with asynchronous loading of external scripts like Flattr. No CMS was detected, suggesting a custom or static site. The absence of analytics and tracking scripts indicates a privacy-conscious approach but limits data-driven improvements. Technical debt appears low, but adding security headers and formal policies would modernize the security posture. Overall, the technical infrastructure supports the business goals effectively with room for incremental improvements.
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. 52/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.