Skip to main content

Security report for tria.ge

Recorded Future · Technology · N/a

Medium risk. 4 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

68/100

Risk levelMedium

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

Recorded Future Triage is a specialized cybersecurity service offering a malware analysis sandbox designed for security professionals to dissect malware samples, track malware trends, and classify threats. The platform supports high-volume sample submissions and provides public reports, positioning itself as a valuable tool in the cybersecurity threat intelligence market. The website reflects a mature business with a domain age consistent with its founding in 2014 and is part of the Recorded Future brand. Technically, the website employs modern web technologies including HTML5, CSS3, JavaScript, and integrates Google reCAPTCHA for security on its login forms. Hosting and DNS services are provided via Cloudflare, ensuring good performance and security. The site is mobile optimized and SEO friendly, though accessibility features are basic. Security best practices such as HTTPS, CSRF tokens, and CAPTCHA are implemented, but additional security headers and explicit security policies could enhance the posture. The security posture is solid with no visible vulnerabilities or exposed sensitive data. Privacy compliance is evident with a cookie consent banner and privacy policy, though direct contact information and incident response details are not publicly available. The site maintains a professional appearance with consistent branding and trustworthy external links. Overall, the website presents a low-risk profile with strong business credibility and technical maturity. Strategic recommendations include enhancing security headers, publishing a security policy, and providing clearer contact channels for incident response to further improve trust and compliance.

Scanned

NIS2 and GDPR posture

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

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

    • 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

  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.

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1
    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

  3. DNS health

    DNS sends visitors and email to the right servers. Misconfigured records can cause outages or let someone redirect your traffic.

    • High

      Weak SPF Policy

      SPF record has permissive policy allowing any server to send email

      What to do: Use -all or ~all qualifier for better email security

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

Keep watching tria.ge

This scan found 21 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
32
Security headers
85
Email security
70
DNS health
55
Network security
100
GDPR outside view
68
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

Technical appendix

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

Business context

Business profile

Recorded Future Triage operates in the cybersecurity technology sector, focusing on malware analysis and threat intelligence. Its business model is SaaS-based, targeting cybersecurity professionals and researchers. The company leverages its parent brand Recorded Future to establish market credibility. The platform's key competitive advantages include a customizable sandbox environment, high-volume sample processing, and integration with public malware reports. Revenue streams likely include subscription services and enterprise licensing. The partnership ecosystem includes media outlets like The Record and integration with major authentication providers such as Google and Github. Growth indicators include regular updates and changelogs published on partner blogs. The company maintains a focused market presence with a medium-sized operational scale.

Security posture

The website demonstrates a mature security posture with HTTPS enforced, use of Google reCAPTCHA on login forms, and CSRF protection tokens. No security.txt or explicit incident response contacts are published, which is a gap in transparency. Security headers like Content-Security-Policy and X-Frame-Options are not detected, representing an area for improvement. No vulnerabilities or exposed sensitive data were found in the HTML content. Privacy compliance is supported by cookie consent mechanisms and a privacy policy. Overall, the security culture appears professional but could benefit from enhanced disclosure and header configurations to meet higher compliance standards such as GDPR and NIS2.

Recommendations

  1. Implement and publish comprehensive security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  2. Create and publish a security policy page detailing incident response procedures and contact channels.
  3. Add a security.txt file to facilitate vulnerability disclosures and improve transparency.
  4. Provide clear contact information for security incidents, such as security@ or abuse@ email addresses.
  5. Enhance accessibility features to improve compliance and user experience for all users.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Recorded Future
Description
Recorded Future Triage offers a malware analysis sandbox for dissecting malware samples, providing malware trends, and a customizable environment for in-depth analysis and classification.
Key services
Malware analysis sandbox, Malware trend reporting, Sample submission and classification, Public malware reports access
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS3, JavaScript, Google reCAPTCHA, Cloudflare DNS, SVG graphics
Performance
fast
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Use of Google reCAPTCHA on login form
  • CSRF token present in login form
  • No exposed sensitive data in HTML

Analytics and tracking

Tracking level
minimal
Privacy practices
good

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Website is a professional malware analysis sandbox service by Recorded Future
  2. Content is accessible and well-structured with no blocking mechanisms
  3. Security best practices are partially implemented with room for improvement
  4. Privacy and cookie policies are present with consent mechanism
  5. No direct contact emails or phone numbers found on the landing page
  6. Login form uses Google reCAPTCHA and CSRF tokens for security
  7. External links mostly point to trusted domains related to Recorded Future and partners
Technical notes

Notes

The website is built with modern web standards including HTML5, CSS3, and JavaScript, with SVG graphics for logos and icons. It uses Google reCAPTCHA for bot mitigation and Cloudflare for DNS and likely CDN services, contributing to fast load times and reliable hosting. The site is mobile optimized and SEO friendly with proper meta tags and Open Graph data. No CMS or frameworks were explicitly detected, suggesting a custom or lightweight implementation. Performance is fast with asynchronous script loading. Technical risks are minimal but could be reduced further by adding security headers and improving accessibility compliance.
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 tria.ge. 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 tria.ge.

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.