Skip to content
Good for Bots

35 browser-local developer tools for JSON, JWTs, certificates, text diffs and data conversion

Click badge to copy

Changed your site? Run a new scan.

Claim to rescan

Claiming is free. Verify ownership to request a rescan after deploying your changes.

Unclaimed listings are checked automatically every 90 days.

Good for Bots report

DevSexy scores 81 of 100: the whole readable base, 31 of the 50 agent-layer points, no penalties.

Earned

The whole readable base above the line, 31 of the 50 agent-layer points below it.

81

3 prompts away

Copy them below ↓

18

Still open

Behind the checks below, with prompts in Pro.

1
Penalties0
How scoring works · current methodology →

Through a bot’s eyes

“DevSexy is a free website offering 35 developer tools for JSON, JWTs, certificates, text and data, which the site says run locally in the browser without an account or upload.”

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

The homepage text covers a set of developer tasks: validating and formatting JSON, decoding JWTs, comparing text, converting timestamps, inspecting URLs and certificates, and working with YAML, TOML, cURL, regular expressions, hashes and mobile build artifacts. It states that the tools run locally in the browser, that no uploads occur, that no account is needed, and that all 35 tools are free without a paywall. The Mac app is offered as a download with keyboard shortcuts. Each tool is named with a short description. The llms.txt file, which was provided in truncated form, adds a site map with core pages, a Mac app changelog and a description for each tool, with more detail on parser behaviour and on keeping inputs off a server. The JSON-LD blocks add five FAQ questions with answers and a list of tools by name and URL. Together they repeat the homepage facts and add detail on each tool.

What stays hidden

A model reading this input cannot tell who operates DevSexy or how to contact it, since the organization data gives only a name and a URL. It also cannot find out what the Mac app costs, or whether it is free in the same way as the browser tools. The input does not name the browsers or platforms the online tools support, and it does not say how the 35 tools were selected or how often they change.

What is DevSexy?

DevSexy is a website that offers 35 developer tools for working with JSON, JWTs, certificates, text, code and data. The homepage says the tools run locally in the browser, that inputs are not uploaded, and that no account is required.

Read more →

It describes the tools as free, with no paywall for the browser tools. The site is aimed at developers. Its homepage presents task-based entry points such as validating JSON, comparing configuration text, converting Unix timestamps, inspecting URL query parameters and decoding JWTs. It also offers a macOS app for repeated offline work, which is available as a download from the homepage.

3 prompts, 18 points

For Claude Code, Cursor or Codex. The score moves after the next scan.

+10score from 81 to 91

Serve Markdown when asked for it

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

Read prompt

+5score from 91 to 96

State a position on AI crawlers

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

Read prompt

+2.5score from 96 to 99

Declare AI usage preferences

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

Read prompt

Pro

12 more prompts in Pro

Pro shows a prompt for every fix and drafts your llms.txt and robots.txt. It never changes the score.

$9 once, per listingSee Pro

Deployed your fixes? Rescan to update your score →

Ready-made files

Pro drafts these for this site.

Pro

A ready-made llms.txt and robots.txt

Pro drafts both files for DevSexy from its scan, keeps only links and rules our parsers can verify, and hands them over ready to review and publish. It never changes the score.

See Pro

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

Readable base

50 / 50

Passes.

3.3 of 3.3 points.

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

Passes.

8.3 of 8.3 points.

Sitemap declared in robots.txt, listing 129 URLs.

Passes.

8.3 of 8.3 points.

All 4 pages read pass. The homepage describes itself to machines as FAQPage, Question, Answer in valid schema.org JSON-LD.

Passes.

10 of 10 points.

All 4 pages read pass. The homepage marks its content root, its heading outline and its landmarks.

Passes.

8.3 of 8.3 points.

7 of 7 assessed homepage navigation links expose usable destinations.

Passes.

4.2 of 4.2 points.

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

Passes.

2.5 of 2.5 points.

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

Passes.

2.5 of 2.5 points.

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

Passes.

1.7 of 1.7 points.

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

Agent layer

31.3 / 50

Passes.

11.3 of 11.3 points.

/llms.txt is well formed: 41 links across 3 sections.

Passes.

7.5 of 7.5 points.

/llms.txt is descriptive: a summary plus descriptions on 100% of links.

Passes.

12.5 of 12.5 points.

/llms-full.txt serves the site's content as markdown (19 KB).

Fails.

0 of 10 points.

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

Fails.

0 of 5 points.

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

Fails.

0 of 2.5 points.

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

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.

Passes.

Penalty: 0 of 25 points.

The captured homepage HTML contains 748 content words; completeness is not assessed.

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 345 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.

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://devsexy.com/

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://devsexy.com/

    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://devsexy.com/

    https://devsexy.com/robots.txt

    User-agent: *

    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.

In its category

9th of 57 in Developer Tools & APIs

  1. 1Good for Botsgoodforbots.com
  2. 2ProxyJamproxyjam.com
  3. 9DevSexy · this reportdevsexy.com

The prompts above would take DevSexy to 99, 2nd in its category.

To the prompts ↑

Category average 63. The percentile appears once the catalogue holds a few hundred sites.

Scanned

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.

Scan details

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

Scanned
8 Nov 2026
Rubric
0.9.0
Requests
23
Fetched
734.8 KB
Took
55 s
Homepage
345 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
  • /changelogcollection · linked from the homepage · from the sitemap · read
  • /applinked from the homepage · from the sitemap · read
  • /tools/curl-http-message-studiolinked from the homepage · from the sitemap · read