Skip to main content

Security report for react.dev

Facebook, Inc. · Technology · United States

Medium risk. 7 critical or high findings in Email security, Security headers and 2 other checks.

Security score

62/100

Risk levelMedium

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

React.dev is the official website for React, a leading JavaScript library for building web and native user interfaces, maintained by Meta Platforms, Inc. The site provides comprehensive educational resources, API references, community links, and conference content targeting developers globally. It positions React as a foundational technology in modern web development with strong community and corporate backing. Technically, the website is built using modern frameworks such as Next.js and React itself, ensuring fast performance, mobile optimization, and accessibility. The use of Google Tag Manager indicates moderate user tracking for analytics purposes. Security-wise, the site enforces HTTPS and implements key security headers, but lacks publicly available privacy policies, cookie consent mechanisms, and security incident response information, which are areas for improvement. Overall, the site is professional, trustworthy, and safe for general audiences, reflecting the maturity and credibility of the React project and its parent company.

Scanned

This is an earlier scan of react.dev. 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

7 findings rated critical or high. Fix these first.

  1. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

  2. 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 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';…

  3. 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 react.dev

This scan found 26 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
72
Security headers
30
Email security
40
DNS health
75
Network security
100
GDPR outside view
53
Average
62

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

React.dev serves as a critical resource for developers using the React library, which is a major open-source project under Meta Platforms. The business model revolves around open-source software with community contributions and corporate sponsorship. The site supports a large developer ecosystem with learning materials, API documentation, and community engagement. Partnerships with frameworks like Next.js and Remix indicate a strategic ecosystem approach. The presence of conference videos and community translations highlights active community involvement and global reach. The website's content and structure support React's market leadership in UI development, targeting professional developers and organizations building web and native applications.

Security posture

The website demonstrates a solid security posture with HTTPS enforcement and multiple security headers such as Content-Security-Policy and Strict-Transport-Security. No exposed sensitive data or vulnerable libraries were detected in the analyzed content. However, the absence of published security policies, vulnerability disclosure programs, and incident response contacts limits transparency and preparedness from a compliance and trust perspective. The site would benefit from adding explicit privacy and cookie policies with consent mechanisms to align better with GDPR and other privacy regulations. Overall, the security maturity is good but could be enhanced by formalizing security governance and communication.

Recommendations

  1. Publish a comprehensive privacy policy and cookie policy with clear consent mechanisms to improve privacy compliance.
  2. Add a publicly accessible security policy and incident response contact information to enhance transparency and trust.
  3. Implement a vulnerability disclosure program or security.txt file to encourage responsible reporting of security issues.
  4. Provide contact details for a Data Protection Officer or security team to comply with regulatory requirements and improve user confidence.
  5. Regularly audit and update third-party dependencies and tracking scripts to maintain security and privacy standards.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Facebook, Inc.
Description
React is the library for web and native user interfaces. Build user interfaces out of individual pieces called components written in JavaScript. React is designed to let you seamlessly combine components written by independent people, teams, and organizations.
Key services
React JavaScript library, Documentation and learning resources, Community engagement, Conference and video content
Content quality
excellent
Branding
consistent

Technology

Stack
React, JavaScript, Next.js, Algolia (search), Google Tag Manager, CSS Modules, Web Vitals
Frameworks
Next.js, React
Platforms
Web
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
90/100
Good practices seen
  • HTTPS enforced
  • Use of security headers
  • No exposed sensitive data in HTML
  • No vulnerable libraries detected in scripts
  • No inline scripts with unsafe eval

Analytics and tracking

Services
Google Analytics (via Google Tag Manager)
Tracking level
moderate
Privacy practices
poor

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. No explicit privacy, cookie, or terms of service pages found in the scanned content.
  3. Strong technical implementation with modern frameworks and good performance.
  4. Security best practices are well implemented but lack published security policies or incident response info.
  5. Business information is consistent with a major technology company (Meta).
  6. Content is safe and targeted at developers and technical audiences.
  7. External links mostly point to trusted domains related to React ecosystem and conferences.
Technical notes

Notes

The website is built on a modern technology stack including React and Next.js, leveraging server-side rendering and static generation for performance. It uses Algolia for search functionality and Google Tag Manager for analytics. The site is well-optimized for mobile devices and accessibility, with proper meta tags and SEO practices. The code samples and interactive components demonstrate advanced React usage, indicating a high level of technical maturity. Hosting appears to be on Meta's infrastructure or a trusted cloud provider, ensuring reliability and scalability. No technical debt or deprecated technologies were observed in the provided content.
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. 62/100Medium35 findingsView report
Reviews of this site

Share your experience with react.dev. 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 react.dev.

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.