Urgent.News

What's breaking now, across thousands of outlets.

Tech

Get one Wayback Machine snapshot per year of any website with one curl (CDX API, no key)

Disclosure: I built the Apify Actor linked at the end and charge per result. The raw endpoints below are free and need no key. Want to see how a site evolved, or build a yearly timeline of a page? The Internet Archive's CDX server can collapse captures by timestamp prefix. One successful capture per year curl -s…

One method for capturing a single Wayback Machine snapshot for any given website involves using the CDX API with a single curl command. This process does not require an API key and provides a free way to retrieve historical snapshots of a website. The raw endpoints for this method are available without any cost.

To obtain a yearly snapshot, the command curl -s "https://web.archive.org/cdx/search/cdx?url=example.com&output=json&fl=timestamp,statuscode&collapse=timestamp:4&filter=statuscode:200&limit=4" can be executed. This command collapses the results by a timestamp prefix, keeping one row for each distinct year. The first four characters of the timestamp represent the year.

For instance, in the results dated 2026-11-01, the first four timestamp characters were 20020120142510, 20030207055228, 20040105045515, and 20050101025054. Each of these timestamps can be opened at the corresponding URL, such as https://web.archive.org/web/20020120142510/example.com, to view the website's snapshot from that particular year.

To get the most recent capture, the command curl -s "https://web.archive.org/cdx/search/cdx?url=example.com&output=json&fl=timestamp&limit=-1" can be used. A limit of -1 returns the last rows instead of the first. As of 2026-11-01, this command returned the timestamp 20261101041731.

Some considerations to keep in mind include the format of the timestamps, which are in the format YYYYMMDDhhmmss in UTC. Using collapse=timestamp:6 will give monthly snapshots, while collapse=timestamp:8 will provide daily snapshots. Heavy domain-wide queries may result in time-outs, so it is advisable to narrow down the queries and manage rate limits accordingly.

For those who prefer not to script the process, an Apify Actor called Wayback Snapshots CDX has been created. This tool charges per result on a pay-per-use basis and does not require a subscription. The Actor can be accessed at https://apify.com/northgrid-data/wayback-snapshots-cdx. Feedback and issues can be submitted through the Actor's issue tracker.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

I scanned my own sites for security issues. Here’s the checklist I wish I’d had.

I've been building a website scanner as a side project, and the first thing I did was point it at my own sites. It was humbling. None of the problems were exotic.

  • Implement security headers like HSTS, CSP, and X-Content-Type-Options.
  • Fix mixed content by ensuring all resources load over HTTPS.
  • Remove exposed files like /.git/ and .env/ to prevent data leaks.

Rounding is a promise when you show a player their odds

Development covered 23 Sep 2026 to 24 Sep 2026 (commit dates). A player in Myriad Immortal Sect read "Tribulation success chance: 100.0%", pressed the button, and failed.

  • Odds rounded towards uncertainty to avoid false promises
  • Consistent odds display across game panels and cards
  • Bonuses capped at 100% to prevent confusion

VS Code remembers the commands you hid with a space

VS Code's Run Recent Command list, in a new window on my laptop. Note the space before export . The token's a fake. The top four were typed on a different machine.

  • VS Code saves hidden commands in its own list, separate from shell history
  • List stored in SQLite file in user folder, persists across sessions
  • Commands also saved in terminal scrollback history, unaffected by clear command

When Pay-Per-GB Proxy Pricing Stops Making Sense

High-volume data collection creates a simple but expensive pricing problem: when a crawler transfers more data, a pay-per-GB bill rises at exactly the same time.

  • Pay-per-GB pricing correlates with data transferred (cost = GB × price per GB)
  • Throughput-based, unmetered access offers fixed speed and duration billing
  • Break-even point calculated as fixed plan price ÷ pay-per-GB rate

More from Sunday 1 November →