Skip to main content

Security report for privy.io

Technology · N/a

Medium risk. 5 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

Privy.io is a technology-focused website offering wallet infrastructure solutions designed for scalability, targeting businesses and developers who need to securely onboard, activate, and manage users at scale. The website is built using modern design tools such as Framer, indicating a contemporary digital presence. However, the site lacks visible contact information, privacy policies, and security disclosures, which are important for trust and compliance. The WHOIS data is unavailable or privacy protected, which is common for tech startups but reduces transparency. The technical infrastructure appears basic with moderate performance and limited SEO and accessibility features. Security posture is weak due to missing security headers and lack of explicit security best practices. Overall, the site is functional but requires improvements in security, privacy compliance, and business transparency to enhance trustworthiness and compliance.

Scanned

This is an earlier scan of privy.io. View the latest report

NIS2 and GDPR posture

GDPR outside view
58/ 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 privy.io

This scan found 18 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
40
Email security
85
DNS health
85
Network security
100
GDPR outside view
58
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

Privy.io operates in the technology sector, providing wallet infrastructure as a SaaS solution. Its business model likely revolves around B2B services for companies needing scalable user management and onboarding solutions. The lack of detailed business information, contact details, and certifications limits the ability to fully assess market positioning and competitive advantages. The site’s branding is consistent but content quality is basic, suggesting a startup or early-stage company. No partnerships or subsidiaries are identified from the available data. The absence of analytics and marketing tools indicates a low level of digital marketing maturity.

Security posture

The security posture of the website is currently low. There is no evidence of HTTPS enforcement or security headers such as Content-Security-Policy, X-Frame-Options, or X-Content-Type-Options in the provided HTML content. No vulnerability disclosure or incident response information is present. The WHOIS data is privacy protected, which is acceptable but reduces transparency. No contact channels for security incidents or abuse are found. The site does not demonstrate GDPR compliance or cookie consent mechanisms. These gaps present risks in trust and regulatory compliance, and the site should prioritize implementing security best practices and transparency measures.

Recommendations

  1. Implement HTTPS with a strong SSL/TLS configuration and ensure all pages enforce HTTPS.
  2. Add essential security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Publish comprehensive privacy and cookie policies with clear GDPR compliance statements.
  4. Provide clear contact information including support and security incident response contacts.
  5. Establish a vulnerability disclosure policy or security.txt file to enhance security transparency.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Securely onboard, activate, and manage your users at scale.
Key services
wallet infrastructure, user onboarding, user activation, user management at scale
Content quality
basic
Branding
consistent

Technology

Stack
Framer
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. WHOIS data unavailable due to malformed response, indicating privacy protection or query issue
  2. Website built with Framer, indicating modern design tool usage
  3. No visible contact emails, phone numbers, or physical addresses on main page
  4. No privacy, cookie, or terms of service policies detected in provided HTML
  5. No security headers or explicit security best practices detected
  6. No analytics or tracking scripts detected in provided HTML snippet
  7. Content is technology focused, targeting developers or businesses needing wallet infrastructure
  8. No adult or questionable content detected
  9. No WAF or blocking mechanisms detected
Technical notes

Notes

The website is built using Framer, a modern design and prototyping tool, which suggests a contemporary front-end approach. However, the site lacks advanced technical features such as SEO optimization, accessibility enhancements, and performance optimizations. No CMS or hosting provider information is discernible from the HTML content. The site’s performance is moderate, and mobile optimization is basic. There is no evidence of analytics or tracking scripts, which may limit marketing insights. Technical debt appears low but the absence of security and privacy features indicates areas for modernization and risk mitigation.
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. 74/100Medium23 findingsView report
Reviews of this site

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

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.