[DBIP] 25 dead links from a full listings/specific-networks link census: fleet-wide dead Blockscout /api-docs class + 11 adjudicated leftovers (evidence tables)

[tianzhicdev]

DBIP: 25 dead links found in listings/specific-networks/ by a full link census — 13 non-dupe URLs (15 cells) left to fix, incl. a fleet-wide dead /api-docs path class on Blockscout instances

What is broken

I ran a link-health census over every CSV in listings/specific-networks/
(973 files, 1,766 unique URLs; 59 overlap my earlier offers/all-networks
census) at origin/main 1a9c075a, probing each URL HEAD
then GET following redirects (system CA store, Mozilla/5.0 UA; JSON-RPC-style
paths additionally POST-probed so RPC endpoints aren't false-killed).

DEAD (both methods 404/410) = 25 unique URLs / 138 cells. Each was
adjudicated against the provider's own site before filing anything here.

The systematic class: Blockscout /api-docs on the instance domain

https://<instance>/api-docs is the pre-rewrite Blockscout UI path. Current
Blockscout UIs 404 it fleet-wide (measured on 5 independent instances:
base.blockscout.com, gnosis-chiado.blockscout.com, soneium.blockscout.com,
explorer.mode.network, eth.blockscout.com, zksync.blockscout.com — all 404
HEAD+GET). The provider's own live API-docs home is
https://docs.blockscout.com/devs/apis (200, title "Blockscout APIs -
Blockscout", contains instance-URL API examples).

Dead cells of this class (6 URLs, 6 rows):

file	row	dead link
base/explorers.csv:5	blockscout-mainnet	https://base.blockscout.com/api-docs
gnosis/explorers.csv:3	blockscout-testnet	https://gnosis-chiado.blockscout.com/api-docs
mode/explorers.csv:2	blockscout-mainnet	https://explorer.mode.network/api-docs
soneium/explorers.csv:2	blockscout-mainnet	https://soneium.blockscout.com/api-docs
scroll/explorers.csv:3	blockscout-mainnet	https://scroll.blockscout.com/api-docs
katana/explorers.csv:2	blockscout-mainnet	https://explorer.katanarpc.com/api-docs

(scroll.blockscout.com additionally 302s to scrollscan.com — that whole row may
be stale-as-listing, separate call, flagging not fixing here.)
(katana: explorer.katanarpc.com's page bytes contain no Blockscout marker —
software unverified, so the docs.blockscout.com repoint is NOT proposed for it.)

PR incoming (refs this issue, addresses 4 of the 15 left-to-fix cells) repoints the 4 rows on instances I verified
run Blockscout (base, gnosis-chiado, mode, soneium) to
https://docs.blockscout.com/devs/apis.

The other DEAD cells, adjudicated (left alone or owned elsewhere)

dead URL	cells	verdict
https://arbitrum.lava.build + https://arbitrums.lava.build	arbitrum/apis.csv:229-230	provider says GONE: POST returns 410 {"error":"This endpoint has been discontinued.","message":"... visit https://gateway.lavanet.xyz"} (gateway.lavanet.xyz now redirects to /login = public endpoints retired). Rows are removal candidates, BUT open PR #3266 rewrites these exact rows (column-drop DBIP) → dropped from my PR per no-dupe; removal belongs after #3266 lands or in it.
https://docs.arbitrum.io/sdk	arbitrum/services.csv:15	moved; open PR #3246 already repoints this exact cell → not touched.
https://www.blockdaemon.com/protocols/aptos	aptos/apis.csv:38-39	marketing page moved (provider alive: /protocols 200, docs.blockdaemon.com/docs/aptos 200); sitemap has NO aptos product page → no published replacement to repoint to; row left (dead-link ≠ dead provider, per prior triage in #3334 discussion).
https://docs.chainbase.com/platform/features/api/chain-rpc	polygon/apis.csv:77-78	docs site migrated (root 302s to /getting-started/welcome); llms.txt has no chain-rpc feature page found → no invented replacement; left.
https://faucets.chain.link/blast-sepolia	blast/faucets.csv:2	index 200, no blast link in index → faucet discontinued; candidate removal, but blast/faucets.csv is inside #3246's blast edits? no — #3246 touches blast/sdks+apis, not faucets. Still: single-row removal with no replacement source = maintainer call, filing here not PR'ing.
https://web3.okx.com/explorer/soneium	soneium/explorers.csv:3	OKX x-to-the-moon explorer path gone (404 incl. oklink/soneium 404); OKX explorer network list (client-side) unverifiable from this host → no replacement invented; left, flag for human check.
https://www.launchcaster.xyz/p/65b67aca2cccdd9d36e48a9c	optimism/faucets.csv:5	launchcaster.xyz root 200 (farcaster tool), specific /p/ page 404; no canonical replacement page → left.
docs.metamask.io/services/reference/{arbitrum,avalanche-c-chain,base}	3 URLs (rest trailing-slash variants)	already mine: open PRs #3335-#3338.

Method notes

• 403/429 responses (bot-walls, rate limits) were NOT counted as dead; 62
  verify-by-hand + 47 ratelimited URLs sit outside this issue.
• JSON-RPC-style URLs got the POST-envelope probe first (a POST-only RPC 404s
  to HEAD/GET and would be a false-kill).

Evidence, probe dumps and per-URL row locations are in the incoming PR body.