IP Tools
Interface ready · capability pending

Claude Availability Test

Inspect narrow browser and probe-region observations for one server-selected public service fixture.

Method:
Explicit same-origin fixed-manifest job; production capability remains gated
Status:
idle

Input

Claude five-step public path

This isolates the public network path; it does not sign in or evaluate accounts, quotas, or model access.

  1. Check 1

    Region signal

    Not observed

    claude_public_web

  2. Check 2

    DNS resolution

    Not observed

    claude_public_web

  3. Check 3

    TCP connection

    Not observed

    claude_public_web

  4. Check 4

    TLS handshake

    Not observed

    claude_public_web

  5. Check 5

    HTTP entry

    Not observed

    claude_public_web

Fixed service
claude

There are no target or credential fields. The server selects business-targets-v1.

Result

Ready

No assessment has been created.

No aggregate conclusion (unknown)

The service and target IDs are closed. No URL, account, Cookie, API key, subscription, model, title or private risk input is accepted. Evidence does not establish availability.

Tool guide

Clear input, result, and evidence boundaries

Inspect the public DNS, connection, TLS, HTTP, and dual-stack path to fixed Claude web targets.

01

Input and method

No account, cookie, API key, or arbitrary URL input.

02

Reading the result

Browser observations and regional probe stages remain separate so a failed public path can be located without making account claims.

03

Boundary and privacy

Public target manifests, terms, real protocol samples, and authorized tests are not approved yet; the capability remains disabled.

FAQ

Frequently asked questions

What does Claude Availability Test check?

Inspect the public DNS, connection, TLS, HTTP, and dual-stack path to fixed Claude web targets.

What input does Claude Availability Test accept?

No account, cookie, API key, or arbitrary URL input.

How should I interpret Claude Availability Test results?

Browser observations and regional probe stages remain separate so a failed public path can be located without making account claims.

What can Claude Availability Test not prove?

Public target manifests, terms, real protocol samples, and authorized tests are not approved yet; the capability remains disabled.

How does Claude Availability Test handle input and results?

Input is used only for this explicit check. Public target manifests, terms, real protocol samples, and authorized tests are not approved yet; the capability remains disabled.

When should I run Claude Availability Test again?

Run it again after the relevant network, address, browser environment, or target changes. Browser observations and regional probe stages remain separate so a failed public path can be located without making account claims.

Continue checking