Skip to main content

Security report for qupital.com

Qupital · Finance · Hong Kong

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

Security score

62/100

Risk levelMedium

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

Qupital is a fintech company founded in 2016, specializing in providing data-driven funding solutions for e-commerce businesses, particularly in the cross-border market. The platform offers financing services to e-commerce sellers and an investment platform for investors seeking alternative investment opportunities. The website is multilingual, targeting primarily Hong Kong and broader Chinese-speaking markets, with English support. The business model leverages big data to optimize financing and investment decisions, positioning Qupital as a niche player in fintech for e-commerce.

Scanned

NIS2 and GDPR posture

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

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 qupital.com

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
62
Security headers
15
Email security
85
DNS health
75
Network security
100
GDPR outside view
35
Average
62

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 qupital.com, from OffSeq Breach.

Total records
3
Employees
0
Customers
3
Third parties
0
Weak passwords
0%

1 subdomain 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 qupital.com.

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

Qupital operates in the finance and e-commerce sectors, focusing on bridging funding gaps for online sellers and providing investment avenues for funders. The company maintains a moderate size and has a clear digital presence with dedicated subdomains for sellers and investors. Its competitive advantage lies in its data-driven approach and fintech innovation. The lack of visible privacy and cookie policies suggests room for improvement in compliance and transparency. Partnerships and subsidiaries appear limited but focused on core service delivery.

Security posture

The website employs HTTPS and standard domain protections such as clientDeleteProhibited status. However, DNSSEC is not enabled, and no security headers were detected in the provided data, indicating potential areas for security enhancement. There is no published security policy or incident response information, which could impact trust and compliance. The site uses modern CMS and plugins but should improve security best practices by enabling DNSSEC, adding security headers, and publishing security-related policies.

Recommendations

  1. Enable DNSSEC to protect against DNS spoofing and improve domain security.
  2. Implement and configure security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Publish comprehensive privacy and cookie policies with clear GDPR compliance and consent mechanisms.
  4. Add a security policy and incident response contact information to enhance transparency and trust.
  5. Regularly audit third-party plugins and scripts to ensure no vulnerable libraries are in use.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Qupital
Description
Data-Driven Funding for E-commerce Businesses, expand your business with quality financing services and solutions rooted in big data.
Key services
E-commerce financing solutions, Investment platform for alternative investments, Partnerships with e-commerce sellers
Content quality
good
Branding
consistent

Technology

Stack
WordPress 6.0.9, Elementor, Yoast SEO, jQuery, Amazon Polly, AutoNumeric, Marquee Image Crawler
Frameworks
Elementor
Platforms
WordPress
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
70/100
Good practices seen
  • HTTPS enabled
  • Domain status includes clientDeleteProhibited and other EPP protections

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is multilingual with English, Traditional Chinese (Hong Kong), and Simplified Chinese versions
  2. No explicit privacy, cookie, or terms of service pages found in the provided content
  3. Contact information such as emails or phone numbers not explicitly found in the HTML content
  4. Social media presence limited to Facebook page link
  5. Uses modern WordPress plugins and themes with SEO optimization
  6. No visible security.txt or vulnerability disclosure information
  7. No visible certifications or security policies published
  8. Forms present for login and application but no detailed form fields extracted due to content truncation
Technical notes

Notes

The website is built on WordPress 6.0.9 with Elementor and Yoast SEO plugins, indicating a modern and SEO-optimized infrastructure. Hosting appears to be on AWS, supported by AWS DNS servers. The site includes advanced UI components such as AutoNumeric for input formatting and Amazon Polly for text-to-speech. Performance is moderate with good mobile optimization. Accessibility is basic and could be improved. The technical stack is well-chosen for the business needs but requires security hardening and compliance enhancements.
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 qupital.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 qupital.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.