Skip to main content

Security report for amply.finance

Amply Finance · Finance · N/a

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

Amply Finance is a decentralized finance platform operating on the Cronos zkEVM blockchain, offering peer-to-pool lending and borrowing services. The platform enables users to deposit crypto assets to earn interest or borrow against collateral, with additional incentives through its native $AMPLY token. Positioned as a niche DeFi lending protocol, Amply Finance targets both newcomers and experienced users within the Cronos ecosystem. The website is professionally designed with clear navigation and modern UI frameworks, reflecting a good level of digital maturity. Technically, the platform leverages React, Next.js, and Chakra UI, providing a responsive and moderately performant user experience. Security-wise, the platform enforces HTTPS and has undergone a SlowMist audit, indicating a commitment to secure smart contract deployment. However, the absence of explicit security headers and limited public WHOIS data slightly reduce the overall security posture. Privacy compliance is basic, with a privacy policy present but lacking cookie consent mechanisms. Overall, Amply Finance presents a credible and functional DeFi service with room for improvement in transparency and security best practices.

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 amply.finance

This scan found 25 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
75
Security headers
15
Email security
75
DNS health
70
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

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Amply Finance operates in the competitive DeFi lending sector, focusing on the Cronos zkEVM chain. Its business model centers on liquidity provision and borrowing, generating revenue through interest rate spreads and token incentives. The platform's competitive advantages include its native token rewards, yield optimization tools, and integration with emerging DeFi ecosystems like H2 Finance. Target customers range from crypto enthusiasts seeking passive income to borrowers needing instant liquidity. Growth indicators include active social media channels and recent feature launches such as E-Mode and liquidation simulators. Partnerships with platforms like H2 Finance enhance its ecosystem reach. Strategic observations suggest Amply Finance should enhance transparency, expand compliance documentation, and strengthen security disclosures to build greater trust and scale effectively.

Security posture

Amply Finance demonstrates a moderate security maturity level. The use of HTTPS and a third-party audit by SlowMist are positive indicators. However, the lack of visible security headers such as Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), and X-Frame-Options reduces defense-in-depth. No explicit incident response or security policy information is published, which may hinder rapid response to security events. Privacy compliance is basic, with no cookie consent mechanism detected. No vulnerabilities or exposed sensitive data were found in the HTML content. To improve, Amply Finance should implement comprehensive security headers, publish incident response contacts, and enhance privacy controls. These steps will mitigate risks and align with industry best practices.

Recommendations

  1. Implement and enforce security headers including CSP, HSTS, and X-Frame-Options to strengthen web security.
  2. Publish a detailed security policy and incident response plan with clear contact channels for vulnerability reporting.
  3. Add a cookie consent banner to comply with privacy regulations and improve user trust.
  4. Provide clear and verified contact information for business and security inquiries on the website.
  5. Regularly update and publicly share audit results and security assessments to maintain transparency.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Amply Finance
Description
Amply Finance is a peer-to-pool borrow and lending protocol on the Cronos zkEVM Chain. Access instant liquidity, earn interest on your assets, and participate in the protocol's growth with $AMPLY token.
Key services
Crypto lending pools, Borrowing against collateral, Yield optimization tools, Native token staking and rewards
Content quality
good
Branding
consistent

Technology

Stack
React, Next.js, Chakra UI, JavaScript
Frameworks
Next.js, Chakra UI
Platforms
Cronos zkEVM blockchain
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Use of audited smart contracts (SlowMist audit)

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
basic

Advertising

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 challenges.
  2. WHOIS data is unavailable due to TLD restrictions; domain registrar is Identity Digital Inc.
  3. No explicit contact emails or phone numbers found on the site.
  4. Privacy policy is present and linked in documentation.
  5. No cookie consent mechanism detected.
  6. Security headers are not explicitly visible in the HTML content.
  7. Google Analytics is used for tracking.
  8. Social media presence includes Discord, Telegram, and X (Twitter).
  9. Site uses modern web technologies and frameworks.
  10. Audited by SlowMist, indicating some security diligence.
Technical notes

Notes

The website is built using modern web technologies such as React and Next.js, with Chakra UI for styling, indicating a contemporary and maintainable codebase. The site is moderately performant with good mobile optimization and basic accessibility features. SEO is well addressed through proper meta tags and Open Graph data. Hosting details are not explicitly disclosed, but the presence of Google Analytics indicates standard tracking practices. The lack of a CMS suggests a custom or static site generation approach. Technical risks include missing security headers and limited privacy controls, which could be addressed to reduce attack surface and improve compliance. Overall, the technical infrastructure supports the business goals but can benefit from enhanced security and privacy implementations.
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 amply.finance. 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 amply.finance.

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.