惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

云风的 BLOG
云风的 BLOG
The GitHub Blog
The GitHub Blog
A
About on SuperTechFans
P
Proofpoint News Feed
G
Google Developers Blog
Stack Overflow Blog
Stack Overflow Blog
IT之家
IT之家
Microsoft Security Blog
Microsoft Security Blog
F
Fortinet All Blogs
人人都是产品经理
人人都是产品经理
博客园 - 叶小钗
C
Check Point Blog
Microsoft Azure Blog
Microsoft Azure Blog
aimingoo的专栏
aimingoo的专栏
月光博客
月光博客
美团技术团队
D
Docker
博客园 - Franky
Y
Y Combinator Blog
大猫的无限游戏
大猫的无限游戏
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
博客园 - 【当耐特】
罗磊的独立博客
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
14% of the Web Is Actually Dead — But Not How You Think (...
Tony Wang · 2026-06-18 · via DEV Community

Tony Wang

Originally published at crawlora.net.

When you hit a dead URL in production, do you know whether the domain is gone — or whether an anti-bot system just blocked your crawler? They look identical from a failed request, but they're completely different failures, and most tools don't tell them apart.

We scanned the DomCop top 10 million domains to find out how much of the popular web is actually dead. The short version: about 14% — not the ~27% you've probably seen quoted.

Dead and blocked are not the same failure

A domain that won't load failed for one of two reasons:

  • It's gone. No DNS record, or nothing accepts a TCP connection. Genuinely dead.
  • It's alive and blocking you. A real server returning a 403 or 429 to anything that looks like a bot.

Most "dead web" studies count both as dead. They shouldn't, because the right response to each is opposite:

  • A dead domain never comes back. Retrying it — rotating proxies, escalating clients — is wasted compute.
  • A blocked domain is live. It needs a different client, not more retries.

The numbers

Probing every domain over HTTP and classifying each as alive / redirect / blocked / dead:

  • 14.1% genuinely dead — overwhelmingly vanished DNS (76% of the dead bucket). The server is gone.
  • 8.9% blocked — live servers returning 403/429 to automated clients.
  • 76.6% alive, 0.3% redirect.

The widely-cited "~27% of the web has rotted" figure conflates blocked-but-live servers (and 404/5xx responses — still a live server answering) with the genuinely gone. Separate them honestly and the truly-dead web is about half what people assume.

Proof: same domains, different client

To show the 8.9% "blocked" really are alive, we re-probed them with a real Chrome TLS/JA3 fingerprint — an HTTP client that speaks Chrome's exact TLS handshake and header order (not a headless browser, no canvas/WebGL).

~72,000 of the blocked domains served content normally. Same URLs, same network — the only thing "dead" was the wall. That dropped the blocked rate from 8.9% to 8.2%.

The takeaway for anyone building crawlers or link-checkers: when a tool reports a dead domain, ~9% of the time it's a live server with anti-bot deployed. NXDOMAIN/REFUSED → dead, skip it. 403/429 → alive, recheck with a real browser TLS context before you mark it dead.

The web rots unevenly

Death rate isn't uniform. By country-code TLD:

  • China's .cn: 33% dead
  • Germany's .de: 7.6% dead

A 4× gap. Institutional TLDs fare badly too — .gov 26%, .edu 22% — matching Pew Research's finding that government and reference pages suffer the worst link rot.

The famous dead

The casualties are all in the data: Grooveshark, Gfycat, del.icio.us, Yahoo Pipes, AddThis, DMOZ, OpenSolaris, GeoCities. Two decades of the social and developer web's graveyard.

The open dataset

Every domain, both probe arms, is open under CC BY 4.0 (one JSON row per domain per arm: domain, tld, rank, mode, outcome, reason, HTTP statuses, redirect hops, parked flag):

(Disclosure: we build a web-scraping API, which is why the dead-vs-blocked distinction bites us daily.)