Skip to main content

Security report for ithaca.xyz

Ithaca · Technology · N/a

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

Security score

69/100

Risk levelMedium

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

Ithaca is a technology startup focused on advancing the crypto frontier by building web3 infrastructure from first principles. Their flagship offering is Porto, an open source TypeScript library that enables passwordless accounts and seamless authentication for crypto applications. The company targets developers building web3 and blockchain applications, positioning itself as an innovator in account abstraction and crypto payment solutions. The website reflects a professional and modern digital presence with clear developer-oriented content and integration with popular web3 libraries like Wagmi and Viem. Technically, the site is built on a modern React and Next.js stack, hosted on Vercel with Cloudflare DNS. It demonstrates good performance, mobile optimization, and SEO practices. The use of Vercel Analytics indicates minimal user tracking. However, the site lacks explicit privacy and cookie policies, which is a gap in compliance and user transparency. No security policy or incident response information is published, which could be improved to enhance trust. From a security perspective, the site uses HTTPS and does not expose sensitive data. The domain registration is consistent with the business claims, with a domain age appropriate for a startup founded in 2022. DNSSEC is not enabled, and security headers are not explicitly detected, suggesting room for improvement in hardening. No vulnerabilities or suspicious patterns were found in the content or WHOIS data. Overall, Ithaca presents a credible and professional web3 infrastructure business with a strong technical foundation but would benefit from enhanced privacy, security policies, and compliance documentation to improve trust and regulatory adherence.

Scanned

NIS2 and GDPR posture

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

6 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 Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • 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

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

Keep watching ithaca.xyz

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. 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
72
Security headers
30
Email security
85
DNS health
75
Network security
100
GDPR outside view
50
Average
69

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

Ithaca operates in the niche market of web3 infrastructure, focusing on developer tools that simplify crypto onboarding and payments. Their competitive advantage lies in their open source Porto library, which integrates with widely used web3 frontend libraries without requiring code changes. The business model centers on providing foundational technology for crypto applications, likely monetizing through developer services or enterprise integrations. The target customers are crypto developers and startups seeking scalable account abstraction solutions. Growth indicators include active GitHub repositories, developer community engagement via Telegram, and ongoing hiring efforts. Partnerships with Wagmi and Viem projects strengthen their ecosystem position. The company appears to be a small but focused startup with a clear technical vision and market niche.

Security posture

The website demonstrates a moderate security maturity level with HTTPS enforced and no visible sensitive data leaks. However, the absence of DNSSEC, security headers, and published security policies indicates gaps in defense-in-depth. No incident response or vulnerability disclosure mechanisms are publicly available, which limits transparency and readiness for security events. The use of modern authentication methods like WebAuthn and OAuth in their product is a positive security indicator. Compliance with GDPR and other privacy regulations is not clearly addressed on the site, representing a compliance gap. Overall, the security posture is adequate for a startup but requires enhancements in policy publication, DNS security, and header configurations to meet higher standards.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Publish comprehensive privacy and cookie policies to enhance GDPR compliance and user trust.
  3. Implement security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  4. Create and publish a security policy and incident response contact information to improve transparency and readiness.
  5. Consider adding a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Ithaca
Description
Building web3 infrastructure from 1st principles. Home of porto.sh. By the teams behind Reth, Foundry, Wagmi & Viem.
Key services
Porto TypeScript library for passwordless accounts, Account abstraction stack for crypto payments, Developer tools integration with Wagmi and Viem
Content quality
good
Branding
consistent

Technology

Stack
React, Next.js, TypeScript, Vercel Analytics, Cloudflare DNS
Frameworks
Next.js
Platforms
Vercel
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Use of modern authentication concepts (WebAuthn, OAuth)

Analytics and tracking

Services
Vercel Analytics
Tracking level
minimal
Privacy practices
poor

Advertising

Tracking pixels
Vercel Analytics
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. No privacy, cookie, or terms of service policies found on the site.
  3. Contact information is limited to an email and subscription form; no phone or physical address found.
  4. Strong focus on developer tools and crypto infrastructure.
  5. Modern tech stack and hosting platform used.
  6. No security policy or incident response information published.
  7. No vulnerability disclosure or security.txt found.
  8. No explicit or adult content detected.
  9. Good SEO and social media integration present.
  10. WHOIS data supports legitimacy and domain age matches business claims.
Technical notes

Notes

The website is built using a modern React and Next.js framework, leveraging TypeScript and hosted on Vercel, ensuring fast performance and scalability. The use of Cloudflare DNS provides reliable DNS resolution, though DNSSEC is not enabled. The site is mobile-optimized with responsive design and good accessibility features. SEO is well addressed with proper meta tags and Open Graph data. Analytics are minimal and privacy-conscious via Vercel Analytics. No CMS is detected, indicating a custom or static site approach. The technical stack is modern and well-suited for a developer-focused technology startup, with opportunities to improve security configurations and compliance documentation.
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 ithaca.xyz. 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 ithaca.xyz.

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.