kappa.lol (page title: segs.lol)
- Free allowance
- No account and no stated per-file cap on the page read; the upload API takes a multipart 'file' field and answers with JSON.
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- not statedsee Price below
- Identity
- anonymousno card, no phone
- Binding limit
- noneno named constraint binds
- Evidence
- measured3 sources; a live request was made and its output kept
- Freshness
- stale on 2026-11-23checked 2026-10-23 (live); stale on 2026-11-23
| Free tier | No account and no stated per-file cap on the page read; the upload API takes a multipart 'file' field and answers with JSON. unit none; metered on none |
|---|---|
| Price | USD 0 |
| Limits |
The page title is 'segs.lol', not the host name: the brand and the domain disagree, which is the kind of drift that breaks a hard-coded allow-list. |
| Binding | none No documented constraint exists to name. At 1 TiB a month nothing in the seven-value vocabulary was observed to bind, because neither a cap nor a retention limit nor a rate is published; the honest answer is that the ceiling is unmeasured, not absent. |
| Identity | anonymous One multipart POST with no cookie and no account returned a link; the reply also carries a delete URL, which is the only control the uploader gets. |
| Egress | Downloads are served from kappa.lol; no byte counter and no download counter are published. free allowance: none published |
| Per-object cap | unverified: no cap is published on the page; 1 MiB was accepted |
| Retention | unverified: no expiry is published and the upload reply carries no expiry field |
| Interface | rest, cli POST https://kappa.lol/api/upload multipart field 'file'. JSON reply: id, ext, type, checksum (MD5), key, link, delete. endpoint: https://kappa.lol/api/upload |
| Tooling | An official uploader exists at github.com/Mald-Entertainment-Studio/uploader; curl works with one multipart POST |
| Composes with | A stored URL with no extension is a clean drop for a script that only needs a link a human can open; it pairs with a checksum check from the client side because the service returns MD5 itself. |
| Reliability | The reply URL carries no file extension (https://kappa.lol/P224n5), so a client that infers type from the URL gets application/octet-stream regardless of the real bytes. |
| Notes | Useful as a one-line anonymous store, unusable as an archive until the cap and retention are measured. The absent extension in the returned URL is the practical trap: a resumption test keyed on Content-Type will see application/octet-stream for every file. |
| Evidence note | measured Upload, read-back and SHA-256 match. The record stays at measured even though the cap and retention are unverified, because neither is claimed as a number here. |
| Parsed numbers |
|
Evidence 3
| date | source | what it proved |
|---|---|---|
| 2026-10-23 | probe: https://kappa.lol/api/upload | POST of 1 048 576 bytes -> HTTP 200, JSON {'id':'P224n5','ext':'.bin','checksum':'0316a02c6c0e8b28ad82065de17289c4','link':'https://kappa.lol/P224n5'}; the checksum equals the MD5 of the uploaded file |
| 2026-10-23 | probe: https://kappa.lol/P224n5 | read-back 1 048 576 bytes, sha256 da0099c231f1182a5d411c8ac5149dfb7a2e3578a3970928490cb78ba92aecc9, full-body hash matched |
| 2026-10-23 | kappa.lol/ | the page <title> is 'segs.lol'; no size or retention number appears on the page |
More fields 2
| md5 echoed | 0316a02c6c0e8b28ad82065de17289c4 |
|---|---|
| delete url in reply | yes |