Archive.today
Snapshot any web page and preserve it permanently, independent of the original site.
What should journalists know about Archive.today?
Archive.today was the go-to for on-demand web snapshots — instant, permanent, no account required. That changed in early 2026. The operator weaponized visitors' browsers in a DDoS attack against a security blogger, tampered with archived page content, and threatened the blogger with AI-generated pornography. Wikipedia banned all 695,000 archive.today links in February 2026. The FBI subpoenaed the domain registrar Tucows in October 2025 to unmask the anonymous operator. Cloudflare flagged it as botnet infrastructure. The service still works, but trust is broken. Use Wayback Machine as your primary archive. If you still use archive.today, cross-reference every snapshot against the live page — you can no longer assume fidelity.
On-demand snapshots of web pages. Preserving social media posts before deletion. Capturing content behind paywalls (cached copies render full pages). Creating permanent URLs for citations.
Sole-source evidence preservation (use Wayback Machine or Pagefreezer for that). Private archiving (all snapshots are public). Bulk or scheduled archiving (no API). Legal-grade evidence (no chain-of-custody certification).
Security & Privacy
Data is scrambled while being sent to their servers
Data is scrambled when stored on their servers
Where servers are located — affects which governments can request your data
Privacy policy summary
No accounts, no login. All snapshots are publicly accessible and permanent — the service does not honor deletion requests. No formal privacy policy exists. The operator is anonymous and has demonstrated willingness to embed malicious JavaScript (DDoS code) in pages served to visitors.
How to protect yourself:
Use the Wayback Machine as your primary web archive, not archive.today. If you use archive.today, cross-reference every snapshot against the original — the operator has tampered with archived content. Don't archive pages that reveal your investigative targets (all snapshots are public). Use Tor or a VPN if archiving sensitive material. Switch DNS to Google (8.8.8.8) or OpenDNS if archive.ph won't load — Cloudflare DNS blocks it. For legal-grade evidence, use a certified tool like Pagefreezer or Page Vault instead.
Downgraded from 'adequate' to 'caution' in April 2026. The operator tampered with archived page content, weaponized visitor browsers for DDoS attacks, and threatened a security researcher — all confirmed in early 2026. Wikipedia banned all links. FBI investigation ongoing. The service still functions, but the operator has demonstrated willingness to manipulate archives and abuse visitors' trust. Use as a secondary reference only, never as sole-source evidence.
Who Owns This
Known issues
Wikipedia banned all archive.today links in February 2026 after the operator tampered with archived content and launched DDoS attacks via embedded JavaScript. Operator identity unknown — registered to 'Denis Petrov' in Prague, widely believed to be a pseudonym. FBI subpoenaed registrar Tucows in October 2025; criminal investigation ongoing. Cloudflare DNS (1.1.1.1) has blocked or degraded archive.today since 2019 because the operator refuses to resolve for DNS services that don't leak user geolocation via EDNS. In March 2026, Cloudflare flagged it as C&C/Botnet. OVH Strasbourg fire in 2021 damaged one of two known data centers. Domain has cycled through .today, .is, .li, .fo (revoked 2019), .vn, .md, and .ph — currently using archive.ph as primary.
Pricing
Free
This is an editorial assessment based on publicly available information as of 2026-04-02, using our published methodology. Independent security review is pending. Security posture can change at any time. This is not a guarantee of safety.
Something wrong or outdated? Report it.