Skip to main content

Security report for beaverbuild.org

Technology · France

Medium risk. 9 critical or high findings in Email security, Security headers and 2 other checks.

Security score

59/100

Risk levelMedium

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

Beaverbuild.org is a small technology project focused on decentralized block building principles, emphasizing decentralization, uncensorability, and neutrality. The website provides minimal content, including a link to an RPC endpoint and documentation, targeting developers or users interested in blockchain or decentralized technologies. The domain is registered in France with a reputable registrar, consistent with the website's technical hosting. Technically, the website is a simple static HTML and CSS site with no detected CMS, frameworks, or advanced technologies. It lacks modern SEO optimization, accessibility features, and performance enhancements but is functional and moderately optimized for mobile. No analytics or tracking technologies are present, indicating a privacy-conscious approach. From a security perspective, the site lacks security headers, privacy and cookie policies, and vulnerability disclosure mechanisms. The domain registration is transparent and legitimate, but the site could improve its security posture by enabling DNSSEC, adding HTTPS security headers, and publishing privacy and security policies. Overall, the website presents a low-risk profile with basic technical implementation and limited business information. Strategic improvements in security and compliance documentation would enhance trust and credibility.

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

9 findings rated critical or high. Fix these first.

  1. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

  2. 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
    • 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';…

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

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

Keep watching beaverbuild.org

This scan found 27 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
72
Security headers
15
Email security
60
DNS health
70
Network security
100
GDPR outside view
35
Average
59

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention beaverbuild.org, from OffSeq Breach.

No leaked records found

Breach holds no records for beaverbuild.org right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

The project appears to be a niche decentralized technology initiative with a focus on blockchain or distributed ledger technology. Its market positioning is unclear due to minimal content, but it likely targets developers and blockchain enthusiasts. The business model is not explicit but may be community-driven or open-source. The use of a riseup.net email suggests a privacy-conscious or activist orientation. There are no visible revenue streams, partnerships, or certifications. Growth indicators and strategic partnerships are not evident from the website content.

Security posture

The security maturity level is low to moderate. The absence of security headers and privacy policies indicates gaps in compliance and best practices. No incident response or vulnerability disclosure information is provided. The domain registration is consistent and legitimate, but DNSSEC is not enabled, which is a missed opportunity for enhanced domain security. The site uses HTTPS (implied by the URL), but SSL configuration details are unknown. No exposed sensitive data or vulnerabilities were detected in the content. Overall, the security posture requires improvement to meet industry standards and regulatory compliance.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Implement standard security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Publish comprehensive privacy and cookie policies to comply with GDPR and other privacy regulations.
  4. Add a vulnerability disclosure policy or security.txt file to facilitate responsible reporting.
  5. Enhance website content with clear business information and trust indicators to improve credibility.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
The website promotes a philosophy of block building that is decentralised, uncensorable, and neutral. It references a URL endpoint (https://rpc.beaverbuild.org/) and provides links to documentation and a text file named buildernet.txt. The content is minimal and abstract, focusing on principles rather than detailed business descriptions.
Key services
Decentralized block building, RPC endpoint service, Documentation provision
Content quality
basic
Branding
moderate

Technology

Stack
HTML5, CSS3
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
poor

Security

Observed score
30/100

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
low

Key observations

  1. Website content is minimal and abstract, focusing on decentralization principles.
  2. No privacy, cookie, or terms of service policies found.
  3. Contact information limited to a single email address at riseup.net and social media links.
  4. No forms or data collection mechanisms detected.
  5. No security headers or advanced security configurations detected.
  6. No analytics or tracking technologies detected.
  7. No advertising or marketing tools present.
  8. Website design is simple with basic CSS styling and no JavaScript.
  9. No CMS or frameworks detected; static HTML site.
  10. No explicit business or company information beyond domain WHOIS data.
Technical notes

Notes

The website is built using basic HTML5 and CSS3 without any detected JavaScript frameworks or CMS platforms. Hosting is provided by Gandi SAS, a reputable French registrar and hosting provider. The site has moderate performance and basic mobile optimization but lacks SEO and accessibility features. There is no evidence of technical debt or legacy technologies, but modernization opportunities include adding responsive design improvements, SEO metadata, and accessibility enhancements. The absence of analytics and tracking reduces privacy concerns but also limits marketing insights.
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 beaverbuild.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 beaverbuild.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.