Skip to content
Good for Bots

Public IP query and risk detection tool with command line support

Good for Bots: Poor, 40 of 100Get this badge →

On your homepage, it turns this report’s link to ping123.app dofollow.

Scanned

What is ping123.app?

Ping123 is a web-based utility tool that displays the public IP address of the visitor and performs network-related lookups. Based on the page title and meta description provided in the input, the service is designed to check geolocation, internet service providers, ASN data, native IP status, and risk metrics such as proxies, VPNs, Tor, blacklists, and access permissions for various external platforms. The interface shows dynamic loading states for location, querying, and STUN services, alongside command-line usage examples for obtaining plain text IP responses, JSON data, and request headers.

Through a bot’s eyes

“Ping123 is an IP lookup and risk detection tool that shows public IP addresses and offers command-line access for IP data, JSON output, and request headers.”

Simulated from the response GoodForBotsBot received on , not a live answer from any AI assistant.

What it can read, and what stays hidden →

What a bot can read

A language model reading this input learns that the site is an IP lookup and risk detection utility. The text covers the display of a public IP address, geographic location indicators via mapping services, STUN service checks, DNS resolution exit checks, and domestic or international site testing indicators. The homepage provides concrete examples of curl commands to interact with the service programmatically via plain text, JSON endpoints, and request header inspections. However, the descriptive text detailing specific risk checks mentioned in the meta description, such as VPN, proxy, blacklist, or specific platform access risks, is not explicitly present in the body content of the markdown input. Pricing, specific target user definitions, and contact details are entirely absent from the provided text.

What stays hidden

The input does not state pricing details, specific documentation for all supported risk checks, terms of service, or background information about the creators or operators of the tool.

Good for Bots report

ping123.app scores 40 of 100: 40 of the 50 base points, none of the agent layer, no penalties.

Earned

40 of the 50 base points above the line, none of the agent layer below it.

40

Still open

Behind the checks below, with prompts in Pro.

26
Penalties0
How scoring works · current methodology →

For the owner of ping123.app

3 prompts, 34 points

They are in the owner view, ready to paste into Claude Code, Cursor or Codex, beside the badge and rescans.

Open the owner view →

Select a check to see what we found and how it is graded.

Readable base

39.8 / 50

Passes.

4.1 of 4.1 points.

robots.txt is valid, with 1 user-agent group.

Passes.

10.2 of 10.2 points.

Sitemap declared in robots.txt, listing at least 200 URLs.

Fails.

0 of 10.2 points.

None of the 4 pages read pass. The homepage publishes no structured data at all: no JSON-LD, no microdata, no RDFa.

Passes.

12.2 of 12.2 points.

3 of 4 pages read pass; 1 partly. The homepage is partly structured: No <h1>, so nothing says what the page is about.

Not applicable.

0 of 0 points.

No applicable navigation links were observed in the homepage HTML.

Passes.

5.1 of 5.1 points.

11 of 11 assessed homepage links and buttons have a nonempty accessible name.

Passes.

3.1 of 3.1 points.

1 of 1 assessed homepage form fields meet the static naming and field-semantics checks.

Passes.

3.1 of 3.1 points.

13 of 13 assessed homepage controls and role declarations meet the static role, state and relationship checks.

Passes.

2 of 2 points.

All 4 pages read pass. The homepage declares itself as its canonical URL.

Agent layer

0 / 50

Fails.

0 of 11.3 points.

No /llms.txt on this site.

Fails.

0 of 7.5 points.

No usable /llms.txt to judge.

Prompt in Pro →
Fails.

0 of 12.5 points.

No /llms-full.txt and no markdown versions linked from llms.txt.

Fails.

0 of 10 points.

None of the 4 pages read pass. Asking the homepage for markdown still returns text/html.

Prompt in Pro →
Fails.

0 of 5 points.

robots.txt names no AI crawlers, so every operator has to guess.

Prompt in Pro →
Fails.

0 of 2.5 points.

No usage declaration found in robots.txt or the final successful homepage response header.

Prompt in Pro →

Penalties

− 0

Passes.

Penalty: 0 of 15 points.

Our crawler reaches the page without being challenged.

Passes.

Penalty: 0 of 20 points.

Nothing on the homepage tells a crawler to skip it or to withhold its snippet.

Not applicable.

Penalty: 0 of 0 points.

The homepage contains text or potentially meaningful elements; JavaScript dependence is not established.

Passes.

Penalty: 0 of 25 points.

robots.txt allows every known search and user-fetch crawler to reach the homepage.

Passes.

Penalty: 0 of 10 points.

The homepage is served over HTTPS and returns HTTP 200.

Passes.

Penalty: 0 of 3 points.

The homepage provides both a non-empty title and meta description.

Passes.

Penalty: 0 of 3 points.

The homepage is reached in 0 redirects.

Passes.

Penalty: 0 of 3 points.

The homepage reached a plain crawler in 53 ms.

Agent capabilities

0 of 11 · no points

Each one found adds +1 to the badge.

Not applicable.

Adds +1 to the badge when found.

No API catalog published.

Not applicable.

Adds +1 to the badge when found.

No /auth.md published.

Not applicable.

Adds +1 to the badge when found.

No AI Catalog published, so no MCP server card can be discovered.

Not applicable.

Adds +1 to the badge when found.

