Skip to main content

Security report for buildernet.org

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

BuilderNet is a newly launched decentralized block building network for Ethereum, leveraging Trusted Execution Environments (TEEs) and sharing Miner Extractable Value (MEV) with the community. The website serves as a documentation and community portal, targeting Ethereum developers and blockchain enthusiasts. It provides technical resources, API references, and a forum link to engage the community. The business model focuses on decentralized infrastructure services within the blockchain technology sector, positioning itself as a niche player in the Ethereum ecosystem. Technically, the website is built using modern web technologies including Docusaurus, React, and KaTeX for math rendering. It is hosted via Cloudflare and uses CDN services for performance optimization. The site demonstrates good SEO, accessibility, and mobile optimization practices, though performance is moderate. Analytics are implemented via Vercel Analytics and Algolia DocSearch, with minimal user tracking. From a security perspective, the site uses HTTPS and has domain transfer protections enabled. However, DNSSEC is not enabled and no explicit security headers were detected in the provided data. There is no published privacy policy, cookie policy, or terms of service, which impacts privacy compliance. No contact or incident response information is available, limiting transparency and user trust. The domain registration data is consistent with the website content and business focus, indicating legitimacy. Overall, BuilderNet's website is professionally designed and technically sound but lacks critical privacy and security policy disclosures. Strategic improvements in security headers, privacy compliance, and contact transparency would enhance trust and compliance posture.

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 buildernet.org

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. 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
30
Email security
70
DNS health
70
Network security
100
GDPR outside view
50
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

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 buildernet.org, from OffSeq Breach.

No leaked records found

Breach holds no records for buildernet.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

BuilderNet operates in the blockchain technology sector, specifically focusing on Ethereum block building and MEV sharing. The business targets developers and blockchain participants interested in decentralized infrastructure. Its competitive advantage lies in leveraging TEEs for secure block building and community MEV distribution. The business model appears to be service-oriented, providing APIs and network services. The website content and domain registration indicate a startup phase with a small organizational size. The presence of a community forum and detailed documentation suggests an emphasis on developer engagement and ecosystem growth. No parent or subsidiary companies are identified. The company uses Cloudflare for domain registration and hosting, indicating a preference for reliable infrastructure providers.

Security posture

The website demonstrates a moderate security maturity level. HTTPS is enabled, and domain transfer protections are active, which are positive indicators. However, the absence of DNSSEC and security headers such as Content-Security-Policy or X-Frame-Options reduces the overall security posture. No vulnerabilities or exposed sensitive data were detected in the content. The lack of published security policies, incident response contacts, or vulnerability disclosure mechanisms indicates gaps in compliance and readiness. Privacy compliance is weak due to missing privacy and cookie policies. The site does not collect user data via forms on the main page, reducing attack surface but also limiting user engagement options. Overall, the security posture is functional but requires enhancements to meet best practices and regulatory expectations.

Recommendations

  1. Enable DNSSEC on the domain to protect against DNS spoofing and improve DNS security.
  2. Implement standard security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to mitigate common web vulnerabilities.
  3. Publish comprehensive privacy and cookie policies to improve GDPR compliance and user trust.
  4. Add clear contact information including security incident response contacts to enhance transparency and readiness.
  5. Regularly audit and update third-party libraries and analytics tools to avoid vulnerabilities and ensure privacy compliance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
BuilderNet is a decentralized block building network for Ethereum that runs on TEEs and shares MEV with the community.
Key services
Decentralized block building for Ethereum, Orderflow sending, API services, Documentation and community forum
Content quality
good
Branding
consistent

Technology

Stack
JavaScript, React, Docusaurus, KaTeX
Frameworks
Docusaurus v3.6.1
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
60/100
Good practices seen
  • HTTPS enabled (implied by canonical URL https://buildernet.org/)
  • Domain status clientTransferProhibited

Analytics and tracking

Services
Vercel Analytics
Tracking level
minimal
Privacy practices
poor

Advertising

Tracking pixels
Vercel Analytics
Marketing tools
Algolia DocSearch
Transparency
basic

Site quality

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

Key observations

  1. Website is a technical documentation and community hub for a new Ethereum decentralized block building network.
  2. No privacy, cookie, or terms of service policies found on the site.
  3. No contact emails, phone numbers, or physical addresses provided on the homepage or main content.
  4. Site uses modern static site generator Docusaurus with good SEO and accessibility practices.
  5. No explicit security policies or incident response information published.
  6. No forms detected on the main page; no user data collection visible.
  7. External links mainly to community forum and trusted CDN/analytics providers.
  8. No advertising or affiliate marketing detected beyond basic analytics and search tools.
Technical notes

Notes

The website is built on a modern static site generator (Docusaurus v3.6.1) using React and JavaScript, with KaTeX for mathematical content rendering. Hosting is provided via Cloudflare, ensuring reliable CDN and DNS services. The site uses Algolia DocSearch for search functionality and Vercel Analytics for traffic monitoring. Performance is moderate with prefetching of JavaScript assets to improve load times. The site is mobile optimized and accessible with semantic HTML and ARIA roles. No CMS beyond Docusaurus is detected. There is no evidence of technical debt or deprecated technologies. Opportunities exist to enhance security configurations and privacy compliance to reduce technical risks.
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 buildernet.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 buildernet.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.