Skip to main content

Security report for clerk.com

Clerk · Technology · N/a

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

Security score

76/100

Risk levelLow

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

Clerk is a technology company specializing in providing authentication and user management solutions tailored for modern web applications built with React, Next.js, and Remix. Their platform offers a comprehensive suite of UI components and APIs that enable developers to implement sign-in, sign-up, user profile management, organization management, and billing functionalities quickly and efficiently. Positioned as a developer-friendly SaaS solution, Clerk targets businesses and developers seeking to streamline user authentication and management processes. Technically, Clerk's website demonstrates a mature digital infrastructure leveraging modern JavaScript frameworks such as React and Next.js. The site is well-optimized for performance and mobile responsiveness, with a clean, professional design that enhances user experience. The use of a dedicated JavaScript SDK and integration with analytics tools indicates a focus on developer usability and data-driven insights. From a security perspective, Clerk employs HTTPS and domain registration protections like clientDeleteProhibited and clientTransferProhibited statuses, which enhance domain security. However, the absence of DNSSEC and security headers represents areas for improvement. The website lacks explicit privacy and cookie policies, which may impact compliance with regulations such as GDPR. No direct contact or incident response information is provided, limiting transparency in security governance. Overall, Clerk presents as a credible and professional service provider with a strong technical foundation and market positioning. To enhance trust and compliance, it is recommended that Clerk publish comprehensive privacy and cookie policies, implement DNSSEC, and adopt standard security headers. These steps will improve their security posture and regulatory compliance, further solidifying their reputation in the authentication services market.

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

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

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

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

Keep watching clerk.com

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. 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
72
Security headers
60
Email security
87
DNS health
85
Network security
100
GDPR outside view
53
Average
76

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

Clerk operates in the technology sector, focusing on authentication and user management services for web applications. Their business model is SaaS-based, offering modular UI components and APIs that integrate seamlessly with popular frameworks like React and Next.js. The company targets developers and businesses building modern web apps, emphasizing ease of integration and scalability. Market positioning highlights Clerk as a modern alternative to legacy authentication providers, with a focus on developer experience and comprehensive user management features. The website showcases trust signals such as endorsements from fast-growing companies and professional design, indicating a growing presence in the developer tools ecosystem. Revenue streams likely include subscription plans for different usage tiers, as suggested by the pricing page links. Strategic partnerships or subsidiaries are not evident from the data provided.

Security posture

Clerk's security posture is solid but not exhaustive. The use of HTTPS and domain registration locks (clientDeleteProhibited, clientTransferProhibited) protects against common domain hijacking risks. However, the lack of DNSSEC leaves the domain vulnerable to DNS spoofing attacks. The website does not display common security headers such as Content-Security-Policy or X-Frame-Options, which are recommended to mitigate cross-site scripting and clickjacking attacks. No explicit security policy or incident response contact information is available, which could hinder timely communication in case of security incidents. The presence of a client-side SDK with request headers indicating human verification suggests some level of bot mitigation. Overall, Clerk demonstrates awareness of security best practices but should enhance transparency and technical controls to meet higher compliance standards.

Recommendations

  1. Publish comprehensive privacy and cookie policies with clear GDPR compliance statements.
  2. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  3. Implement standard security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  4. Provide explicit security policy and incident response contact information on the website.
  5. Enhance transparency around data collection, retention, and user consent mechanisms.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Clerk
Description
The easiest way to add authentication and user management to your application. Purpose-built for React, Next.js, Remix, and “The Modern Web”.
Key services
User authentication, User management, Organization management, Billing components
Content quality
excellent
Branding
consistent

Technology

Stack
React, Next.js, Remix, JavaScript, TypeScript, Clerk.js SDK
Frameworks
React, Next.js, Remix
Platforms
Web
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enabled
  • Use of client-side SDK with security headers for requests
  • Domain status includes clientDeleteProhibited, clientTransferProhibited, clientUpdateProhibited

Analytics and tracking

Services
dub analytics
Tracking level
moderate
Privacy practices
poor

Advertising

Tracking pixels
dub analytics
Marketing tools
dub analytics
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. Content is rich and focused on authentication and user management for modern web apps
  3. No explicit privacy, cookie, or terms of service pages found in the provided content
  4. No direct contact emails or phone numbers found in the content
  5. Use of modern JavaScript frameworks and SDKs
  6. Good visual design and user experience
  7. Security best practices partially implemented but could be improved with DNSSEC and security headers
  8. No suspicious or malicious content detected
Technical notes

Notes

The website is built using modern web technologies including React, Next.js, and Remix frameworks, supported by a JavaScript SDK (Clerk.js) for authentication features. The site is well-structured with appropriate meta tags for SEO and social media sharing (Open Graph and Twitter cards). Performance appears optimized with preloading of fonts and images, and responsive design for mobile devices. Hosting details are not explicit but DNS and registrar information indicate stable domain management. No CMS is detected, suggesting a custom or framework-based site. Analytics usage includes a third-party service (dub analytics) for tracking user interactions. Technical risks include missing DNSSEC and lack of security headers, which could be addressed to reduce attack surface and improve compliance. Overall, the technical implementation supports a fast, accessible, and developer-centric user experience.
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 clerk.com. 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 clerk.com.

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.