Skip to main content

Security report for soonly.pl

Soonly · Finance · Poland

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

Soonly.pl is a Polish fintech company positioned as a leader in the consumer finance sector in Poland. The website presents Soonly as a provider of modern financial products and solutions tailored to contemporary customer needs. The business targets modern consumers in Poland seeking consumer finance services. The website content is professional and consistent with fintech industry standards, though explicit privacy and terms of service pages are not found, which is a gap in compliance and transparency. Technically, the website is built on the Webflow platform, utilizing modern web fonts, analytics tools such as Microsoft Clarity and Google Analytics, and a cookie consent management system via Cookiebot. The site is mobile optimized and demonstrates good SEO practices. However, security headers and explicit SSL configuration details are not visible in the provided data, suggesting room for improvement in security hardening. From a security posture perspective, the site uses HTTPS and cookie consent mechanisms, but lacks visible security policies, incident response contacts, or vulnerability disclosure information. The absence of WHOIS data due to privacy protection is common in fintech but limits domain trust verification. Overall, the site appears legitimate but would benefit from enhanced transparency and security documentation. The overall risk assessment is moderate with recommendations to publish privacy and terms policies, add contact information, implement security headers, and maintain regular security audits to strengthen trust and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
88/ 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 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
    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching soonly.pl

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
52
Security headers
30
Email security
85
DNS health
90
Network security
100
GDPR outside view
88
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

Soonly operates in the fintech consumer finance market in Poland, positioning itself as a leader. The business model revolves around providing financial products and solutions to modern consumers. The website content and metadata emphasize innovation and customer-centric services. The company likely targets individual consumers and possibly small businesses seeking consumer finance. The use of Webflow and modern analytics indicates a digitally mature approach. No direct partnerships or subsidiaries are identified from the website content. The lack of explicit business registration details or contact information limits deeper business intelligence insights but the brand appears established and focused on growth within Poland's fintech sector.

Security posture

The website demonstrates a basic to moderate security posture. HTTPS is enforced, and cookie consent is managed via Cookiebot, indicating GDPR awareness. Analytics tools are used responsibly with consent mechanisms. However, no explicit security headers or policies are detected, and no incident response or vulnerability disclosure information is published. The absence of WHOIS data limits domain trust verification. No vulnerabilities or malware indicators are found in the content. The site would benefit from publishing a privacy policy, terms of service, security policy, and incident response contacts. Implementing security headers such as CSP, HSTS, and X-Frame-Options would enhance protection against common web attacks. Overall, the security posture is adequate but could be improved for higher trust and compliance.

Recommendations

  1. Publish a comprehensive privacy policy page detailing data processing and GDPR compliance.
  2. Add terms of service and security policy pages to improve transparency and legal compliance.
  3. Implement and verify HTTP security headers (CSP, HSTS, X-Frame-Options, X-XSS-Protection).
  4. Provide clear contact information including security incident response and data protection officer contacts.
  5. Consider publishing a security.txt file to facilitate vulnerability disclosure and improve security culture.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Soonly
Description
Poznaj Soonly - polski fintech tworzący produkty i rozwiązania dopasowane do potrzeb nowoczesnych klientów. Zobacz nasze nowości i otwarte stanowska.
Key services
consumer finance products, fintech solutions
Content quality
good
Branding
consistent

Technology

Stack
Webflow, Google Fonts (Poppins, Outfit), Microsoft Clarity, Cookiebot, Google Tag Manager, jQuery, Splide.js
Frameworks
Webflow
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
70/100
Good practices seen
  • HTTPS enforced (implied by canonical URL)

Analytics and tracking

Services
Microsoft Clarity, Google Analytics (implied by cookies)
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Microsoft Clarity
Marketing tools
Cookiebot consent management
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenge
  2. No explicit privacy policy or terms of service pages found
  3. Cookie consent mechanism implemented via Cookiebot
  4. No direct contact emails or phone numbers found on main page
  5. Uses modern web technologies and analytics tools
  6. WHOIS data is not publicly available, indicating privacy protection
  7. Content is professional and focused on fintech consumer finance in Poland
Technical notes

Notes

The website is built on the Webflow platform, leveraging modern web fonts (Poppins, Outfit), and includes analytics via Microsoft Clarity and Google Tag Manager. Cookie consent is managed by Cookiebot, ensuring user privacy preferences are respected. The site uses Splide.js for UI components and loads resources from reputable CDNs. Performance is moderate with good mobile optimization and basic accessibility features. SEO is supported by proper meta tags and Open Graph data. No CMS other than Webflow CMS is detected. Hosting is likely via Webflow's infrastructure. Technical debt appears low, but security hardening and accessibility improvements are recommended to enhance overall quality and resilience.
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 soonly.pl. 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 soonly.pl.

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.