Skip to main content

Security report for signal.me

Signal · Technology · United States

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

Security score

68/100

Risk levelMedium

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

Signal is a well-established nonprofit organization providing a secure, privacy-focused messaging platform widely recognized for its strong encryption and open-source approach. The website signal.me serves as a contact and redirect landing page, linking users to the main signal.org domain and app download resources. The business is positioned as a leader in secure communications, targeting privacy-conscious users globally. The domain and website content align with the organization's mission and market presence. Technically, the site uses modern CSS frameworks like Bulma and JavaScript, hosted behind Cloudflare DNS services. The site is mobile optimized with responsive navigation and basic accessibility features. However, some security best practices such as DNSSEC and security headers are not implemented on this domain. The site uses HTTPS with good SSL configuration, ensuring secure connections. From a security perspective, the website shows good domain registration protections and no visible vulnerabilities or exposed sensitive data. Privacy compliance is strong on the main domain, though this subdomain lacks explicit cookie consent mechanisms. No forms or tracking scripts are present, minimizing data collection risks. Contact information is limited to a media inquiry email, with no phone or physical address listed. Overall, the website is trustworthy, professional, and safe for general audiences. Recommendations include enabling DNSSEC, adding security headers, and publishing a vulnerability disclosure policy to enhance security posture and transparency.

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 signal.me

This scan found 23 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
57
Security headers
30
Email security
80
DNS health
85
Network security
100
GDPR outside view
53
Average
68

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention signal.me, from OffSeq Breach.

No leaked records found

Breach holds no records for signal.me right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

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

Business context

Business profile

Signal operates as a nonprofit technology organization focused on secure messaging services. Its market position is strong due to its open-source model, privacy-first approach, and widespread adoption. Revenue streams primarily come from donations and grants rather than commercial sales. The target audience includes privacy-conscious individuals, activists, journalists, and general users seeking secure communication. The company maintains a consistent brand and has a robust partnership ecosystem visible through its social media and open-source presence. Growth indicators include active development and community engagement. The business model emphasizes trust, transparency, and user empowerment.

Security posture

Signal demonstrates a mature security posture with enforced HTTPS, domain registration protections, and minimal attack surface on this landing page. However, the absence of DNSSEC and security headers represents areas for improvement. No incident response or security contact information is provided on this domain, which could hinder rapid vulnerability reporting. The lack of a security.txt or vulnerability disclosure page limits transparency. Privacy compliance is strong on the main site but not explicitly reflected here. Overall, the security culture appears robust but could benefit from enhanced communication and technical controls.

Recommendations

  1. Enable DNSSEC on the domain to prevent DNS spoofing and enhance integrity.
  2. Implement standard security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Publish a dedicated security policy and vulnerability disclosure page or security.txt file.
  4. Add explicit cookie policy and consent mechanisms to comply with privacy regulations.
  5. Provide clear incident response contact channels such as security@ or abuse@ email addresses.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Signal
Description
Signal is a nonprofit organization providing a secure private messaging platform.
Key services
Secure messaging, Voice and video calls, Encrypted communication
Content quality
good
Branding
consistent

Technology

Stack
Bulma CSS, JavaScript, Cloudflare DNS
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • Domain status clientDeleteProhibited, clientTransferProhibited, clientUpdateProhibited

Analytics and tracking

Tracking level
minimal
Privacy practices
good

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is a landing/contact page for Signal messenger service.
  2. No forms present on the page.
  3. No cookie consent banner or explicit cookie policy found.
  4. Minimal tracking or analytics detected.
  5. Strong brand consistency with main signal.org domain.
  6. No security.txt or explicit vulnerability disclosure found.
  7. No phone numbers or physical addresses listed.
  8. Contact email for media inquiries present in footer.
  9. Mobile optimization is good with responsive navigation.
  10. No explicit privacy or security policy pages linked directly on this subdomain, but main site has comprehensive policies.
Technical notes

Notes

The website uses Bulma CSS framework and custom JavaScript for UI and navigation. Hosting is via Cloudflare DNS with no DNSSEC enabled. The site is mobile responsive and loads moderate assets including fonts and images. No CMS or backend platform is detected, indicating a static or minimal dynamic site. Performance is moderate with no evident heavy scripts or trackers. Accessibility is basic but functional. SEO is minimal with meta tags and Open Graph tags present but no structured data or JSON-LD. The technical stack is modern but could be enhanced with additional security and SEO optimizations.
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. 71/100Medium30 findingsView report
Reviews of this site

Share your experience with signal.me. 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 signal.me.

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.