Skip to main content

Security report for interledger.org

Interledger Foundation · Technology · United States

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

Security score

67/100

Risk levelMedium

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

The Interledger Foundation is a US-based nonprofit organization founded in 2015 that leads the development and stewardship of the Interledger protocol, an open-source technology enabling interoperability between diverse financial systems globally. The foundation focuses on grantmaking, community building, and advancing open financial standards to foster financial inclusion and economic opportunity worldwide. The website reflects a professional, well-branded presence with comprehensive content targeting fintech startups, remittance users, small businesses, and gig workers. Technically, the site is built on Drupal 10, uses Cloudflare for DNS, and employs modern web standards with good mobile optimization and accessibility. Analytics are handled via Umami, indicating a privacy-conscious approach with minimal user tracking. However, DNSSEC is not enabled, and some security headers are missing, representing areas for improvement. Security posture is solid with HTTPS enforced and domain registration consistent with the foundation's identity. No critical vulnerabilities or exposed sensitive data were detected. Privacy compliance is good with a clear privacy policy and terms of service, though no explicit cookie consent mechanism was found. Contact is available via a form but no direct emails or phone numbers are published. Overall, the website is trustworthy, professional, and well-aligned with the foundation's mission. Strategic recommendations include enabling DNSSEC, adding security headers, publishing incident response and vulnerability disclosure policies, and implementing cookie consent to enhance compliance and security transparency.

Scanned

NIS2 and GDPR posture

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

5 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 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. 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.

    • High

      No SPF record found

      SPF helps prevent email spoofing

      What to do: Add SPF record: "v=spf1 include:_spf.yourmailprovider.com ~all"

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

Keep watching interledger.org

This scan found 24 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
85
Security headers
40
Email security
50
DNS health
75
Network security
100
GDPR outside view
53
Average
67

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

Interledger Foundation occupies a unique niche as a nonprofit steward of open financial protocols designed to enable seamless payments across different ledgers and currencies. Its business model centers on grantmaking and community support rather than direct commercial services. The foundation targets fintech startups, remittance users, small businesses, and content creators, positioning itself as an enabler of financial inclusion and innovation. The organization benefits from a strong open-source ethos and a growing ecosystem of partners and developers. Its market position is that of a thought leader and standards body in the emerging field of interoperable digital payments. The foundation's longevity since 2015 and consistent branding reinforce credibility and stability.

Security posture

The website demonstrates a mature security posture with mandatory HTTPS, clientTransferProhibited domain status, and use of Cloudflare DNS. However, the absence of DNSSEC and missing security headers such as Content-Security-Policy and Strict-Transport-Security reduce the overall security hardening. No incident response or security policy pages were found, which could limit transparency and preparedness. No vulnerabilities or exposed sensitive data were detected in the content. Privacy compliance is good but could be improved with explicit cookie consent mechanisms. Overall, the security posture is solid but could benefit from additional best practices and transparency measures.

Recommendations

  1. Enable DNSSEC on the domain to protect against DNS spoofing and improve DNS security.
  2. Implement security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to enhance browser security.
  3. Publish explicit security policies and incident response procedures on the website to improve transparency and preparedness.
  4. Add a cookie consent banner or mechanism to comply with privacy regulations and improve user trust.
  5. Consider publishing a vulnerability disclosure policy or security.txt file to facilitate responsible reporting of security issues.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Interledger Foundation
Description
The Interledger Foundation is a global nonprofit grantmaking foundation, leading the next revolution in payments through Interledger, the global network for inclusive digital financial service providers.
Key services
Open standards development, Grant funding, Community building, Developer resources
Content quality
excellent
Branding
consistent

Technology

Stack
Drupal 10, Cloudflare DNS, HTML5, CSS3, JavaScript
Frameworks
Drupal
Performance
moderate
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • Client transfer prohibited domain status
  • Use of Cloudflare DNS

Analytics and tracking

Services
Umami Analytics
Tracking level
minimal
Privacy practices
good

Advertising

Tracking pixels
Umami Analytics
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges
  2. Content is rich, well-structured, and professionally presented
  3. Strong focus on open financial protocols and community engagement
  4. No direct contact emails or phone numbers found; contact via form only
  5. No explicit cookie consent mechanism detected
  6. Social media presence is strong and consistent with brand
  7. No security.txt or explicit vulnerability disclosure found
  8. DNSSEC not enabled, which is a minor security gap
  9. Use of modern CMS (Drupal 10) and CDN/DNS provider (Cloudflare)
Technical notes

Notes

The website is built on Drupal 10, a modern and widely supported CMS, indicating good technical maturity. It uses Cloudflare for DNS, which provides resilience and performance benefits. The site includes responsive design and accessibility features, enhancing user experience across devices. The use of Umami analytics reflects a privacy-conscious approach. Performance is moderate, likely due to video content and rich media. No outdated or vulnerable libraries were detected in the provided content. The site lacks DNSSEC and some security headers, which are recommended for improved security posture. Overall, the technical infrastructure is solid with room for incremental improvements.
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 interledger.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 interledger.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.