Skip to main content

Security report for neon.tech

Neon, Inc. · Technology · United States

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

Security score

68/100

Risk levelMedium

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

Neon, Inc. operates a modern serverless Postgres database platform designed to accelerate application development by providing scalable, reliable, and developer-friendly database services. Positioned as a trusted technology provider, Neon targets developers and technology teams seeking cloud-native database solutions with features like autoscaling, branching, and instant provisioning. The company enjoys a strong market position supported by industry certifications and a growing user base. Technically, the website demonstrates a mature digital infrastructure leveraging Next.js and React frameworks, optimized for performance and mobile responsiveness. The platform integrates with popular developer tools and languages, showcasing a modern tech stack and cloud hosting likely on AWS. The site is well-structured with comprehensive documentation and community engagement channels. From a security perspective, Neon exhibits a robust posture with HTTPS enforcement, multiple security headers, and compliance with major standards including ISO 27001, SOC 2, GDPR, and HIPAA. While no critical vulnerabilities or exposed sensitive data were detected, the absence of explicit incident response contacts and vulnerability disclosure policies suggests areas for improvement. Overall, Neon presents a low-risk profile with high trustworthiness and professionalism. Strategic recommendations include enhancing privacy compliance with cookie consent mechanisms, publishing incident response and vulnerability disclosure information, and maintaining transparency to further strengthen security culture and customer confidence.

Scanned

NIS2 and GDPR posture

GDPR outside view
80/ 100 · Low
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 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
  4. DNS health

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

    • High

      Unregistered MX Record

      MX record points to unregistered domain: aspmx.2.google.com

      What to do: Remove or fix MX record pointing to unregistered domain

      • RFC 5321 §5.1
      • NIS2 21(2)(i)
      • IR 2024/2690 12.4: Implementing Regulation (EU) 2024/2690, Annex point 12.4: Asset inventory
      • NIST CM-8: NIST SP 800-53 Rev. 5 CM-8: System Component Inventory

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

Keep watching neon.tech

This scan found 24 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
30
Email security
70
DNS health
55
Network security
100
GDPR outside view
80
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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention neon.tech, from OffSeq Breach.

Total records
715
Employees
0
Customers
715
Third parties
0
Weak passwords
10%

5 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for neon.tech.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Technical appendix

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

Business context

Business profile

Neon operates in the cloud database technology sector, focusing on serverless Postgres solutions that cater to developers and enterprises requiring scalable and cost-efficient database services. Their business model revolves around cloud-based subscriptions and usage-based pricing, targeting startups, enterprises, and platform providers. The company leverages partnerships and community engagement through GitHub and Discord, enhancing its ecosystem. Growth indicators include a strong social media presence, multiple compliance certifications, and endorsements from industry leaders. Neon’s competitive advantage lies in its modern workflows like branching and autoscaling, positioning it well against traditional database providers.

Security posture

Neon demonstrates a mature security posture with adherence to industry best practices and certifications such as ISO 27001, SOC 2, and HIPAA compliance. The website enforces HTTPS, employs security headers, and avoids exposing sensitive information. However, the lack of publicly available incident response contacts and vulnerability disclosure policies indicates a gap in transparency and readiness communication. Data protection practices align with GDPR and CCPA requirements, but cookie consent mechanisms are not evident. Overall, Neon’s security culture appears strong but could benefit from enhanced incident response visibility and formal vulnerability disclosure processes.

Recommendations

  1. Publish explicit incident response contact information on the website to improve transparency and readiness.
  2. Implement a cookie consent banner or mechanism to ensure full GDPR compliance and user privacy control.
  3. Develop and publish a vulnerability disclosure policy or security.txt file to encourage responsible reporting and improve security posture.
  4. Regularly review and update privacy policies and compliance documentation to reflect evolving regulations and best practices.
  5. Enhance user education on security features and compliance certifications to build greater trust and security culture.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Neon, Inc.
Description
The database you love, on a serverless platform designed to help you build reliable and scalable applications faster.
Key services
Serverless Postgres database, Autoscaling, Connection pooling, Bottomless storage, Branching, Instant restores, API and CLI for database management
Content quality
excellent
Branding
consistent

Technology

Stack
React, Next.js, JavaScript, PostgreSQL, Serverless architecture
Frameworks
Next.js
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
90/100
Good practices seen
  • HTTPS enforced
  • Security headers present
  • No exposed credentials in HTML
  • Use of serverless driver with secure connection strings

Analytics and tracking

Tracking level
minimal
Privacy practices
good

Advertising

Tracking pixels
neonapi.io
Marketing tools
Discord, GitHub, Twitter, LinkedIn, YouTube
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 rich content and professional design.
  2. Strong focus on serverless Postgres technology and modern developer workflows.
  3. Multiple compliance certifications and trust indicators are prominently displayed.
  4. Active community engagement via Discord, GitHub, and social media.
  5. No signs of suspicious or malicious content.
  6. No exposed sensitive data or security vulnerabilities detected in the HTML content.
Technical notes

Notes

The website is built using modern web technologies including React and Next.js, ensuring server-side rendering and optimized performance. The tech stack supports fast loading times, mobile responsiveness, and accessibility standards. Hosting appears to be on a major cloud provider, likely AWS, supporting scalability and reliability. The site integrates with developer tools and languages such as Python, Ruby, Go, and JavaScript frameworks, indicating a versatile platform. Technical risks are minimal with no visible outdated libraries or exposed credentials. Opportunities exist to further modernize privacy compliance and incident response capabilities.
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 neon.tech. 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 neon.tech.

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.