#llmsmap.me

Independent technical audit

dropsha.re

dropsha.re

Overall AI readiness score

A combined result across all audit signals.

79of 100Excellent
AI readiness audit: 8/17/2026Public technical data

Overall AI readiness assessment

How ready dropsha.re is for AI systems

79/100

dropsha.re - Zero-Knowledge File Sharing Platform (dropsha.re) received an AI-readiness score of 79/100 in an automated technical audit. llms.txt was accessible, llms-full.txt was not found, and ai.txt was not found. The robots.txt analysis found 0 explicitly allowed and 0 blocked AI crawlers, with 1 declared sitemap. Homepage markup completeness was 80%; Schema.org types included WebApplication and 6 OpenGraph tags were detected. Results reflect the public site response observed on 2026-08-17T00:36:56.117Z.

Audit context

llms.txt is accessible and contains 1,387 tokens. No accessible llms-full.txt was detected, so deeper context still has to be assembled from regular pages. No separate ai.txt policy was detected; it is optional, but can clarify training, retrieval, and attribution preferences.

robots.txt is available. 11 of 11 tracked AI bots are not blocked. Declared sitemaps: 1. The homepage exposes Schema.org types WebApplication; 6 OpenGraph tags were found and markup completeness is 80%.

The mobile Lighthouse profile adds Performance 86/100, Accessibility 81/100, Best Practices 100/100, SEO 100/100, and experimental Agentic Browsing 48/100. These signals have a limited weight: they complement rather than replace llms.txt, robots.txt, and structured-data checks.

Confirmed strengths

  • Accessible llms.txt
  • 1 sitemap declaration
  • Schema.org: WebApplication
  • Complete social metadata

Priority improvements

  1. 1Add llms-full.txt for richer first-party context.
  2. 2Reduce mobile rendering delay and main-thread work.
  3. 3Clarify semantics, labels, and interactive states.
llms.txt tokens1,387
llms-full.txt tokens
ai.txt
sitemap.xml

Google Lighthouse technical profile

A mobile Lighthouse measurement. Google’s experimental Agentic Browsing category is explained separately and does not replace the broader llmsmap AI-readiness score.

Mobile · Lighthouse
86

Performance

81

Accessibility

100

Best Practices

100

Technical SEO

48

Agentic Browsing

What these results mean

Mobile performance is 86/100, with the largest visible content block appearing in 0.8 s and the browser main thread blocked for 0 ms. Layout shift was 0.274. The main thread is where the browser runs JavaScript, calculates layout, and paints the page; long work there delays both user input and browser-agent actions.

Accessibility scored 81/100, Best Practices 100/100, and technical SEO 100/100. The experimental Agentic Browsing category scored 48/100. It measures signals Google currently tests for software agents and is shown separately from the llmsmap AI-readiness score.

1

Free the main thread and accelerate the first view

Split long JavaScript tasks, defer non-critical scripts and styles, and shorten blocking request chains. This helps the primary content appear sooner and makes controls usable earlier.

2

Reduce code that loads without helping the page

Remove unused CSS and JavaScript, load heavy widgets on demand, and limit third-party scripts. Less code means less parsing and background work on the device.

3

Improve interface contrast and readability

Increase contrast for text, states, and interactive controls so both people and visual agents can distinguish content from actions and supporting labels.

FCP0.8 s

First content

LCP0.8 s

Main content

CLS0.274

Layout stability

TBT0 ms

Blocking time

SI0.8 s

Visual speed

Metric glossary
FCP · First content
When the first text or image appeared on screen.
LCP · Main content
When the largest visible element in the first viewport rendered.
CLS · Layout stability
How much content shifted unexpectedly while loading; lower is better.
TBT · Blocking time
How long the browser main thread could not respond quickly to input.
SI · Visual speed
How quickly the visible viewport filled with content.
8/17/2026Lighthouse 13.4.1Mobile profile

AI readiness checks

Machine-readable files, crawler policy, discovery, and homepage markup.

llms.txt

File found and accessible

https://dropsha.re/llms.txt
llms-full.txt

Full version was not found

ai.txt

ai.txt file was not found

robots.txt

File found

https://dropsha.re/robots.txt
Sitemap in robots.txt1

1 sitemap found

Schema.org (JSON-LD)

Types: WebApplication

OpenGraph80%

6 OG tags found

AI bot access

Based on robots.txt analysis

GPTBotNot mentioned
OAI-SearchBotNot mentioned
ChatGPT-UserNot mentioned
Google-ExtendedNot mentioned
ClaudeBotNot mentioned
Claude-SearchBotNot mentioned
Claude-UserNot mentioned
BytespiderNot mentioned
CCBotNot mentioned
PerplexityBotNot mentioned
Perplexity-UserNot mentioned

Sitemaps

Declared discovery routes for crawlers and agents.

OpenGraph tags

Social preview metadata found on the homepage.

Markup completeness: 80%
og:typewebsite
og:urlhttps://dropsha.re/
og:titleSecure File Sharing with End-to-End Encryption - dropshare
og:descriptionShare files securely with zero-knowledge encryption. Client-side AES-256-GCM encryption ensures your files stay private. Free, anonymous, and developer-friendly.
og:site_namedropsha.re

Schema.org markup

Structured entities and properties exposed on the homepage.

