Skip to main content

Security report for webmonetization.org

Interledger Foundation · Technology · United States

Medium risk. 6 critical or high findings in Email security, Security headers and 2 other checks.

Security score

66/100

Risk levelMedium

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

The website webmonetization.org is operated by the Interledger Foundation and serves as the official hub for the Web Monetization API, a technology standard enabling websites to receive payments automatically from visitors. Positioned as an innovator within the web standards community, the site targets developers, content creators, and organizations interested in integrating micropayments into web experiences. The business model revolves around promoting an open, interoperable protocol leveraging the Interledger payment system. Technically, the site is built with modern frameworks such as Astro, optimized for performance, mobile responsiveness, and accessibility. It uses Cloudflare DNS and minimal external dependencies, with a clean, professional design and clear navigation. Security posture is solid with HTTPS enforced and no exposed sensitive data, though some security headers and formal policies are absent. Privacy compliance is strong, with comprehensive policies hosted via Iubenda. Overall, the site is trustworthy, professional, and well-aligned with its stated mission.

Scanned

NIS2 and GDPR posture

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

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

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

Keep watching webmonetization.org

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
75
Security headers
15
Email security
60
DNS health
80
Network security
100
GDPR outside view
68
Average
66

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention webmonetization.org, from OffSeq Breach.

Total records
35
Employees
0
Customers
35
Third parties
0
Weak passwords
23%

3 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for webmonetization.org.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

The Interledger Foundation operates webmonetization.org to promote the Web Monetization API as a new web standard for streaming payments. The foundation leverages partnerships with W3C groups and payment protocol providers like Interledger and Open Payments. The site supports a small but focused audience of developers and content creators, offering tools, libraries, and wallet integrations. Referral links to wallet providers indicate some monetization or partnership revenue streams. The foundation's market position is that of a standards innovator and ecosystem enabler rather than a commercial vendor. The presence of active GitHub repositories and community links suggests ongoing development and engagement. The business model is primarily open standard promotion with ecosystem growth as a key objective.

Security posture

The website demonstrates a mature security posture with HTTPS enforced and no visible vulnerabilities or sensitive data leaks. However, it lacks explicit security policies, incident response contacts, and security.txt or vulnerability disclosure documents. DNSSEC is not enabled, which is a recommended improvement. Minimal tracking is used, respecting user privacy. The absence of forms reduces attack surface. Overall, the site is secure for its purpose but could enhance transparency and formal security governance documentation to improve trust and compliance.

Recommendations

  1. Enable DNSSEC on the domain to strengthen DNS security and prevent spoofing.
  2. Publish a formal security policy and incident response contact information on the website.
  3. Add security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to HTTP responses.
  4. Implement a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  5. Consider adding a cookie consent mechanism to comply with evolving privacy regulations.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Interledger Foundation
Description
The Web Monetization API allows websites to automatically and passively receive payments from Web Monetization-enabled visitors. It aims to provide an open, native, efficient, and automatic way to compensate creators, pay for content, and support crucial web infrastructure.
Key services
Web Monetization API specification, Open Payments-enabled wallets, Developer tools and libraries, Educational resources and playground
Content quality
excellent
Branding
consistent

Technology

Stack
Astro v5.11.0, JavaScript, CSS custom properties, Cloudflare DNS
Frameworks
Astro
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced (implied by canonical URL and external links)
  • No forms collecting sensitive data
  • No exposed credentials or sensitive data in HTML

Analytics and tracking

Services
Umami
Tracking level
minimal
Privacy practices
good

Advertising

Transparency
good

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 focused on a technical standard for web payments.
  3. No direct contact emails or phone numbers found on the site.
  4. Privacy and cookie policies are outsourced to Iubenda and are comprehensive.
  5. No forms or data collection fields present on the homepage.
  6. Use of modern web framework Astro and good SEO practices.
  7. No explicit security policy or incident response information published.
  8. Referral affiliate links present for some wallet providers.
  9. No advertising or tracking beyond minimal analytics (Umami).
Technical notes

Notes

The website is built using Astro v5.11.0, a modern static site generator framework, ensuring fast load times and good SEO. The use of CSS custom properties and responsive design techniques provides excellent mobile optimization and accessibility. Hosting appears to leverage Cloudflare DNS services, contributing to performance and reliability. The site uses minimal external scripts, primarily for analytics (Umami) and referral tracking. No CMS is detected, indicating a static or JAMstack architecture. The technical implementation is modern and well-executed, with opportunities to improve security headers and DNS configuration.
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 webmonetization.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 webmonetization.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.