Skip to main content

Security report for aave.com

Aave · Finance · N/a

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

Security score

72/100

Risk levelMedium

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

Aave is a leading decentralized finance (DeFi) protocol that enables users to supply, borrow, swap, and stake digital assets across multiple blockchain networks. It operates as a non-custodial liquidity market with a strong emphasis on open-source development and community governance. The platform holds a prominent market position as one of the largest liquidity protocols in the DeFi space, offering innovative services such as the Aave-native stablecoin GHO and multi-network deployment capabilities. The website reflects a mature and professional digital presence with excellent design, clear navigation, and comprehensive content tailored to DeFi users, developers, and financial institutions. Technically, the site leverages modern web technologies including React and Next.js, hosted on Cloudflare for performance and security. It is optimized for mobile devices and accessibility, with fast loading times and proper SEO practices. Security is robust, featuring HTTPS, security headers, public audit reports, and a bug bounty program hosted on Immunefi. However, DNSSEC is not enabled, and a security.txt file is absent, which are areas for improvement. The security posture is strong with no detected vulnerabilities or exposed sensitive data. Privacy compliance is well addressed with clear privacy and cookie policies, including consent mechanisms and GDPR adherence. Business credibility is high, supported by transparent domain registration, consistent branding, and trust signals such as community governance and partnerships. No direct contact emails or phone numbers are publicly listed, which is common for decentralized protocols but could be enhanced for user support. Overall, Aave presents a secure, trustworthy, and technically advanced platform with a clear focus on DeFi innovation and community engagement. Strategic recommendations include enabling DNSSEC, publishing a security.txt file, and enhancing incident response contact transparency to further strengthen trust and security culture.

Scanned

NIS2 and GDPR posture

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

5 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. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • 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

    • 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

  3. 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 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 aave.com

This scan found 20 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
40
Email security
85
DNS health
80
Network security
100
GDPR outside view
53
Average
72

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

Aave operates in the decentralized finance sector, providing liquidity markets that allow users to earn interest and borrow assets without custodial intermediaries. Its business model revolves around protocol fees, staking rewards, and stablecoin issuance. The platform targets crypto investors, developers, and institutions seeking DeFi solutions. Market positioning is strong as a top liquidity protocol with multi-chain support and a broad ecosystem of partners and integrations. Revenue streams likely include protocol fees and token economics related to AAVE and GHO tokens. Growth indicators include active governance, extensive developer resources, and partnerships with analytics and DeFi infrastructure providers. The company maintains a transparent and open-source approach, fostering trust and community participation.

Security posture

Aave demonstrates a mature security posture with enforced HTTPS, comprehensive security headers, and a proactive bug bounty program via Immunefi. The protocol's non-custodial design minimizes custodial risk, and public audit reports enhance transparency. No critical vulnerabilities or exposed sensitive data were detected in the website content. Privacy policies and cookie consent mechanisms align with GDPR requirements. However, the absence of DNSSEC and a security.txt file are minor gaps. Incident response contact channels are indirect, relying on bug bounty platforms rather than explicit security emails. Overall, the security culture appears strong but could benefit from enhanced direct communication channels and DNS security improvements.

Recommendations

  1. Enable DNSSEC to improve DNS security and prevent spoofing.
  2. Publish a security.txt file to standardize security contact information.
  3. Provide explicit incident response and abuse contact emails on the website.
  4. Enhance transparency around data protection officer or privacy contacts.
  5. Regularly update and publicly share security audit results and remediation status.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Aave
Description
Aave is an Open Source Protocol to create Non-Custodial Liquidity Markets to earn interest on supplying and borrowing assets with a variable interest rate. The protocol is designed for easy integration into your products and services.
Key services
Liquidity supply, Asset borrowing, Token swapping, Staking, Stablecoin issuance (GHO), Developer integrations
Content quality
excellent
Branding
consistent

Technology

Stack
React, Next.js, Cloudflare, Web3 integrations, SVG graphics, Immunefi bug bounty
Frameworks
Next.js
Platforms
Ethereum, Multiple EVM-compatible networks
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
90/100
Good practices seen
  • HTTPS enforced
  • Bug bounty program
  • Security audit reports publicly available
  • Non-custodial protocol design
  • Client transfer prohibited domain status

Analytics and tracking

Tracking level
minimal
Privacy practices
good

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Strong focus on decentralized finance services and developer integrations.
  3. Comprehensive security and vulnerability disclosure presence.
  4. Good privacy and cookie policy with consent mechanisms.
  5. No direct contact emails or phone numbers found on main site.
  6. Multiple partnerships and integrations with DeFi ecosystem projects.
  7. Modern, performant, and mobile-optimized website design.
  8. No adult or questionable content detected.
Technical notes

Notes

The website is built using modern web technologies including React and Next.js, ensuring a performant and responsive user experience. Hosting on Cloudflare provides CDN, DDoS protection, and SSL termination. The site uses SVG graphics extensively for scalable visuals and supports multiple EVM-compatible blockchain networks. SEO and accessibility practices are well implemented with proper meta tags and responsive design. No CMS was detected, indicating a custom or static site generation approach. Performance is fast with preloading of fonts and scripts. Technical risks are minimal, though enabling DNSSEC and adding a security.txt file would further harden the infrastructure.
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. 73/100Medium26 findingsView report
Reviews of this site

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