The Incident Challenge
A bi-weekly production incident challenge. Race the clock, debug like it's real, and climb the leaderboard.
Added May 25, 2026
· Last analysed May 25, 2026 · via 
StackScope records what new websites are built with, the week they launch. Most we find ourselves, by watching public internet infrastructure for brand-new sites; the rest come from Product Hunt, Hacker News and PeerPush. We crawled this one for its tech stack and scored it for launch readiness: DNS, security headers, SEO basics. This page is what we saw on 25 May 2026; the live site may have changed since.
Every technology below links to its own page: which other new sites launched with it. Vendors and agencies watch those pages with Stackdar and hear about new adopters the week they ship, from £15 a month.
The Incident Challenge covers some of the launch checklist, with a thorough launch checklist, fast page loads, and clean crawl signals. Worth fixing first: missing several security headers, incomplete legal pages, and tracking cookies set before any opt-in.
Launched on Product Hunt on May 25, 2026. The site is hosted on AWS S3 and served through AWS CloudFront, with a domain registered 3 weeks before launch. Our crawler found 14 technologies on this site, covering advertising, analytics, seo, and CDN. The stack includes Tailwind CSS, Amazon Web Services, and AWS CloudFront.
It's also running the same core stack as 307 other launches.
If you own this site, refresh the snapshot and see the full fix list any time →
Tech Stack (14) · Scale-up stack
| CDN |
AWS CloudFront
|
| Cloud |
Amazon Web Services
|
| DNS |
AWS Route 53
|
| Hosting |
AWS S3
|
| Protocol | HTTP/3 |
| CSS framework |
Tailwind CSS
|
| Developer tools |
Vite
|
| UI library |
shadcn/ui
|
| Advertising |
Facebook Pixel
(2)
|
Google Ads
(3)
|
|
| Analytics |
Google Analytics
(3)
|
Mixpanel
(4)
|
|
| SEO |
Google Search Console
|
LinkedIn
(2)
|
Infrastructure
Email Security
Storage (15)
| Name | Lifetime | Detected as |
|---|---|---|
| bcookie | 1y | |
| lidc | 1d | |
| li_gc | 6mo | |
| mp_b0830d76990b828c7b1ba204b507aec6_mixpanel | 1y | Mixpanel |
| _fbp | 3mo | Facebook Pixel |
| _ga | 1y | Google Analytics |
| _ga_C0NXHZJ3D8 | 1y | Google Analytics |
| _gcl_au | 3mo | Google Ads |
| Key | Size | Detected as |
|---|---|---|
| lastExternalReferrer | 5 B | - |
| lastExternalReferrerTime | 13 B | - |
| _gcl_ls | 152 B | Google Ads |
| __mpq_b0830d76990b828c7b1ba204b507aec6_ev | 711 B | Mixpanel |
| Key | Size | Detected as |
|---|---|---|
| mp_gen_new_tab_id_mixpanel_b0830d76990b828c7b1ba204b507aec6 | 1 B | Mixpanel |
| mp_tab_id_mixpanel_b0830d76990b828c7b1ba204b507aec6 | 41 B | Mixpanel |
| Database | Version | Detected as |
|---|---|---|
| mixpanelBrowserDb | 1 | Mixpanel |
Readiness Breakdown How?
Vibe Score Breakdown How?
| Signal | Points |
|---|---|
| AI palette signals | +5 |
This score is based on structural patterns and is not definitive. Many legitimate sites may trigger signals, and AI-built sites may go undetected. It should be treated as an indicator, not a verdict.