Skip to main content

Security report for base.app

Base · Technology · N/a

Low risk. 2 critical or high findings in GDPR outside view and SSL/TLS.

Security score

80/100

Risk levelLow

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

Base is a technology platform focused on enabling users to create, earn, trade, discover applications, and chat with friends within a unified environment. The website positions itself as an emerging player in the app and social interaction market, targeting a general audience interested in digital creation and social engagement. The platform's business model appears to revolve around providing tools and a marketplace for app-related activities and social communication. Technically, the site leverages modern frameworks such as Next.js and React, indicating a contemporary and scalable infrastructure. The inclusion of Google Tag Manager and Coinbase scripts suggests integration with analytics and payment services, respectively. Security-wise, the website benefits from HTTPS and uses standard analytics tools but lacks visible security headers and formal security policies, which could be improved to enhance trust and compliance. Privacy compliance is weak due to the absence of explicit privacy and cookie policies, and no contact information is readily available for users or security incidents. Overall, the site is professional and safe for general audiences but would benefit from enhanced transparency and security documentation.

Scanned

NIS2 and GDPR posture

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

2 findings rated critical or high. Fix these first.

  1. GDPR outside view

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

    • 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

  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 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 base.app

This scan found 15 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
85
Email security
70
DNS health
80
Network security
100
GDPR outside view
68
Average
80

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

Base operates in the technology sector, focusing on app creation and social interaction. Its market positioning is that of an innovative platform combining multiple digital services in one place. The business model likely includes user engagement through app creation, trading, and social features, potentially monetized via transactions or premium services. The target customer segment is broad, encompassing creators and social users. The platform shows signs of growth potential with integrations to major services like Coinbase. However, the lack of detailed business information, contact data, and formal policies limits full assessment of its operational maturity and partnership ecosystem.

Security posture

The website demonstrates a moderate security posture with HTTPS enabled and use of reputable analytics tools. However, it lacks several security best practices such as security headers (CSP, X-Frame-Options), explicit privacy and cookie policies, and incident response contact information. No vulnerability disclosures or security certifications are evident. The absence of a security.txt file and formal incident response channels suggests limited readiness for handling security incidents. These gaps present moderate risks, especially as the platform may handle user data and transactions. Enhancing these areas would improve compliance with GDPR and other regulations, and strengthen user trust.

Recommendations

  1. Implement and publish comprehensive privacy and cookie policies with clear GDPR compliance statements.
  2. Add security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to improve security posture.
  3. Provide explicit contact information including security incident response channels (e.g., security@ or abuse@ emails).
  4. Publish a security.txt file to facilitate vulnerability disclosures and demonstrate security transparency.
  5. Regularly audit third-party scripts and dependencies to mitigate risks from vulnerable libraries.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Base
Description
Create, earn, trade, discover apps, and chat with friends all in one place. Join the waitlist.
Key services
App creation, Earning, Trading, App discovery, Chat with friends
Content quality
good
Branding
consistent

Technology

Stack
Next.js, React, Google Tag Manager, Coinbase SDK
Frameworks
Next.js, React
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enabled
  • Use of Google Tag Manager for analytics

Analytics and tracking

Services
Google Analytics (via Google Tag Manager)
Tracking level
moderate
Privacy practices
poor

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Website uses modern web technologies (Next.js, React).
  2. No explicit privacy, cookie, or terms of service policies found on the main page.
  3. No contact emails or phone numbers explicitly provided in the visible content.
  4. Google Tag Manager and Coinbase scripts indicate analytics and possible payment integration.
  5. No security.txt or vulnerability disclosure information found.
  6. Content is professional and targeted at general users interested in app creation and social features.
  7. No adult or questionable content detected.
  8. No WAF or blocking mechanisms detected; content fully accessible.
Technical notes

Notes

The website is built using Next.js and React, indicating a modern and performant web application framework. It uses Google Tag Manager for analytics and includes Coinbase scripts, likely for payment or crypto-related functionality. The site appears mobile-optimized with responsive design elements. Performance is moderate, with proper use of preload and async script loading. However, accessibility features are basic and could be improved. SEO is supported by appropriate meta tags and Open Graph data. No CMS or hosting provider details are explicitly detected. The technical implementation is solid but could benefit from enhanced security configurations and accessibility improvements.
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 base.app. 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 base.app.

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.