IP Tools
Interface ready · capability pending

OpenAI API & Codex Connectivity 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

Separate API and Codex paths

No API key or billable call is used; model access, quota, and real SSE remain outside this check.

  1. Check 1

    API DNS

    Not observed

    openai_unauthenticated_gateway

  2. Check 2

    API TLS

    Not observed

    openai_unauthenticated_gateway

  3. Check 3

    Credential-free HTTP

    Not observed

    openai_unauthenticated_gateway

  4. Check 4

    Codex sign-in

    Not observed

    codex_login_entry

  5. Check 5

    Codex service entry

    Not observed

    codex_login_entry

  6. Check 6

    WebSocket

    Not observed

    codex_websocket_observation

Fixed service
openai_api_codex

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

Check the public API gateway, Codex sign-in, and realtime network paths without an API key.

01

Input and method

No API key, account, model, billing, upload, or arbitrary endpoint input.

02

Reading the result

API DNS, TLS, and unauthenticated HTTP authentication response remain separate from Codex sign-in and WebSocket observations.

03

Boundary and privacy

A 401 can prove only that an authentication layer answered; it does not validate a key, quota, model, billing, SSE, or task execution.

FAQ

Frequently asked questions

What does OpenAI API & Codex Connectivity Test check?

Check the public API gateway, Codex sign-in, and realtime network paths without an API key.

What input does OpenAI API & Codex Connectivity Test accept?

No API key, account, model, billing, upload, or arbitrary endpoint input.

How should I interpret OpenAI API & Codex Connectivity Test results?

API DNS, TLS, and unauthenticated HTTP authentication response remain separate from Codex sign-in and WebSocket observations.

What can OpenAI API & Codex Connectivity Test not prove?

A 401 can prove only that an authentication layer answered; it does not validate a key, quota, model, billing, SSE, or task execution.

How does OpenAI API & Codex Connectivity Test handle input and results?

Input is used only for this explicit check. A 401 can prove only that an authentication layer answered; it does not validate a key, quota, model, billing, SSE, or task execution.

When should I run OpenAI API & Codex Connectivity Test again?

Run it again after the relevant network, address, browser environment, or target changes. API DNS, TLS, and unauthenticated HTTP authentication response remain separate from Codex sign-in and WebSocket observations.

Continue checking