archive.today
archive.ph · Crawling · 1 record · JSON
archive.today Crawling
deadanonymousno cardMrequest-rate
| Free tier | no 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 |
|---|---|
| Price | none stated |
| Per-object cap | not applicable: the unit is a capture |
| Retention | captures are kept indefinitely, which is the service's purpose |
| Egress | not applicable: it answers HTML |
| Identity | anonymous no account was asked for |
| Limits |
an unpublished allowance is worse than a small one: there is no threshold to design against |
| Binding | request-rate |
| Interface | rest an HTML route, /newest/<url>; no JSON API |
| Tooling | none published |
| Composes with | Nothing chains to it: the only programmatic route answers a challenge |
| Reliability | 429 with a 59,077-byte challenge page on the first followed request |
| Notes | The 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 rung | measured no page read |
| Checked | 2026-10-22 (live); stale on 2026-12-21 |
Evidence (3)
| date | source | what it proved |
|---|---|---|
| 2026-10-22 | archive.ph/newest/https://example.com | 302 to https://archive.ph/20351231145959/http://example.com/, a timestamp in 2035, so the redirect names no real capture |
| 2026-10-22 | archive.ph/newest/https://example.com | 429 with 59,077 bytes when the redirect was followed |
| 2026-10-22 | archive.today/ | 301 with a zero byte body |