Skip to main content

Security report for soliditylang.org

Solidity Team · Technology · Switzerland

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

Security score

61/100

Risk levelMedium

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

Soliditylang.org is the official website for the Solidity programming language, a statically-typed language designed for developing smart contracts on the Ethereum blockchain. The site serves a global developer audience, providing comprehensive documentation, blog updates, community forums, and event information. It is maintained by the Solidity Team and positioned as a leading technology resource in the blockchain and smart contract development space. The business model is open-source and community-driven, with no direct commercial transactions on the site. Technically, the website is built using modern web technologies including Next.js and Chakra UI, hosted on Amazon AWS infrastructure. The site is fast, mobile-optimized, accessible, and SEO-friendly. It uses HTTPS exclusively, ensuring secure communications. However, some security best practices such as DNSSEC and explicit security headers are not enabled, and there is no cookie consent mechanism or dedicated privacy policy page on the site itself. From a security perspective, the site demonstrates good maturity with a published security policy and clear vulnerability reporting instructions. The domain registration is consistent and trustworthy, with no suspicious patterns. No critical vulnerabilities or exposed sensitive data were detected. Privacy compliance is partial, with the privacy policy hosted on GitHub rather than the main site, and no cookie consent mechanism present. Overall, soliditylang.org is a professional, trustworthy, and technically sound website serving a specialized developer community. Strategic improvements in privacy compliance and security headers would enhance its posture further. The site poses low risk and is a reliable resource for Ethereum smart contract developers.

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. 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 soliditylang.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. 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
72
Security headers
15
Email security
65
DNS health
80
Network security
100
GDPR outside view
35
Average
61

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

Soliditylang.org occupies a strong market position as the primary resource for the Solidity programming language, which is integral to Ethereum smart contract development. Its open-source, community-driven business model fosters collaboration and continuous improvement. The site supports a global developer base with educational content, forums, and events such as the Solidity Summit. Partnerships with Ethereum.org and Remix IDE enhance its ecosystem. The absence of direct commercial activity suggests revenue streams may come from sponsorships or related services. Growth indicators include regular releases, active community engagement, and frequent blog updates. The project is well-established since 2020 and headquartered in Switzerland, reflecting a mature and credible operation.

Security posture

The security posture of soliditylang.org is solid, with HTTPS enforced and domain transfer protections in place. The presence of a published security policy and vulnerability disclosure instructions indicates a mature security culture. However, the lack of DNSSEC and missing security headers such as Content Security Policy and HSTS represent areas for improvement. No signs of malware, phishing, or exposed credentials were found. Privacy compliance is partial, lacking cookie consent and a dedicated privacy policy page on the main site. Incident response mechanisms are documented via GitHub. Overall, the site demonstrates good security hygiene but could enhance defenses and compliance to meet higher standards.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Implement and publish a cookie policy with a consent mechanism to comply with GDPR and other privacy regulations.
  3. Add standard security headers such as Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), X-Frame-Options, and X-Content-Type-Options.
  4. Host a dedicated privacy policy page on the main website for better user accessibility and compliance.
  5. Provide explicit contact information for security incidents and data protection officer if applicable.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Solidity Team
Description
Solidity is a statically-typed curly-braces programming language designed for developing smart contracts that run on Ethereum.
Key services
Smart contract programming language development, Documentation and educational resources, Community forums and events
Content quality
excellent
Branding
consistent

Technology

Stack
React, Next.js, Chakra UI, JavaScript, TypeScript
Frameworks
Next.js, Chakra UI
Platforms
Web
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Client transfer prohibited domain status
  • Security policy published
  • Vulnerability reporting instructions

Analytics and tracking

Tracking level
minimal
Privacy practices
basic

Advertising

Transparency
poor

Site quality

Design
excellent
User experience
excellent
Content relevance
excellent
Navigation
excellent
Professionalism
excellent
Trustworthiness
high

Key observations

  1. Website is a professional, well-maintained open-source project site for Solidity programming language.
  2. Content is rich with documentation, blog updates, events, and community engagement.
  3. No privacy or cookie policy page found on the website itself; privacy policy is hosted on GitHub.
  4. No contact emails or phone numbers explicitly provided on the website.
  5. Security policy and vulnerability reporting instructions are clearly provided.
  6. No advertising or tracking scripts detected in the HTML content.
  7. Modern web technologies and frameworks are used for site implementation.
  8. No WAF or blocking mechanisms detected; site fully accessible.
Technical notes

Notes

The website is built on a modern React-based stack using Next.js for server-side rendering and Chakra UI for styling, ensuring a responsive and accessible user interface. Hosting on AWS provides reliable infrastructure. The site demonstrates fast load times and good SEO practices with comprehensive meta tags and Open Graph data. No CMS is detected, indicating a custom or static site generation approach. The absence of third-party advertising or tracking scripts reduces privacy risks and improves performance. Technical debt appears low, with opportunities to enhance security headers and DNS configuration. Overall, the technical implementation supports a high-quality user experience and robust platform for the Solidity community.
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 soliditylang.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 soliditylang.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.