Live check

IP Address & Network Checker for AI Services

Locate region
  1. Parse IP
  2. Locate region
  3. Match ASN
  4. Check proxy / VPN / Tor
  5. Check risk lists
  6. Summarize AI access

Result

Current exit IPCheckingCollecting network profile…
EvidenceChecking

Evidence will appear after the exit check finishes.

AI Availability

Live check on this network
Checking
Checking
Checking
Checking
Checking

AI routing exits

Identifies the public exits used by AI apps and vendor networks.
Checking
Identifying AI service exits

Supported endpoints are being checked without replacing the existing connectivity result.

View complete AI routing results

Results reflect the public exit returned by an app or vendor network endpoint for this connection. They do not represent account, subscription, or product availability.

How to read this check

Understand the Current AI Network Environment

The home check combines public exits, network profile, routing attributes, risk signals, and AI service status in one result. Start here, then open a focused tool when a signal needs review.

What the check includes

  • Separate available IPv4 and IPv6 exits
  • IP region, ASN, network type, and region consistency
  • Regional AI support references and live browser connectivity

How to use the result

Confirm the public exit first, then review network and routing attributes, and finally combine risk notices with AI service status. Do not rely on one label or score alone.

ipforai Network Check

On a server, over SSH, or when verifying proxy/split routing, use the read-only command-line check with either curl -fsSL https://ipforai.cc/sh | sh or curl -fsSL https://ipforai.cc/sh | bash. Both run the same script. It does not write local config, install software, or require an API key.

Safer flow: curl -fsSL https://ipforai.cc/sh -o /tmp/ipforai-check.sh && less /tmp/ipforai-check.sh && sh /tmp/ipforai-check.sh; replace sh with bash if preferred. Connectivity and routing probe endpoints are maintained in the script and may differ from browser checks. Results describe the network only, not account status.

The Developer JSON accepts one optional GET parameter, ip: curl -sS 'https://ipforai.cc/json' profiles the request exit, curl -4 -sS 'https://ipforai.cc/json' or curl -6 -sS 'https://ipforai.cc/json' forces one address family, and curl -sS 'https://ipforai.cc/json?ip=8.8.8.8' looks up a specified IP. It is a server-side exit profile, not local system or browser inspection.

What it cannot prove

A network result cannot replace account login, subscription, or service-side risk decisions. For a manually entered IP, AI status is mainly a regional reference rather than a live browser test.

Frequently asked questions

What does the environment score measure?

The environment score combines observable network attributes, region consistency, and public risk signals for the current exit. It does not read account, subscription, or service-side risk state and cannot predict that an AI service will definitely work or fail.

Why should IPv4 and IPv6 be checked separately?

A dual-stack network can use different exits, ASNs, regions, or proxy paths for IPv4 and IPv6. Checking only one address family can miss the path an AI service actually uses.

Does a data-center, proxy, or risk signal mean an account will be restricted?

No. These labels describe observable properties of the current network. Account outcomes can also depend on sign-in, behavior, subscription, organization policy, regional eligibility, and service-side rules.

How is a manual IP lookup different from checking the current network?

A manual lookup analyzes public network attributes and regional references for the entered IP. It cannot replace live browser connectivity checks. For active troubleshooting, use the automatically detected IPv4 and IPv6 exits together with live service results.

How do I run ipforai Network Check?

Official entry: https://ipforai.cc/sh. Use curl -fsSL https://ipforai.cc/sh | sh or curl -fsSL https://ipforai.cc/sh | bash; both run the same script. Prefer review first: curl -fsSL https://ipforai.cc/sh -o /tmp/ipforai-check.sh, open it with less, then run it. Read-only; it requests profile and probe data from this site’s APIs. Not an account verdict.

How can I safely share a result with an AI assistant?

Use the redacted diagnostic summary and share only the network type, region, ASN, routing, risk signals, and score boundary needed for troubleshooting. The summary hides the full IP by default; never add account credentials, verification codes, cookies, or other sensitive data.