Skip to main content

Security report for autopay.eu

Autopay S.A. · Finance · Poland

Low risk. 2 critical or high findings in Security headers and SSL/TLS.

Security score

82/100

Risk levelLow

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

Autopay S.A. is a well-established payment processing company founded in 1999, offering a broad range of payment solutions including card processing, 3DS authentication, and data-driven insights. The company targets businesses such as e-commerce platforms, fintechs, and payment service providers, positioning itself as a trusted partner with regulatory supervision and certifications like PCI DSS. The website reflects a mature digital presence with modern technologies like Vue.js and Bootstrap, integrated analytics, and a strong cookie consent mechanism. Security posture is robust with HTTPS, security headers, and no visible vulnerabilities. However, explicit security policies and incident response contacts are not published, representing an area for improvement. Overall, the site is professional, trustworthy, and compliant with GDPR requirements.

Scanned

NIS2 and GDPR posture

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

2 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. 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 autopay.eu

This scan found 17 issues across 5 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
77
Security headers
65
Email security
70
DNS health
80
Network security
100
GDPR outside view
100
Average
82

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

Autopay operates in the finance and technology sectors, serving a large customer base including over 50,000 online stores and about 300 banks and institutions. Its business model revolves around providing scalable and secure payment processing services, supported by partnerships with major card networks like Visa and Mastercard. The company emphasizes innovation, global reach, and tailored solutions for various market segments. The presence of regional partner domains indicates a multi-market strategy. Trust indicators such as certifications and regulatory oversight enhance its credibility. The website content and structure support clear communication of services and business value.

Security posture

The website demonstrates a good security maturity level with enforced HTTPS, comprehensive cookie consent management, and use of security headers. No exposed sensitive data or vulnerable libraries were detected in the HTML content. The use of Matomo and Google Tag Manager is managed with privacy considerations. However, the absence of a published security policy, incident response plan, or vulnerability disclosure program limits transparency. No direct security contact emails were found. The site would benefit from publishing these documents and contacts to improve security culture and incident readiness.

Recommendations

  1. Publish a dedicated security policy and incident response information on the website.
  2. Implement and publicize a vulnerability disclosure program or security.txt file.
  3. Provide direct security contact channels such as security@ or abuse@ emails.
  4. Enhance website accessibility features to improve compliance and user experience.
  5. Regularly audit and update third-party scripts and analytics tools to mitigate risks.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Autopay S.A.
Description
Autopay provides innovative and flexible payment processing solutions trusted by thousands of companies, enabling seamless transactions, enhanced security, and business growth.
Key services
Card processing, 3DS Authentication, Support API, Payment gateway solutions, Data-driven insights and advertising
Content quality
good
Branding
consistent

Technology

Stack
Vue.js, Bootstrap 5, Consentmanager.net, Matomo Analytics, Google Tag Manager
Frameworks
Bootstrap
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Cookie consent with granular controls
  • Use of security headers
  • No exposed sensitive data in HTML
  • Use of official analytics with privacy controls

Analytics and tracking

Services
Matomo, Google Tag Manager, YourCX
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Matomo, YourCX
Marketing tools
Consentmanager.net
Transparency
good

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenge.
  2. Strong cookie consent mechanism with granular user controls.
  3. No explicit terms of service page found.
  4. Contact information is primarily via contact form; no direct emails or phone numbers found in HTML.
  5. Use of modern frontend technologies and analytics tools.
  6. Good security posture with HTTPS and security headers.
  7. Business is well established with certifications and regulatory supervision.
  8. No suspicious or malicious content detected.
  9. Website content is professional and business-focused.
Technical notes

Notes

The website uses a modern technology stack including Vue.js for frontend interactivity and Bootstrap 5 for responsive design. It integrates third-party services for consent management and analytics, including Consentmanager.net, Matomo, and Google Tag Manager. The site is mobile optimized with good navigation clarity and SEO metadata. Performance is moderate, with asynchronous loading of scripts and lazy loading of images. No popular CMS was detected, suggesting a custom or proprietary platform. Hosting provider details are not explicitly available. Overall, the technical infrastructure supports a professional and scalable web presence with room for performance optimization and enhanced accessibility.
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 autopay.eu. 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 autopay.eu.

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.