Skip to main content

Security report for lead.dev

lead.dev · Technology · N/a

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

Security score

67/100

Risk levelMedium

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

lead.dev is a technology platform designed to help startups share their verified monthly recurring revenue (MRR) with the world, compete on leaderboards, and gain feedback to grow their businesses. The platform targets startup founders, developers, and SaaS entrepreneurs, positioning itself as a niche community hub for startup growth and visibility. The website is well-designed with a modern tech stack based on Next.js and React, offering a fast and mobile-optimized user experience. Security posture is solid with HTTPS enforced and no exposed sensitive data, though there is room for improvement in security headers and formal security policies. Privacy compliance is basic with privacy and terms pages present but no cookie consent mechanism or GDPR-specific indicators. Overall, the site is trustworthy and professional, with good business credibility and technical implementation.

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

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

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

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

Keep watching lead.dev

This scan found 22 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
75
Security headers
35
Email security
55
DNS health
85
Network security
100
GDPR outside view
53
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

Technical appendix

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

Business context

Business profile

lead.dev operates a platform that facilitates startup growth by enabling founders to claim profiles, share revenue data, and compete on MRR leaderboards. Its business model revolves around community engagement and visibility rather than direct monetization visible on the site. The platform leverages testimonials and founder profiles to build trust and attract users. The ecosystem includes numerous linked startup domains, indicating a broad network of early-stage companies. The company appears small but focused on the technology sector, with no parent or subsidiary companies identified. The lack of explicit contact information suggests a lean operation or reliance on digital engagement channels.

Security posture

The website demonstrates a moderate to good security maturity level. HTTPS is properly configured, and scripts are loaded asynchronously to optimize performance and security. However, the absence of key security headers such as Content-Security-Policy and X-Frame-Options is a notable gap. There is no visible vulnerability disclosure policy or security.txt file, which could improve incident response readiness. No sensitive data or credentials are exposed in the HTML content. Privacy compliance is basic, with no cookie consent mechanism detected. Overall, the security posture is adequate for the business type but could be enhanced with additional best practices and formal policies.

Recommendations

  1. Implement comprehensive security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to enhance protection against common web attacks.
  2. Add a vulnerability disclosure policy or security.txt file to facilitate responsible reporting and improve incident response.
  3. Introduce a cookie consent mechanism and update privacy policy to explicitly address GDPR compliance and user data rights.
  4. Provide clear and accessible contact information for business and security inquiries to improve trust and communication.
  5. Regularly audit third-party scripts and tracking tools to minimize privacy risks and optimize performance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
lead.dev
Description
Share your startup with the world. Compete on the MRR leaderboard, get feedback, find users, and grow your startup.
Key services
Startup profile creation, MRR leaderboard competition, User feedback and growth facilitation
Content quality
good
Branding
consistent

Technology

Stack
Next.js, React, JavaScript, CSS, Web Vitals, Polyfills
Frameworks
Next.js, React
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Async loading of scripts

Analytics and tracking

Services
web-vitals
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
web-vitals.js, dead-clicks-autocapture.js, recorder.js
Marketing tools
web-vitals, dead-clicks-autocapture
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Clear privacy policy and terms of service pages are present.
  3. No explicit contact emails or phone numbers found on the site.
  4. Modern web technologies and frameworks are used.
  5. Good mobile optimization and user experience.
  6. No security headers detected; opportunity for improvement.
  7. No vulnerability disclosure or security policy pages found.
  8. Content is safe and appropriate for general audiences.
  9. Multiple external links to startup products and related domains.
Technical notes

Notes

The website is built on a modern and robust technology stack featuring Next.js and React, ensuring fast loading times and excellent mobile responsiveness. The use of web-vitals and dead-clicks autocapture scripts indicates attention to performance monitoring and user interaction analytics. The site employs asynchronous script loading and font preloading for optimized rendering. No CMS is detected, suggesting a custom or static site generation approach. Hosting provider details are not explicit but the site uses HTTPS with a valid SSL certificate. The technical implementation is solid with good SEO and accessibility features, though security headers and formal policies are areas for improvement.
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/100Medium31 findingsView report
Reviews of this site

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