Internet Panic Index Scan a site
Public dependency scan + live incidents

See what could break your site before it does.

Enter a domain. We inspect its public homepage, identify visible third-party services and check whether any matched provider is reporting trouble.

Free. No account. Public homepage data only.

No code to install Source-backed incidents Limits shown clearly
Outside-in fragility snapshot Public surface

What is holding this site up?

The first scan looks for hosting clues, CDNs, payment scripts, analytics, support tools and other browser-visible dependencies.

01 / LIVE CONTROL SIGNAL

What major platforms report right now.

The public index stays free. It is the control signal we use to correlate a site's visible providers with named, official incidents—not the product we ask teams to buy.

Read the transparent formula
Internet panic level Checking now
—/ 100
Collecting signal

Checking official sources

The first live pulse will appear shortly.

—affected
—operational
—data coverage
Last 24 hoursWaiting for first check
Score = reach-weighted share of tracked services reporting trouble. See the formula.
NOWConnecting to official status pages…Live
02 / LIVE INCIDENTS

What’s causing trouble

Only unresolved incidents reported by the vendors themselves. No rumor mill and no mystery sentiment model.

Checking all official sources…
03 / STATUS SOURCES

The public control group

OperationalDegradedUnknown
04 / THE COMPOUNDING ADVANTAGE

The code is easy. The memory is valuable.

Every useful scan should improve a historical map of how the public web depends on a small set of providers.

⌁

Discover

Find visible infrastructure and browser-loaded services without asking a team to document its stack first.

↗

Correlate

Match discovered providers with named incidents and show the evidence without claiming certainty we do not have.

◎

Remember

Track dependency drift and concentration over time. That history cannot be generated retroactively in a weekend.

05 / VALIDATION PRICING

The scan is live.
The monitoring plans earn their way in.

We will charge only after the beta demonstrates a useful recurring signal.

SnapshotAvailable now
$0

Inspect one public homepage and compare visible providers with current incidents.

  • Visible third-party hosts
  • Recognized provider evidence
  • Matched live status
  • Explicit scan limitations
Scan a site
FOUNDING BETA
Monitored SiteNo charge today
$19/ month at launch

For small internet businesses that want an outside-in record without another observability suite.

  • Scheduled dependency rescans
  • Dependency drift alerts
  • Matched provider incidents
  • Monthly resilience record
Scan first, then reserve
PortfolioDesign partners
$79/ month at launch

For agencies and operators responsible for several public websites.

  • Up to 25 sites
  • Portfolio change feed
  • Client-ready evidence
  • Exportable monthly record
Scan a client site
06 / QUESTIONS

No artificial certainty

Does a detected provider mean it can take down the entire site?

No. Detection proves only that the public homepage exposed a relationship or hosting clue. The scan does not silently infer criticality, redundancy or server-side architecture.

Can the scan see private APIs and authenticated flows?

No. The first version examines public homepage HTML and response headers without executing JavaScript. Private and server-side dependencies remain invisible until a future verified integration is explicitly authorized.

Why keep the public panic index?

It is a free control signal, an acquisition surface and a transparent incident source. The paid value is the evolving dependency record for a specific site or portfolio.

Is monitoring available today?

Not yet. The free snapshot is live. Monitoring prices are proposed founding prices; joining the beta does not create a subscription or charge a card.