Skip to main content

Security report for apecoin.com

Ape Foundation · Technology · N/a

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

Security score

74/100

Risk levelMedium

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

ApeCoin is a cryptocurrency token project officially associated with the Bored Ape Yacht Club NFT community. It supports decentralized governance, digital asset marketplaces, and community proposals, targeting Web3 enthusiasts, gamers, and digital artists. The website is well designed, mobile optimized, and uses modern technologies such as React and Next.js hosted on Cloudflare infrastructure. Security posture is strong with HTTPS enforcement, security headers, and a bug bounty program, though DNSSEC is not enabled and no explicit security or incident response policies are published. Privacy compliance is partially met with a clear privacy policy and terms of service but lacks a cookie consent mechanism. Overall, the domain registration is consistent and trustworthy, supporting the legitimacy of the project.

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 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 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 apecoin.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
57
Security headers
60
Email security
85
DNS health
90
Network security
100
GDPR outside view
53
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

ApeCoin holds a strong market position as the official token of the Bored Ape Yacht Club, a leading NFT community. Its business model revolves around token governance, digital marketplaces, and community engagement. The project targets a niche but growing segment of Web3 users and digital asset collectors. Partnerships with snapshot.org for governance and immunefi.com for security bounty programs indicate a mature ecosystem. The absence of phone or physical address suggests a primarily digital-native organization. The website content and branding are consistent and professional, supporting credibility and trust.

Security posture

The website demonstrates a mature security posture with HTTPS, multiple security headers, and domain registration protections. The presence of a bug bounty program on Immunefi shows proactive vulnerability management. However, the lack of DNSSEC and absence of published security policies or incident response contacts are gaps. No forms or inputs on the main page reduce attack surface. No exposed sensitive data or vulnerable libraries detected. Overall security score is high but could be improved with enhanced DNS security and transparency on security policies.

Recommendations

  1. Enable DNSSEC to strengthen DNS security and prevent spoofing.
  2. Implement a visible cookie consent banner to comply with privacy regulations.
  3. Publish a dedicated security policy and incident response information on the website.
  4. Add contact information for a data protection officer or privacy compliance officer.
  5. Consider adding a security.txt file to facilitate vulnerability disclosures.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Ape Foundation
Description
A token made to support the evolution of art, gaming, entertainment, digital and physical events, storytelling, and everything else web3 dreams up. The official token of Bored Ape Yacht Club.
Key services
Token governance, Marketplace for digital assets, Community proposals and voting, Delegation services
Content quality
good
Branding
consistent

Technology

Stack
React, Next.js, Cloudflare
Frameworks
Next.js
Platforms
Cloudflare Pages
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Domain status includes clientDeleteProhibited, clientTransferProhibited, clientUpdateProhibited
  • Bug bounty program available

Analytics and tracking

Services
Cloudflare Pages Analytics
Tracking level
minimal
Privacy practices
basic

Advertising

Tracking pixels
Cloudflare Pages Analytics
Transparency
basic

Site quality

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

Key observations

  1. Website is professionally designed and well structured.
  2. Content is relevant to the Web3 and NFT community.
  3. No forms detected that collect user data directly on the main page.
  4. Social media presence is active with official Twitter and Instagram links.
  5. No phone numbers or physical addresses found.
  6. Bug bounty program linked externally indicating proactive security posture.
  7. No cookie consent banner or explicit cookie policy detected.
  8. No explicit security policy or incident response details published on site.
Technical notes

Notes

The website uses a modern React and Next.js framework hosted on Cloudflare Pages, ensuring fast performance and good mobile optimization. The site is SEO optimized with proper meta tags and Open Graph data. No CMS detected, indicating a custom or static site generation approach. The use of deferred JavaScript and prefetching improves load times. Accessibility is good with semantic HTML and ARIA roles. No technical debt or deprecated technologies observed. The site benefits from Cloudflare's CDN and security features but could improve DNS security by enabling DNSSEC.
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 apecoin.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 apecoin.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.