Skip to main content

Security report for filecoin.energy

Energy · United States

Medium risk. 8 critical or high findings in Email security, Security headers and 1 other check.

Security score

63/100

Risk levelMedium

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

Filecoin.energy operates a specialized data dashboard titled 'Filecoin Green Dashboard' that focuses on providing environmental impact data and analytics for Filecoin storage providers. The platform targets blockchain participants and environmental stakeholders interested in sustainable storage solutions. The website is built using modern web technologies including React and integrates Umami analytics for user tracking. Hosting is managed via AWS infrastructure, as indicated by DNS records. While the site demonstrates a good level of technical maturity and user experience, it lacks critical privacy and security policy disclosures, as well as direct contact information, which impacts its overall trustworthiness and compliance posture. Security practices such as HTTPS are in place, but additional security headers and incident response details are absent.

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

8 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 filecoin.energy

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. 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
95
Security headers
15
Email security
60
DNS health
75
Network security
100
GDPR outside view
35
Average
63

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 business positions itself as a niche analytics provider within the blockchain energy sector, focusing on green metrics for Filecoin storage providers. Its business model revolves around data visualization and methodology publication, catering to a specialized audience. The domain age and registration details align with a legitimate startup or project, though the use of privacy protection obscures registrant identity. The absence of contact details and formal policies suggests an early-stage or lean operation. The platform leverages partnerships with Filecoin community channels for feedback, indicating community engagement. Growth potential exists in expanding transparency and compliance features to enhance credibility.

Security posture

The website employs HTTPS and avoids exposing sensitive data in its HTML content, reflecting baseline security hygiene. However, the lack of security headers such as Content-Security-Policy, X-Frame-Options, and X-XSS-Protection reduces its defense-in-depth. No vulnerability disclosures or incident response contacts are published, limiting readiness for security events. The absence of privacy and cookie policies indicates compliance gaps with GDPR and related regulations. Overall, the security maturity is moderate but requires enhancements in policy transparency and technical controls to mitigate risks effectively.

Recommendations

  1. Implement and publish comprehensive privacy and cookie policies to improve compliance and user trust.
  2. Enable DNSSEC on the domain to enhance DNS security.
  3. Add standard security headers (CSP, X-Frame-Options, X-XSS-Protection) to harden the website against common attacks.
  4. Provide clear contact information including incident response and abuse contacts to improve transparency and readiness.
  5. Conduct a security audit to identify and remediate any potential vulnerabilities and improve overall security posture.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Filecoin Green Dashboard provides data and methodology related to storage providers in the Filecoin network with a focus on environmental impact.
Key services
Data visualization, Methodology publication, Storage provider analytics
Content quality
good
Branding
consistent

Technology

Stack
React, JavaScript, Google Fonts, Umami Analytics, AWS DNS
Frameworks
React
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
75/100
Good practices seen
  • HTTPS enabled
  • No exposed sensitive data in HTML
  • Use of client-side JavaScript with deferred loading

Analytics and tracking

Services
Umami Analytics
Tracking level
minimal
Privacy practices
poor

Advertising

Tracking pixels
Umami Analytics
Marketing tools
Google Fonts
Transparency
basic

Site quality

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

Key observations

  1. Website is a data dashboard for Filecoin Green initiative
  2. No privacy, cookie, or terms of service pages found
  3. No direct contact emails or phone numbers found
  4. Uses modern React framework and Umami analytics
  5. Domain is privacy protected but legitimate
  6. No security headers detected in provided data
  7. No security or incident response policies published
  8. Content is safe and professional
  9. No advertising networks detected except analytics and fonts
Technical notes

Notes

The website is built on a React framework with client-side rendering and uses Google Fonts and Umami for analytics. Hosting is via AWS as indicated by DNS nameservers. The site loads scripts with defer attributes, optimizing performance. Mobile optimization is good, and navigation is clear. However, SEO optimization is basic with minimal meta tags beyond title and description. Accessibility features are present but limited. The absence of CMS suggests a custom or static site build. Performance is moderate, with potential for improvement through enhanced SEO and accessibility practices.
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 filecoin.energy. 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 filecoin.energy.

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.