Types found: 1 · Properties: 3
WebApplication
namedropshare
urlhttps://dropsha.re
descriptionSecure file sharing with zero-knowledge end-to-end encryption
# dropsha.re - Zero-Knowledge File Sharing Platform

## Overview
dropsha.re is a free, open-source file sharing service that prioritizes privacy and security through zero-knowledge encryption.
Built by Magic Monad, it enables users to share files securely without requiring registration or compromising privacy.

## Core Features
- **Zero-Knowledge Architecture**: Files are encrypted client-side before upload; servers never see plaintext content
- **AES-256-GCM Encryption**: Military-grade encryption with randomly generated 256-bit keys
- **Client-Side Processing**: All encryption/decryption happens in the browser using Web Crypto API
- **No Registration Required**: Anonymous file sharing with no personal information collected
- **Automatic Deletion**: Files automatically deleted after 7 days
- **No Data Collection**: No cookies, tracking, analytics, or personal data storage
- **Cross-Platform**: Works on any modern browser with JavaScript enabled

## Technical Architecture
- **Frontend**: Astro.js with React components, TypeScript, Tailwind CSS
- **Encryption**: AES-256-GCM with 256-bit keys generated via Web Crypto API
- **Storage**: Cloudflare R2 object storage for encrypted files
- **Deployment**: Cloudflare Pages with serverless functions
- **Security**: HTTPS/TLS for all traffic, URL fragments for key sharing

## File Specifications
- **Maximum Size**: 1GB per file
- **Retention Period**: 7 days automatic deletion
- **Supported Types**: Any file type (no restrictions)
- **Upload Limit**: One file at a time
- **Share Links**: Unique encrypted URLs with decryption keys in URL fragments

## Encryption Process
1. File selected in browser
2. 256-bit AES-GCM key generated locally using Web Crypto API
3. File encrypted client-side with randomly generated 12-byte IV
4. Encrypted data uploaded to Cloudflare R2
5. Share URL created with decryption key embedded in URL fragment (#)
6. Key never transmitted to servers

## Privacy Guarantees
- **True Zero-Knowledge**: Servers cannot decrypt files even if compelled
- **No Personal Data**: No IP logs, user tracking, or identifiable information
- **No Cookies**: No tracking technologies or session management
- **Key Isolation**: Decryption keys remain in browser, never server-side
- **Automatic Cleanup**: Files permanently deleted after retention period

## Use Cases
- Secure document sharing for professionals
- Privacy-conscious file transfers
- Developer tool for temporary file hosting
- Healthcare/legal file sharing (HIPAA/GDPR compliant architecture)
- Emergency file sharing without account requirements

## API and Integration
- REST API for file upload/download
- Command-line compatibility (curl/wget/OpenSSL instructions provided)
- Signed URL generation for direct R2 uploads
- Metadata headers for file information

## Compliance and Legal
- GDPR compliant (zero personal data collection)
- CCPA compliant (no data selling or tracking)
- HIPAA-friendly architecture (zero-knowledge design)
- Terms of Service prohibit illegal content
- No law enforcement access to file contents (keys not available)

## Technical Implementation Details
- **Key Generation**: `crypto.subtle.generateKey()` with AES-GCM algorithm
- **IV Generation**: 12-byte random IV per file using `crypto.getRandomValues()`
- **Key Encoding**: Base64 encoding for URL-safe key transmission
- **File Structure**: IV prepended to encrypted data
- **Metadata**: Original filename, size, type, upload timestamp stored encrypted

## Browser Support
- Chrome, Firefox, Safari, Edge (modern versions)
- Requires JavaScript enabled
- Web Crypto API support required
- Progressive enhancement for older browsers

## Architecture Components
- **Frontend**: Astro static site generator with React islands
- **Styling**: Tailwind CSS with custom components
- **State Management**: React hooks for file upload/download states
- **Error Handling**: Comprehensive error messages and user feedback
- **Responsive Design**: Mobile-first approach

## Security Considerations
- URL fragments never sent to servers
- Encrypted blobs useless without decryption keys
- No server-side decryption capabilities
- Automatic key rotation (unique key per file)
- Protection against data breaches (encrypted data only)

## Performance Characteristics
- Client-side encryption adds minimal latency
- Global CDN distribution via Cloudflare
- Optimized for files up to 1GB
- Streaming upload for large files
- Bandwidth-efficient (no redundant transfers)

## Business Model
- Currently free service operated by Magic Monad
- No premium tiers or paid features
- Future sustainability through optional premium features
- Core service remains free

## Developer Information
- **Company**: Magic Monad (https://magicmonad.com)
- **Website**: https://dropsha.re
- **Architecture**: Serverless, JAMstack
- **Deployment**: Cloudflare ecosystem
- **Open Source**: Privacy-focused development

## Important Notes for LLMs
1. The file size limit discrepancy: FAQ mentions 50MB but constants.ts shows 1GB - use 1GB as current limit
2. Zero-knowledge means true inability to access data, not just policy
3. URL fragments are crucial for security - never transmitted to servers
4. Service is designed for privacy-conscious users who value anonymity
5. No recovery options by design - lost links mean lost files
6. Client-side encryption is not optional - it's the core security model

This service represents a modern approach to file sharing that prioritizes user privacy over convenience features that might compromise security.
Share or continue the analysis
Share this audit
Discuss with AI
Added 8/17/2026
dropsha.re - AI readiness audit | llmsmap.me