grabs.in
A live wall of new sites. New sites show up in certificate-transparency logs minutes after they go up. grabs.in renders each one and puts the picture on the wall as it arrives.
- What it is
- A live screenshot wall, per extension
- The work
- A real-time feed, a rendering pipeline, a page that stays readable at speed, share cards
- Built with
- Node, server-sent events, headless Chrome, sharp, Cloudflare
- Data from
- Certificate transparency logs, our own captures
- Live since
- 2026, redesigned October 2026
- Visit
- grabs.in
Every TLS certificate issued for a new website is published to public logs within minutes. grabs.in watches those logs, renders each new site on a phone-sized screen, and adds the picture to a wall that never stops moving. Open it and you are watching the web get built, one small business at a time: a new clinic, a new school, a coming-soon page, a shop.
Each extension has its own wall: the .in one is the home, .ai, .com, .io and sixty more have theirs, and one shows everything. The page paints the latest captures first, then goes live; a pace control slows the stream so cards stay readable, a stop freezes it, and a filter drawer hides the spam networks that churn out hundreds of look-alike sites.
The work
A feed that fast needs discipline at every step: a server-side filter per extension so a phone never downloads a thousand irrelevant events, a sixty-second cache for the opening grid, a suppression list for operators we have flagged, and a render pipeline that produces a desktop and a mobile capture for every site without ever skipping one.
In October 2026 the page was rebuilt in our data-tools family and every extension page got its own share card: rendered on the server from the four latest captures with the family’s own typefaces, refreshed every six hours, so a link to grabs.in/ai previews as a strip of real .ai sites from this afternoon.
How it is built
The wall is a single page served by a Node application and fed over server-sent events; the cards are plain HTML the browser inserts as events arrive, which is why it runs on a cheap phone. Share cards are composed with sharp from the capture store. The crawler files, the sitemap of extension pages and the nav are generated from the data rather than typed.