Skip to main content

Security report for obol.org

Obol Collective · Technology · United States

Low risk. 4 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

77/100

Risk levelLow

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

Obol Collective is a technology-focused group dedicated to strengthening and sustaining Ethereum's consensus layer through tools, teams, and community collaboration. The website presents a professional and consistent brand image with a focus on Ethereum blockchain technology. The technical infrastructure leverages modern web technologies including Framer for design and Cloudflare for DNS hosting, with Google Analytics integrated for visitor tracking. Security posture is adequate with HTTPS enabled and domain protections in place, though improvements are needed in security headers and explicit security policies. Privacy compliance is lacking as no privacy or cookie policies are present, and no consent mechanisms are implemented. Overall, the website is functional and trustworthy but would benefit from enhanced privacy and security disclosures.

Scanned

NIS2 and GDPR posture

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

  2. 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

  3. 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: vmpifqj7fsalsufqfszzk7daeyscqqh5hyvq63ldxti43bnlz7eq.mx-verification.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 obol.org

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
80
Email security
85
DNS health
70
Network security
100
GDPR outside view
53
Average
77

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 Obol Collective operates in the niche Ethereum blockchain technology sector, targeting developers and consensus layer stakeholders. Its business model centers on open-source tools and community-driven initiatives to support Ethereum's consensus sustainability. The domain age and privacy protection align with a mature technology project. The absence of direct contact information and formal policies suggests a community or decentralized organization rather than a traditional commercial enterprise. The website's market position is specialized, serving a technical audience with a focus on blockchain consensus mechanisms.

Security posture

The website employs HTTPS with a valid SSL configuration and uses Cloudflare DNS with domain status protections such as clientDeleteProhibited. However, it lacks key security headers like Content-Security-Policy and Strict-Transport-Security, which could enhance protection against common web attacks. No vulnerability disclosure or incident response information is provided, limiting transparency for security issues. The use of Google Analytics without visible cookie consent raises privacy compliance concerns. Overall, the security maturity is moderate but could be improved by adopting best practices and publishing security policies.

Recommendations

  1. Enable DNSSEC to strengthen DNS security and prevent spoofing.
  2. Implement and publish comprehensive privacy and cookie policies with GDPR compliance details.
  3. Add security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  4. Provide clear contact information including security incident response contacts.
  5. Publish a vulnerability disclosure policy or security.txt file to facilitate responsible reporting.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Obol Collective
Description
A group of tools, teams, and communities dedicated to strengthening and sustaining Ethereum’s consensus layer.
Key services
Tools for Ethereum consensus layer, Community collaboration, Sustainability initiatives
Content quality
good
Branding
consistent

Technology

Stack
Framer, Google Analytics, Cloudflare DNS
Frameworks
Framer
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

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

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
poor

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Website uses Framer for design and hosting with Cloudflare DNS.
  2. No explicit privacy, cookie, or terms of service policies found on the homepage.
  3. No contact emails, phone numbers, or physical addresses found in the HTML content.
  4. Google Analytics is used for visitor tracking without visible cookie consent mechanism.
  5. No security.txt or vulnerability disclosure policy found.
  6. Domain WHOIS is privacy protected but domain age and status indicate legitimacy.
  7. No WAF or blocking mechanisms detected; content fully accessible.
  8. Content is technical and community focused on Ethereum consensus layer.
Technical notes

Notes

The website is built using Framer, a modern design and prototyping platform, and hosted with Cloudflare DNS services. It uses Google Analytics for visitor tracking. The site demonstrates good mobile optimization and SEO practices with proper meta tags and Open Graph data. Performance is moderate, with no critical errors detected. However, the absence of accessibility features and security headers indicates areas for technical improvement. The domain's long history and DNS protections contribute positively to the technical risk profile.
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 obol.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 obol.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.