Skip to main content

Security report for layeredge.io

LayerEdge · Technology · Iceland

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

Security score

65/100

Risk levelMedium

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

LayerEdge is a technology startup focused on providing fast, low-cost verification of zero-knowledge and validity proofs to enable scalable and permissionless innovation on blockchain protocols such as Bitcoin and Ethereum. The company positions itself as a provider of verification services and node operation roles including validators, light nodes, and full nodes. The website content is minimal and currently shows an application error, limiting full content access. The company has established partnerships with multiple blockchain and security firms, indicating an active ecosystem engagement. Technically, the website is built using modern frameworks such as React and Next.js, hosted on AWS infrastructure with Cloudfront CDN. However, the site suffers from an application error on the main page, basic mobile optimization, and lacks accessibility and SEO best practices. No CMS is detected, and the site does not currently implement security headers or DNSSEC. From a security perspective, HTTPS is enabled with good SSL configuration, but the absence of security headers and DNSSEC reduces the overall security posture. No privacy, cookie, or terms of service policies are published, and no incident response or vulnerability disclosure information is available. The domain is privacy protected, which is justified for a technology startup, and the domain age aligns with the company's founding year. Overall, the website's risk profile is moderate due to the application error, lack of security policies, and minimal content. Strategic improvements in security headers, policy publication, and resolving the application error are recommended to enhance trust and compliance.

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

7 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
    • 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

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

Keep watching layeredge.io

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
77
Security headers
20
Email security
70
DNS health
70
Network security
100
GDPR outside view
50
Average
65

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

LayerEdge operates in the blockchain technology sector, focusing on verification of zero-knowledge proofs to support scalability and security of major blockchain networks. The business model revolves around providing infrastructure services for blockchain validators and node operators. The company targets developers, blockchain projects, and technology innovators seeking scalable verification solutions. Partnerships with recognized blockchain and security companies strengthen its market position. The company is newly founded in 2024 and appears to be a small-sized startup. Revenue streams likely include node operation rewards and service fees. The partnership ecosystem is broad, indicating strategic collaboration to enhance technology adoption.

Security posture

The current security maturity level is basic. HTTPS is enforced with good SSL configuration, but critical security headers are missing, and DNSSEC is not enabled, exposing the domain to potential DNS spoofing risks. No privacy or cookie policies are published, indicating compliance gaps with GDPR and other privacy regulations. Incident response readiness is unclear due to lack of published contact channels for security issues. No vulnerabilities or exposed sensitive data were detected in the accessible content, but the application error may mask deeper issues. The security culture appears immature, with room for improvement in policy transparency and technical safeguards.

Recommendations

  1. Resolve the client-side application error to restore full website functionality and improve user experience.
  2. Publish comprehensive privacy, cookie, and terms of service policies to enhance compliance and user trust.
  3. Implement security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to strengthen security posture.
  4. Enable DNSSEC on the domain to protect against DNS spoofing and improve domain security.
  5. Establish and publish vulnerability disclosure and incident response procedures with clear contact channels.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
LayerEdge
Description
LayerEdge provides fast, low-cost verification of zero-knowledge/validity proofs, enabling scalable, permissionless innovation on Bitcoin, Ethereum, and other protocols.
Key services
Verification of zero-knowledge/validity proofs, Support for Bitcoin, Ethereum, and other blockchain protocols, Node operation roles including Validator, Light Node, and Full Node
Content quality
poor
Branding
moderate

Technology

Stack
React, Next.js, AWS DNS, Cloudfront CDN
Frameworks
React, Next.js
Platforms
AWS
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
50/100
Good practices seen
  • HTTPS enforced

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website currently shows an application error on main page indicating client-side exception.
  2. No privacy, cookie, or terms of service policies found.
  3. No contact emails or phone numbers explicitly provided.
  4. Social media links present for Medium, Telegram, Discord, and X (Twitter).
  5. Multiple partner domains linked indicating active partnership ecosystem.
  6. No security headers detected and DNSSEC not enabled.
  7. HTTPS is enabled with good SSL configuration.
  8. Content is minimal and mostly technical placeholders due to error page.
  9. No forms detected on the accessible page.
  10. No analytics or advertising scripts detected.
Technical notes

Notes

The website uses a modern technology stack including React and Next.js frameworks, hosted on AWS infrastructure with Cloudfront CDN for content delivery. While the infrastructure is modern, the site suffers from a client-side application error that prevents full content rendering. Mobile optimization and accessibility are basic, and SEO practices are minimal with only essential meta tags present. No CMS is detected, indicating a custom or framework-based site. The absence of security headers and DNSSEC represents technical debt and security risk. Performance is moderate but could be improved by resolving errors and optimizing resources.
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 layeredge.io. 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 layeredge.io.

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.