Skip to main content

Security report for mpc.org

MPC Foundation · Technology · United States

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

Security score

66/100

Risk levelMedium

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

The MPC Foundation website presents a small, specialized non-profit organization focused on advancing modern cryptography and the multiparty computation (MPC) ecosystem. The site highlights participation in relevant industry events such as Encrypt and SecureFi, targeting cryptography professionals and ecosystem participants. The business model centers on ecosystem advancement and community engagement rather than commercial services. Technically, the site is built on Webflow with modern web fonts, Google Analytics (with IP anonymization), and Plausible Analytics for privacy-conscious tracking. Hosting and DNS are managed via Cloudflare and Webflow, ensuring good performance and HTTPS security. However, the site lacks critical privacy and cookie policies, security headers, and contact information, which impacts compliance and trust. The domain is long-established since 1997, with privacy protection typical for tech foundations, and domain locking enabled to prevent unauthorized changes. Overall, the site is professional but basic in content and security posture, with room for improvement in privacy compliance and security best practices.

Scanned

NIS2 and GDPR posture

GDPR outside view
35/ 100 · High
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 Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1

  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

    • High

      Third-party services without privacy policy

      Detected services: Google Analytics, Google APIs

      What to do: Document all third-party data sharing in your privacy policy

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

Keep watching mpc.org

This scan found 23 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
45
Email security
70
DNS health
75
Network security
100
GDPR outside view
35
Average
66

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

The MPC Foundation occupies a niche position in the cryptography and MPC technology sector, focusing on ecosystem development and event participation. Its business model is non-commercial, likely funded by grants or donations, targeting researchers and professionals in cryptography. The foundation leverages partnerships with event platforms like Encrypt and SecureFi to increase visibility. The lack of detailed business contact information and policies suggests a lean organizational structure. The domain age and locking status support legitimacy, while privacy protection is justified given the nature of the organization. The foundation's digital presence is modest but consistent with a specialized technology non-profit.

Security posture

The website enforces HTTPS and uses IP anonymization in analytics, reflecting basic security awareness. However, the absence of DNSSEC, security headers (such as CSP, HSTS, X-Frame-Options), and published security or incident response policies indicates gaps in security maturity. No forms or input fields reduce attack surface but also limit user engagement. The domain's locked status and long age are positive trust signals. Overall, the security posture is moderate but could be significantly improved by implementing recommended headers, policies, and transparency measures.

Recommendations

  1. Enable DNSSEC to improve domain name system security.
  2. Publish comprehensive privacy and cookie policies with GDPR compliance details.
  3. Implement a cookie consent mechanism to comply with privacy regulations.
  4. Add security headers including Content Security Policy, HSTS, X-Frame-Options, and X-Content-Type-Options.
  5. Provide clear contact information and incident response contacts to enhance trust and compliance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
MPC Foundation
Description
Advancing modern cryptography and the MPC ecosystem.
Key services
Advancing modern cryptography, Supporting MPC ecosystem, Event participation (Encrypt, SecureFi)
Content quality
basic
Branding
consistent

Technology

Stack
Webflow, Google Fonts, Google Analytics (gtag.js), Plausible Analytics, jQuery 3.5.1, Cloudflare DNS
Frameworks
Webflow
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
70/100
Good practices seen
  • HTTPS enabled
  • IP anonymization in Google Analytics

Analytics and tracking

Services
Google Analytics, Plausible Analytics
Tracking level
minimal
Privacy practices
poor

Advertising

Tracking pixels
Plausible Analytics
Transparency
basic

Site quality

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

Key observations

  1. Website is a small technology foundation focused on cryptography and MPC.
  2. No privacy, cookie, or terms of service policies found.
  3. No contact emails, phone numbers, or physical addresses provided on the site.
  4. Uses modern web technologies and analytics with IP anonymization.
  5. No security headers detected; DNSSEC not enabled.
  6. Domain is privacy protected but long-established and locked.
  7. No signs of adult or questionable content.
  8. External links to partner event sites encrypt.xyz and securefi.io.
  9. No forms or data collection fields detected on the homepage.
Technical notes

Notes

The website uses a modern tech stack centered on Webflow CMS, Google Fonts, and analytics tools including Google Analytics and Plausible. Hosting and DNS are managed by Cloudflare and Webflow, providing reliable infrastructure and HTTPS support. Performance is moderate with good mobile optimization and basic accessibility features. SEO is supported by proper meta tags and Open Graph data. The site lacks advanced technical security configurations such as DNSSEC and security headers, which are recommended to reduce risk. No forms or interactive elements reduce complexity but also limit data collection capabilities. Overall, the technical implementation is solid but could benefit from enhanced security and privacy features.
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 mpc.org. 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 mpc.org.

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.