Skip to main content

Security report for matrix.to

Matrix.org · Technology · N/a

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

Security score

67/100

Risk levelMedium

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

Matrix.to is a specialized web service that facilitates the creation of shareable links to Matrix network rooms, users, and messages. It operates as part of the Matrix.org ecosystem, which is focused on decentralized and secure communication. The website serves a niche audience of Matrix users and communities seeking easy access and sharing capabilities without being tied to specific client applications. The business model appears to be community and open source driven, with no direct monetization evident on the site. Technically, the website uses JavaScript and CSS with client-side processing to preserve user privacy. The site is functional and moderately optimized for performance and mobile use, though accessibility and SEO optimizations are basic. There is no evidence of a CMS or advanced frameworks. The site links to GitHub repositories, indicating open source transparency. From a security perspective, the site lacks explicit security headers and documented security policies. HTTPS usage is assumed but not confirmed from the data. No privacy or cookie policies are present, which limits compliance with GDPR and other privacy regulations. The absence of contact information and incident response details reduces transparency. However, the association with Matrix.org and open source nature provide some trust signals. Overall, the site is safe, professional, and trustworthy for its intended purpose but would benefit from enhanced privacy compliance, security policies, and contact transparency to improve user trust and regulatory adherence.

Scanned

This is an earlier scan of matrix.to. View the latest report

NIS2 and GDPR posture

GDPR outside view
50/ 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 Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • 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

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

Keep watching matrix.to

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. 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
75
Security headers
30
Email security
70
DNS health
75
Network security
100
GDPR outside view
50
Average
67

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 matrix.to, from OffSeq Breach.

No leaked records found

Breach holds no records for matrix.to 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

Matrix.to operates within the decentralized communication sector, leveraging the Matrix.org Foundation's ecosystem. Its competitive advantage lies in providing a simple, app-agnostic link creation tool that supports Matrix's open network philosophy. The business model is likely non-commercial or community-supported, focusing on user adoption and ecosystem growth rather than direct revenue. The target customers are Matrix users, developers, and communities. The presence of GitHub links suggests active community involvement and potential for collaborative development. The site does not display commercial partnerships or payment processing, indicating a focus on open source and community trust rather than monetization. Growth indicators include integration with multiple Matrix clients and ongoing open source development.

Security posture

The security posture of matrix.to is moderate. The site uses client-side processing to enhance privacy, which is a positive practice. However, the lack of visible security headers and absence of documented security policies or incident response contacts are weaknesses. No vulnerabilities or exposed sensitive data were detected in the provided content. The site does not implement privacy or cookie policies, which is a compliance gap. The absence of HTTPS confirmation is a concern but likely present given the Matrix.org ecosystem standards. Overall, the site demonstrates basic security hygiene but should improve transparency and compliance to strengthen its security posture.

Recommendations

  1. Implement and publicly display a comprehensive privacy policy and cookie policy to improve GDPR compliance.
  2. Add security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to enhance protection against common web attacks.
  3. Provide clear contact information including security and incident response contacts to improve transparency and trust.
  4. Confirm and enforce HTTPS usage site-wide to ensure secure communications.
  5. Enhance accessibility and mobile optimization to improve user experience and broaden audience reach.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Matrix.org
Description
Matrix.to is a service that creates shareable links to Matrix rooms, users, or messages without being tied to any app. It facilitates decentralized and secure communication on the Matrix network.
Key services
Creating shareable links to Matrix rooms, Creating shareable links to Matrix users, Creating shareable links to Matrix messages
Content quality
good
Branding
consistent

Technology

Stack
JavaScript, RegeneratorRuntime, CSS
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
60/100
Good practices seen
  • Client-side processing to preserve privacy

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is a functional tool for creating Matrix communication links.
  2. No privacy, cookie, or terms of service policies found on the page.
  3. No contact emails or phone numbers explicitly provided.
  4. Content is minimal but relevant and professional.
  5. No advertising or tracking detected.
  6. No security headers visible in provided data.
  7. No explicit security or incident response information.
  8. Open source project links enhance trust.
  9. No signs of WAF or content blocking.
Technical notes

Notes

The website is built using standard web technologies including JavaScript and CSS, with client-side rendering indicated by the use of regeneratorRuntime and bundled JS/CSS files. There is no evidence of a CMS or server-side frameworks. The site loads a CSS bundle and a JavaScript bundle, suggesting a modern modular build process. Performance is moderate with basic mobile optimization. SEO is basic with meta tags for description and Twitter cards but no Open Graph or JSON-LD structured data. Accessibility features are minimal, with a noscript fallback message. Hosting provider and SSL configuration details are not provided, limiting deeper technical assessment. Overall, the technical implementation is functional but could benefit from modernization and enhanced SEO and accessibility features.
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. 67/100Medium28 findingsView report
  2. 67/100 +2Medium28 findingsView report
  3. 65/100Medium24 findingsView report
Reviews of this site

Share your experience with matrix.to. 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 matrix.to.

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.