Skip to main content

Security report for ecommpay.com

Ecommpay · Finance · United Kingdom

Medium risk. 4 critical or high findings in Security headers and SSL/TLS.

Security score

74/100

Risk levelMedium

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

Ecommpay is a UK-based international payment service provider and direct bank card acquirer, specializing in bespoke, data-driven payment solutions tailored for ecommerce businesses ranging from mid-sized to enterprise level. The company offers a comprehensive suite of payment services including direct acquiring, over 100 alternative payment methods, open banking, direct debits, and payment orchestration, positioning itself as a full-stack payment ecosystem provider. Their market position is strengthened by industry certifications such as ATOL and IATA, and a strong focus on customer support and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
83/ 100 · Low
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 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. 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 Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

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

Keep watching ecommpay.com

This scan found 20 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
20
Email security
85
DNS health
85
Network security
100
GDPR outside view
83
Average
74

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

The company targets high-growth ecommerce businesses seeking seamless and scalable payment solutions. Their business model revolves around providing integrated payment services with a focus on customization and customer excellence. Ecommpay maintains a robust partnership ecosystem and leverages modern technologies to deliver fast onboarding and improved payment experiences. Their strategic emphasis on compliance and certifications enhances trust and market credibility. The presence of multiple subdomains for dashboard and developer resources indicates a mature operational infrastructure supporting clients and developers.

Security posture

Ecommpay demonstrates a mature security posture with enforced HTTPS, integration of advanced bot protection mechanisms like Cloudflare Turnstile and Google reCAPTCHA Enterprise, and a comprehensive cookie consent mechanism via Cookiebot. The website employs multiple security best practices including session management and use of security-related cookies. However, there is room for improvement by enabling DNSSEC and explicitly publishing security headers and incident response contacts. No critical vulnerabilities or exposed sensitive data were detected, indicating a secure environment suitable for handling financial transactions.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Implement and explicitly declare security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Publish a dedicated incident response or security contact page/email to improve transparency and readiness.
  4. Consider adding a security.txt file to facilitate responsible vulnerability disclosure.
  5. Maintain and regularly audit third-party scripts and cookies to ensure ongoing compliance and security.

Contact details published on the site

Addresses
Legal name
Ecommpay
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Ecommpay
Description
Ecommpay is an international payment service provider and a direct bank card acquirer, engineering bespoke, data-driven payment solutions for ecommerce businesses worldwide.
Key services
direct acquiring, alternative payment methods (100+), open banking, Direct Debits, payment orchestration, subscriptions and recurring payments, payouts, virtual payment terminal, payment links, currency choice
Content quality
excellent
Branding
consistent

Technology

Stack
Google Tag Manager, Google reCAPTCHA Enterprise, Cookiebot, Cloudflare Turnstile, HubSpot, Hotjar, New Relic, Akamai, AWS DNS, Figma, Marker.io, Imperva
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Use of Cloudflare Turnstile for bot protection
  • Google reCAPTCHA Enterprise integration
  • Cookie consent with Cookiebot
  • Session management cookies
  • No exposed sensitive data found in HTML

Analytics and tracking

Services
Google Analytics, Hotjar, HubSpot, LinkedIn Insight Tag
Tracking level
extensive
Privacy practices
good

Advertising

Ad networks
Google DoubleClick, Facebook, Google AdSense, HubSpot
Tracking pixels
Hotjar, HubSpot, LinkedIn Insight Tag
Marketing tools
HubSpot, Statsig (multi-variate testing)
Transparency
good

Site quality

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

Key observations

  1. Website is professionally designed with comprehensive content and clear navigation.
  2. Strong privacy and cookie compliance with explicit consent mechanisms.
  3. Use of multiple security and analytics technologies indicating mature digital infrastructure.
  4. No signs of blocking or WAF challenges; full content accessible.
  5. WHOIS data supports legitimacy and long-term operation.
  6. No exposed sensitive data or obvious vulnerabilities detected in HTML content.
Technical notes

Notes

The website is hosted on AWS infrastructure with DNS managed via AWS DNS services and uses Akamai and Cloudflare for load balancing and security. The technology stack includes Google Tag Manager, HubSpot, Hotjar, New Relic, and Cookiebot, indicating a modern and well-instrumented platform. The site is mobile-optimized with responsive design and good accessibility features. Performance is fast with proper use of preloading and asynchronous script loading. The presence of multiple subdomains for developer and dashboard services reflects a modular and scalable architecture. Overall, the technical implementation supports a high-quality user experience and robust operational capabilities.
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 ecommpay.com. 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 ecommpay.com.

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.