No A2A Agent Card at /.well-known/agent-card.json, and none listed in an AI Catalog.

Not applicable.

Adds +1 to the badge when found.

No usable Agent Skills index was found at either well-known path or in the AI Catalog.

Not applicable.

Adds +1 to the badge when found.

No WebMCP declarations were found in the collected HTML or inline scripts. External scripts were not inspected.

Not applicable.

Adds +1 to the badge when found.

No Web Bot Auth key directory at /.well-known/http-message-signatures-directory.

Not applicable.

Adds +1 to the badge when found.

No HTTP 402 payment challenge on the homepage or robots.txt, and no manifest at /.well-known/x402.

Not applicable.

Adds +1 to the badge when found.

No ACP discovery declaration established at /.well-known/acp.json.

Not applicable.

Adds +1 to the badge when found.

No UCP discovery declaration established at /.well-known/ucp.

Not applicable.

Adds +1 to the badge when found.

No public AMP discovery declaration established. Private or hidden agents may not advertise one to our crawler.

Site profile

Login
Not established
API
Not established
Commerce
Not established

It decides which conditional checks apply. “Not established” means no proof in what we read, not proof of absence.

Access & usage policy

Who can read this page, and for what purpose?

GoodForBotsBot received HTTP 200 via a direct request. No indexing restriction was observed in the supported homepage directives.

Sampled URL: https://ping123.app/

Declared crawling rules

No matching refusal for this URL was found for the listed identities.

Sources and scope: declared crawling rules
  • Declared allow · Scan admission

    • GoodForBotsBot/1.0 (+https://goodforbots.com/bot)

    The recorded robots admission decision allowed our crawler to proceed.

    GoodForBotsBot admission along the homepage request chain

    https://ping123.app/

    robots.txt is present and valid

  • Declared allow · robots.txt

    • goodforbotsbot (Site diagnostics)
    • * (Default robots group)
    • oai-searchbot (ai-search)
    • claude-searchbot (ai-search)
    • perplexitybot (ai-search)
    • mistralai-index (ai-search)
    • kimi-searchbot (ai-search)
    • amzn-searchbot (ai-search)
    • meta-webindexer (ai-search)
    • exasearchbot (ai-search)
    • aiwebindex (ai-search)
    • duckassistbot (ai-search)
    • shapbot (ai-search)
    • yandexadditional (ai-search)
    • yandexadditionalbot (ai-search)
    • gptbot (ai-training)
    • claudebot (ai-training)
    • mistralai-training (ai-training)
    • kimibot (ai-training)
    • ai2bot (Unknown)
    • applebot-extended (ai-training)
    • webzio-extended (ai-training)
    • chatgpt-user (user-fetch)
    • claude-user (user-fetch)
    • perplexity-user (user-fetch)
    • mistralai-user (user-fetch)
    • kimi-user (user-fetch)
    • amzn-user (user-fetch)
    • diffbot-user (user-fetch)
    • firecrawlagent (extraction)
    • webzio (extraction)
    • meta-externalfetcher (user-fetch, agent)
    • google-extended (ai-training, grounding)
    • meta-externalagent (ai-training, product-improvement)
    • amazonbot (ai-training, product-improvement)
    • ccbot (open-dataset, ai-training)
    • googlebot (search)
    • bingbot (search)

    No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.

    Acquisition of https://ping123.app/

    https://ping123.app/robots.txt

    User-agent: *
    allow: /

    robots.txt is present and validStates a position on AI crawlersAllows search and user-fetch crawlers

Observed access

GoodForBotsBot received HTTP 200 via a direct request.

Sources and scope: observed access
Coverage and interpretation
  • Crawler coverage includes the registered identities and up to 50 user-agent entries from robots.txt. Source excerpts and detail groups are bounded; omissions are labelled.
  • Observed access describes GoodForBotsBot only. Other crawler entries describe declared rules, not tests of those operators' access.
  • Coverage is the sampled homepage response and collected robots.txt files. No indexing or citation is guaranteed. Usage preferences are declarations, not a legal determination of permission.
  • This explanation adds no points or penalties. Any score effects belong to the linked checks.
  • AIPREF and Content Signals keep their own definitions. AIPREF search can include processing used exclusively for search; training preferences are not a blanket ruling on every search process.

Scan details

Every scan is kept. Pro draws the history as a chart →

Scanned
27 Oct 2026
Rubric
0.9.0
Requests
23
Fetched
194.5 KB
Took
12.5 s
Homepage
53 ms · direct
Pages read
4
robots.txt
allowed
Which pages the scan read

The homepage and up to three pages from the sitemap and homepage links. Structured data, page structure, Markdown negotiation and typed links check each page read and take the median page; other checks read the homepage.

  • Homepagealways read
  • /guides/ai-platform-riskarticle · from the sitemap · read
  • /guides/collection · from the sitemap · read
  • /aboutabout · from the sitemap · read

interviewace.online

Real-time AI answer suggestions for job candidates during live video interviews

submityourstartup.now

Free weekly launch directory where early-stage founders list startups and are ranked by votes

talhabashir.com

Free online calculators and tools for US taxes, mortgages, business and personal finance

volanea.com

Transactional email, campaigns, and automation API with AI agent support

vouchgeo.com

Tracks how AI assistants mention a brand across multi-question buying conversations

Do you run ping123.app? Open the owner view → Removing the listing is free. Remove →