Skip to main content

Security report for antom.com

Antom · Finance · N/a

Medium risk. 6 critical or high findings in Security headers and GDPR outside view.

Security score

68/100

Risk levelMedium

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

Antom is a global payment solutions provider offering a comprehensive suite of payment products and enhanced features tailored for merchants across various verticals including e-commerce, gaming, travel, and digital services. Positioned as a leading player in the finance and technology sectors, Antom leverages its acquiring licenses and extensive global partnerships to serve over 1.6 billion consumers worldwide. The company operates under the parent entity Ant International and integrates with prominent partners such as Alipay+, Bettr, and WorldFirst. Technically, the website is built on modern frameworks like Next.js and React, hosted on Alibaba Cloud infrastructure, and utilizes a CDN for optimized performance. Security-wise, the site employs a valid SSL certificate but lacks advanced security headers and mechanisms such as HSTS and DNSSEC, indicating room for improvement in its security posture. Privacy and compliance documentation such as privacy policy, cookie policy, and terms of service are not explicitly found, which may pose compliance risks. Overall, the website demonstrates good design quality, user experience, and trustworthiness, supported by consistent branding and social media presence.

Scanned

This is an earlier scan of antom.com. View the latest report

NIS2 and GDPR posture

GDPR outside view
40/ 100 · High
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. 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 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 antom.com

This scan found 19 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
80
Security headers
15
Email security
85
DNS health
85
Network security
100
GDPR outside view
40
Average
68

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

Antom's market positioning as a major global payment processor is reinforced by its broad product portfolio and strategic partnerships. The business model focuses on providing unified payment solutions and digital marketing tools to merchants, enabling seamless cross-border and local transactions. Revenue streams likely derive from payment processing fees, subscription services, and value-added features like risk management and marketing rewards. The target audience includes enterprises and merchants in e-commerce, digital entertainment, travel, and mobility sectors. The company shows strong growth indicators through its extensive consumer reach and trusted brand associations. The partnership ecosystem with Ant International and other fintech entities enhances its competitive advantage and market penetration. Strategic observations suggest a focus on expanding digital marketing capabilities and enhancing payment orchestration to capture more market share.

Security posture

The current security maturity level of Antom's website is moderate. The presence of a valid SSL certificate and absence of known SSL vulnerabilities are positive indicators. However, the lack of HSTS, DNSSEC, and comprehensive security headers such as Content-Security-Policy and X-Frame-Options indicates gaps in defense-in-depth strategies. No explicit security policies or incident response contacts are published, which may affect transparency and readiness in case of security incidents. Compliance with GDPR and other data protection regulations is unclear due to missing privacy and cookie policies and absence of consent mechanisms. The security culture appears to be in early stages of formalization, with room to improve communication and documentation. Overall, the risk of data exposure or regulatory non-compliance exists but is mitigated by the use of modern infrastructure and partnerships with reputable entities.

Recommendations

  1. Enable HTTP Strict Transport Security (HSTS) with includeSubDomains and preload to enforce HTTPS and prevent downgrade attacks.
  2. Publish comprehensive privacy, cookie, and terms of service policies to improve compliance and user trust.
  3. Implement DNSSEC to protect against DNS spoofing and enhance domain security.
  4. Add security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to mitigate common web vulnerabilities.
  5. Establish and publish an incident response policy with dedicated contact channels to improve transparency and readiness.
Technical notes

Notes

The website is built using Next.js and React frameworks, served via a Tengine web server, and hosted on Alibaba Cloud infrastructure with CDN support from marmot-cloud.com. The tech stack is modern and supports good performance and mobile optimization. However, the absence of TLS 1.2 or TLS 1.3 protocols in the SSL configuration is unusual and may indicate incomplete SSL/TLS scanning or configuration issues. The site uses multiple asynchronously loaded JavaScript chunks and preloaded images for performance optimization. No CMS is explicitly detected. The DNS setup uses Aliyun MX records and Alipay nameservers, indicating integration with Alibaba's ecosystem. Performance metrics are not provided but inferred to be fast due to CDN usage and modern tech. Technical risks include missing advanced security configurations and lack of visible compliance mechanisms.
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

Earlier scans of this domain

  1. 66/100Medium31 findingsView report
Reviews of this site

Share your experience with antom.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 antom.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.