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 startup founders and developers share their startups with the world, compete on a Monthly Recurring Revenue (MRR) leaderboard, and gain feedback and users to grow their businesses. The platform targets the developer and SaaS startup community, offering profile creation and leaderboard competition as key services. The website is professionally designed with a modern React and Next.js tech stack, optimized for mobile and fast performance. Security posture is strong with HTTPS and security headers implemented, though privacy compliance could be improved by adding cookie consent mechanisms and explicit contact information. Overall, lead.dev presents a trustworthy and niche platform with good market positioning in the startup ecosystem.

Scanned

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

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 in the technology sector, focusing on SaaS startups and developer communities. Its business model revolves around providing a public leaderboard and profile system for startups to showcase verified revenue and compete for visibility. The platform fosters community engagement through feedback and user acquisition features. The presence of testimonials and verified revenue sharing enhances trust and credibility. The external links to various startup product domains suggest an active ecosystem and partnership network. The company appears to be a small-sized entity with a focused niche market, aiming to grow through community-driven growth and exposure.

Security posture

The website demonstrates a mature security posture with enforced HTTPS, presence of key security headers such as Strict-Transport-Security, X-Content-Type-Options, and Content-Security-Policy, and no visible exposure of sensitive data. However, there is no publicly available security policy or incident response contact information, which could be a gap in transparency and readiness. The lack of a vulnerability disclosure policy or security.txt file also limits formal communication channels for security issues. Privacy compliance is partial, with a privacy policy present but no cookie consent mechanism detected. Overall, the security posture is good but could be enhanced by formalizing policies and improving privacy compliance.

Recommendations

  1. Implement a cookie consent banner to comply with GDPR and other privacy regulations.
  2. Publish a dedicated security policy and incident response contact information on the website.
  3. Add a vulnerability disclosure policy or security.txt file to facilitate responsible reporting.
  4. Include clear and verified contact information such as company email and phone number for trust and compliance.
  5. Regularly review and update privacy and security practices to maintain compliance and user trust.
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
React, Next.js, JavaScript, CSS
Frameworks
Next.js
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Security headers present
  • No exposed sensitive data in HTML

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
excellent
User experience
excellent
Content relevance
good
Navigation
good
Professionalism
excellent
Trustworthiness
high

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Professional and modern design with clear startup-focused content.
  3. No explicit contact emails or phone numbers found on the public pages.
  4. Privacy policy and terms of service pages are present but cookie policy and consent mechanism are missing.
  5. Security headers and HTTPS are properly implemented.
  6. Multiple external domains linked, mostly startup product domains.
  7. No signs of suspicious or malicious content.
  8. Moderate use of tracking scripts for analytics and user interaction.
Technical notes

Notes

The website is built using modern web technologies including React and Next.js, ensuring server-side rendering and good SEO performance. The use of asynchronous JavaScript loading and optimized CSS contributes to fast page load times. The site is mobile-optimized with responsive design and accessibility features. No CMS is detected, indicating a custom or framework-based implementation. Tracking scripts for web vitals and user interaction are present, supporting analytics and performance monitoring. Hosting provider details are not explicitly identified. Overall, the technical infrastructure is robust and modern, supporting a high-quality user experience with minimal technical debt.
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.