Skip to main content

Security report for predibase.com

Predibase · Technology · N/a

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

Security score

74/100

Risk levelMedium

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

Predibase is a technology company founded in 2020 that offers a developer-focused platform for fine-tuning and serving large language models (LLMs). Their platform enables customization and deployment of open-source models that claim to outperform GPT-4, targeting developers and enterprises seeking advanced AI capabilities. The website is built using modern web technologies including React, Gatsby, and Tailwind CSS, hosted with a reputable registrar and DNS provider. The site demonstrates good design quality, mobile optimization, and SEO practices, though it lacks explicit privacy, cookie, and security policies. Security posture is moderate with HTTPS enabled and domain protections in place, but missing DNSSEC and security headers. Overall, the website is professional and functional but could improve transparency and compliance documentation.

Scanned

NIS2 and GDPR posture

GDPR outside view
73/ 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

  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
    • 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 predibase.com

This scan found 20 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
52
Security headers
65
Email security
75
DNS health
80
Network security
100
GDPR outside view
73
Average
74

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

Predibase positions itself as a niche platform in the AI/ML space, focusing on LLM fine-tuning and serving. The business model is platform-as-a-service targeting developers and enterprises. The company appears to be a small-sized startup with no public parent or subsidiaries. The website content is consistent and well-branded, targeting a technical audience. The lack of explicit contact information and compliance policies suggests an early-stage or stealth approach. The company leverages HubSpot for marketing and lead capture, indicating a structured approach to customer engagement.

Security posture

The website uses HTTPS with a valid SSL certificate and domain status protections to prevent unauthorized changes. However, DNSSEC is not enabled, and no security headers were detected in the provided data. There is no published security policy, incident response information, or vulnerability disclosure program. Forms are present but no explicit security measures or data protection statements are visible. The absence of privacy and cookie policies indicates compliance gaps, especially regarding GDPR. Overall, the security posture is moderate but could be significantly improved with better transparency and technical controls.

Recommendations

  1. Enable DNSSEC to enhance DNS security and prevent spoofing
  2. Implement and publish comprehensive privacy and cookie policies with consent mechanisms
  3. Add security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security
  4. Publish a security policy and incident response contact information to improve trust and compliance
  5. Include clear contact information for business and security inquiries to enhance credibility
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Predibase
Description
Customize and serve open-source models for your use case that outperform GPT-4—all within your cloud or ours.
Key services
Fine-tuning open-source large language models, Serving LLMs on cloud or on-premises, Developer tools for AI model customization
Content quality
good
Branding
consistent

Technology

Stack
React, Gatsby, Tailwind CSS
Frameworks
React, Gatsby
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enabled
  • Domain status includes clientDeleteProhibited and clientTransferProhibited

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Marketing tools
HubSpot (form handling)
Transparency
basic

Site quality

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

Key observations

  1. Website is accessible with no blocking or WAF challenge
  2. No explicit privacy, cookie, or terms of service policies found on main page
  3. Contact information such as emails or phone numbers not found in visible content
  4. Uses modern web technologies and frameworks
  5. No explicit security or incident response information published
  6. WHOIS data shows domain is relatively new but consistent with business profile
  7. No suspicious external domains or links detected
Technical notes

Notes

The website is built on a modern React/Gatsby stack with Tailwind CSS for styling, indicating a contemporary and maintainable codebase. Hosting and DNS are managed via reputable providers. Performance is moderate with good mobile responsiveness and SEO metadata present. Accessibility is basic but could be improved. No CMS detected, suggesting a custom or static site generation approach. The use of HubSpot forms indicates integration with marketing automation tools. Technical risks include missing DNSSEC and security headers, which could expose the site to certain attacks. Overall, the technical infrastructure is solid but has room for security and compliance enhancements.
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 predibase.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 predibase.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.