Skip to main content

Security report for ibcprotocol.org

Interchain Foundation · Technology · N/a

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

Security score

73/100

Risk levelMedium

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

The Inter-Blockchain Communication Protocol (IBC) website serves as the primary informational and developer resource portal for the IBC protocol, a leading blockchain interoperability standard used by over 115 chains. The site is professionally designed with a focus on technology and developer engagement, offering extensive resources, documentation, and ecosystem insights. The business is positioned as a key player in blockchain interoperability, supported by the Interchain Foundation and a broad community of contributors. Technically, the website leverages modern web technologies including React and Next.js, with a performant and mobile-optimized design. The use of Google Tag Manager indicates moderate analytics and tracking capabilities. The site is hosted on a modern platform with strong SSL and security headers, reflecting a mature digital infrastructure. From a security perspective, the site enforces HTTPS and includes standard security headers, with no visible vulnerabilities or sensitive data exposure. However, it lacks explicit security policies, incident response information, and a cookie consent mechanism, which are areas for improvement to enhance compliance and user trust. Overall, the website presents a low-risk profile with high professionalism and technical maturity. Strategic enhancements in privacy compliance and security transparency would further strengthen its position and trustworthiness.

Scanned

NIS2 and GDPR posture

GDPR outside view
70/ 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

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

  3. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching ibcprotocol.org

This scan found 19 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
55
Email security
60
DNS health
80
Network security
100
GDPR outside view
70
Average
73

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

IBC is a widely adopted blockchain interoperability protocol with a strong ecosystem of over 115 chains. The business model revolves around open-source protocol development and ecosystem enablement, targeting blockchain developers and projects. The Interchain Foundation funds and supports the protocol, with contributions from independent developers. The website reflects a strong market position with partnerships and testimonials from notable blockchain projects. Revenue streams are indirect, likely through ecosystem growth and foundation funding. Growth indicators include annual network growth of 34% and over 2 million monthly active users. The partnership ecosystem includes major blockchain projects and developer communities, reinforcing strategic market presence.

Security posture

The website demonstrates a mature security posture with enforced HTTPS, comprehensive security headers, and no detected vulnerabilities or exposed sensitive data. The use of light client-based interoperability in the protocol itself enhances security by removing trusted third parties. However, the absence of a published security policy, incident response plan, and vulnerability disclosure mechanism limits transparency and preparedness. Privacy compliance is basic, with a privacy policy present but no cookie consent or GDPR-specific indicators. Incident response readiness and security culture indicators are not explicitly documented, suggesting room for improvement in formal security governance and user communication.

Recommendations

  1. Implement a cookie consent banner to comply with privacy regulations and enhance user trust.
  2. Publish a detailed security policy and incident response plan accessible from the website.
  3. Add a terms of service page to clarify user and developer obligations and legal protections.
  4. Establish and publicize a vulnerability disclosure program or security.txt file to encourage responsible reporting.
  5. Enhance privacy compliance by including GDPR-specific information and data retention policies.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Interchain Foundation
Description
IBC is a blockchain interoperability protocol used by over 115 chains for cross-chain communication.
Key services
Blockchain interoperability protocol, Cross-chain communication, Developer tooling and resources
Content quality
excellent
Branding
consistent

Technology

Stack
React, Next.js, JavaScript, CSS, Google Tag Manager
Frameworks
Next.js
Platforms
Web
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
90/100
Good practices seen
  • HTTPS enforced
  • No visible sensitive data exposure
  • Use of security headers
  • No vulnerable libraries detected

Analytics and tracking

Services
Google Tag Manager
Tracking level
moderate
Privacy practices
basic

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Website is a professional, well-designed portal for the IBC blockchain interoperability protocol.
  2. Strong presence of developer resources and ecosystem information.
  3. No direct contact emails or phone numbers found on the site.
  4. Privacy policy is present but basic; no cookie consent mechanism detected.
  5. No terms of service or explicit security policy pages found.
  6. Use of modern web technologies and frameworks.
  7. Good SEO and accessibility practices observed.
  8. No signs of malicious or suspicious content.
Technical notes

Notes

The website is built on a modern React and Next.js stack, ensuring fast performance and excellent mobile responsiveness. It uses Strapi as a CMS for content management, inferred from media URLs. The hosting environment is likely a modern cloud platform optimized for Next.js applications. SEO is well implemented with comprehensive meta tags and Open Graph data. Accessibility features are present, contributing to a good user experience. No technical debt or legacy technology indicators were found. The site integrates Google Tag Manager for analytics and marketing, indicating a moderate level of user tracking. Overall, the technical infrastructure is robust, scalable, and aligned with current best 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 ibcprotocol.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 ibcprotocol.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.