fshy

Home / Crawling

archive.today

archive.ph/Archivecrawler-scraper/archive-todayJSONcomparereport an errorprovider JSON

Free allowance
No account and no key stated; a 429 was the answer to the first followed request
Verdict
deadthe offer or the service no longer exists
Cost
no price stated
Identity
anonymousno card, no phone
Binding limit
request-rate429 on the first followed request; no published allowance
Evidence
measured3 sources; a live request was made and its output kept
Freshness
checked 2026-10-22checked 2026-10-22 (live)
Free tierno account and no key stated; a 429 was the answer to the first followed request
unit requests; metered on request-count; the allowance is not published anywhere reachable
Pricenone stated
Limits
  • request-rate (binding) 429 on the first followed request; no published allowance source
an unpublished allowance is worse than a small one: there is no threshold to design against
Identityanonymous no account was asked for
Egressnot applicable: it answers HTML
Per-object capnot applicable: the unit is a capture
Retentioncaptures are kept indefinitely, which is the service's purpose
Interfacerest an HTML route, /newest/<url>; no JSON API
Toolingnone published
Composes withNothing chains to it: the only programmatic route answers a challenge
Reliability429 with a 59,077-byte challenge page on the first followed request
NotesThe 2035 timestamp in the redirect is the finding worth keeping: a caller that trusts the redirect records a capture that does not exist. Three routes, three refusals, so the class is closed for programmatic use.
Evidence notemeasured no page read
Parsed numbers
  • has-free-tier 0
Evidence 3
datesourcewhat it proved
2026-10-22archive.ph/newest/https://example.com302 to https://archive.ph/20351231145959/http://example.com/, a timestamp in 2035, so the redirect names no real capture
2026-10-22archive.ph/newest/https://example.com429 with 59,077 bytes when the redirect was followed
2026-10-22archive.today/301 with a zero byte body