Skip to main content

Security report for openpayments.dev

Technology · N/a

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

Security score

61/100

Risk levelMedium

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

Open Payments is a technology-focused website providing an open API standard aimed at facilitating interoperability in payment setups and completions. The site targets developers, financial institutions, and payment service providers interested in implementing open payment standards. It positions itself as a niche player in the payment interoperability space, offering documentation and open source resources hosted on GitHub. The business model revolves around providing open standards rather than direct commercial services. Technically, the website is built using modern frameworks such as Astro and Starlight, hosted likely on Netlify, and employs SVG graphics and client-side search functionality. The site demonstrates good performance, mobile optimization, and accessibility, with a clean and professional design. SEO practices are well implemented with proper meta tags and Open Graph data. From a security perspective, the site uses HTTPS and avoids exposing sensitive data. However, it lacks explicit security headers and formal security policies such as privacy, cookie, or incident response information. Analytics usage is minimal and privacy compliance is low due to missing policies. No vulnerabilities or suspicious elements were detected in the content or scripts. Overall, the website is trustworthy and professional but would benefit from adding privacy and cookie policies, contact information, and enhanced security headers to improve compliance and user trust. The domain WHOIS data aligns well with the website content, supporting legitimacy.

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

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 openpayments.dev

This scan found 25 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
72
Security headers
15
Email security
70
DNS health
60
Network security
100
GDPR outside view
50
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

Open Payments operates as an open API standard provider in the technology sector, focusing on payment interoperability. Its competitive advantage lies in offering an open, standardized approach to payment setup and completion, appealing to developers and financial institutions seeking interoperability solutions. The business model is based on open standards and community collaboration rather than direct revenue generation. The presence of a GitHub repository indicates active open source engagement. The target customers are technical users and organizations involved in payment processing. Growth potential depends on adoption by financial entities and integration into payment ecosystems. No direct partnerships or subsidiaries are indicated on the site.

Security posture

The website demonstrates a moderate to good security posture with HTTPS enforced and no visible sensitive data exposure. However, it lacks explicit security headers such as Content Security Policy (CSP), HSTS, and X-Frame-Options, which are recommended best practices. There are no published security policies, incident response contacts, or vulnerability disclosure mechanisms, which limits transparency and readiness for security incidents. Privacy compliance is weak due to the absence of privacy and cookie policies. No known vulnerabilities or malicious scripts were detected. Overall, the security maturity is adequate for an informational site but should be enhanced for better compliance and trust.

Recommendations

  1. Implement and publish a comprehensive privacy policy and cookie policy to improve GDPR compliance and user trust.
  2. Add security headers including CSP, HSTS, and X-Frame-Options to strengthen site security.
  3. Provide clear contact information including security incident response contacts or abuse emails.
  4. Establish a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  5. Regularly audit and update analytics and tracking practices to align with privacy best practices.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Open Payments is an open API standard that can be implemented by account servicing entities to facilitate interoperability in the setup and completion of payments for different use cases.
Key services
Open API standard for payments, Documentation for implementation, Open source code repository on GitHub
Content quality
good
Branding
consistent

Technology

Stack
Astro v5.11.1, Starlight v0.34.7, Pagefind search, Custom JavaScript, SVG graphics
Frameworks
Astro, Starlight
Performance
fast
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced (implied by canonical URL https://)
  • No exposed sensitive data in HTML
  • No visible vulnerable libraries

Analytics and tracking

Services
ilf-site-analytics
Tracking level
minimal
Privacy practices
poor

Advertising

Tracking pixels
ilf-site-analytics.netlify.app
Transparency
basic

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
moderate

Key observations

  1. Website is an open API standard documentation site for payment interoperability.
  2. No privacy, cookie, or terms of service policies found on the site.
  3. No contact emails, phone numbers, or physical addresses are provided.
  4. Site uses modern web technologies and is well-structured and accessible.
  5. Security posture is good but lacks explicit security policies and headers.
  6. Analytics usage is minimal and privacy compliance is low due to missing policies.
  7. No advertising or affiliate marketing detected.
  8. No adult or questionable content present.
  9. WHOIS data supports legitimacy and consistency.
Technical notes

Notes

The website is built on a modern static site generation framework (Astro) combined with the Starlight UI framework, ensuring fast load times and good mobile responsiveness. Hosting appears to be on Netlify, inferred from analytics script sources. The site uses SVG for logos and icons, enhancing scalability and visual quality. Client-side search is implemented via Pagefind. The technical implementation is clean with no broken elements detected. However, there is room for improvement in security headers and formal privacy compliance. The absence of a CMS suggests a static content approach, which reduces attack surface but requires manual updates. Overall, the technical infrastructure is modern, performant, and well-structured.
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 openpayments.dev. 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 openpayments.dev.

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.