fshy

Home / Storage

transfer.archivete.am

transfer.archivete.amAnonymous dumpstorage/transfer-archivete-amJSONcomparereport an errorprovider JSON

Free allowance
No account; no published per-file cap (transfer.sh successor, same DutchCoders codebase)
Verdict
fails: quotathe free allowance is too small to matter
Cost
free tier
Identity
anonymous?placeholder, not evidence; card unknown, phone unknown
Binding limit
noneno named constraint binds
Evidence
reported2 sources; a third party said so
Freshness
stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
Free tierno account; no published per-file cap (transfer.sh successor, same DutchCoders codebase)
unit mixed; metered on unstated
Pricenone stated
Identityanonymous (inferred, not read) not published
Egressunmetered direct links; plain GET returns bytes
Per-object capnot stated
Retentionnot stated
Interfacerest, cli rest
Toolingcurl --upload-file ./f https://transfer.archivete.am/f — the original transfer.sh CLI contract, unchanged. Also supports /virustotal and /scan suffixes.
Composes withnone — per-file only, no account surface. N files with independent expiry.
ReliabilityTHE transfer.sh successor that actually answers. This is the one live instance found; the long list of 'transfer.sh alternatives' blogs mostly point at dead clones.
Parsed numbers
  • has-free-tier 1
Evidence 2
datesourcewhat it proved
2026-10-21transfer.archivete.am/'Easy file sharing from the command line', curl upload/download examples
2026-10-21source not publishedprobe: PUT --upload-file -> 200 + URL + X-Url-Delete; GET -> 200 / 32768 B / sha256 match
More fields 2
dead end{"failure_class": "quota","why": "no account; no published per-file cap (transfer.sh successor, same DutchCoders codebase)","retry_when": null,"first_recorded": "2026-10-21"}
probe reportedPUT --upload-file probe.bin -> 200, body 'https://transfer.archivete.am/8Rt07/probe.bin', header X-Url-Delete present; GET that URL -> 200, 32768 B, application/octet-stream, sha256 MATCH
Unknown values 4
  • per object cap notes: the field may be stated in a source that was not read
  • per object cap stated: the field may be stated in a source that was not read
  • retention notes: the field may be stated in a source that was not read
  • retention stated: the field may be stated in a source that was not read