八八ファイル便 / 88file.jp

Free allowance: Claims '容量無制限のファイル転送を無料にて提供します' (unlimited-capacity file transfer, free) and 'データ送信量の制限はありません' — no send-volume limit, free, ad-free, domestic Japanese servers.
Verdict: caveatusable, with a named limit or an unprobed read path
Cost: free tier
Identity: anonymous?placeholder, not evidence; card unknown, phone unknown
Binding limit: noneno named constraint binds
Evidence: inferred2 sources; reasoned from other evidence
Freshness: stale on 2026-11-21checked 2026-10-21 (inherited); stale on 2026-11-21

Free tier	Claims '容量無制限のファイル転送を無料にて提供します' (unlimited-capacity file transfer, free) and 'データ送信量の制限はありません' — no send-volume limit, free, ad-free, domestic Japanese servers. unit unlimited; metered on unstated
Price	none stated
Identity	anonymous (inferred, not read) not published
Egress	No metered egress claimed; ad-free at the free tier.
Per-object cap	not stated
Retention	not stated
Interface	rest rest
Tooling	Web form only. No API.
Composes with	Nominally unlimited x unlimited, but unverified — the entire upload and pricing surface returned 503.
Reliability	This is the classic Japanese small-host failure mode: the marketing page stays up and the actual service is down. Every functional URL 503'd while the root page served fine, which is exactly the 'never trust HTTP 200' trap in reverse — here the 200 was the brochure and the 503 was the service.
Parsed numbers	has-free-tier 1

Evidence 2

date	source	what it proved
2026-10-21	88file.jp/	'容量無制限のファイル転送を無料にて提供します', 'データ送信量の制限はありません'
2026-10-21	source not published	probe: GET /datafiles/new -> 503, /plan -> 503, /faq -> 503, /about -> 503, body title '八八ファイル便 - 現在システムメンテナンス中'

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