
DevSexy
devsexy.com35 browser-local developer tools for JSON, JWTs, certificates, text diffs and data conversion
- Scanned
- Category
- Developer Tools & APIs
- Markdown
- Read this report
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. 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.
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 →Show less ↑
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.
Good for Bots report
DevSexy scores 81 of 100: the whole readable base, 31 of the 50 agent-layer points, no penalties.
robots.txt is present and valid. robots.txt is valid, with 1 user-agent group.
Sitemap is present and parses. Sitemap declared in robots.txt, listing 129 URLs.
Describes itself to machines with schema.org JSON-LD. All 4 pages read pass. The homepage describes itself to machines as FAQPage, Question, Answer in valid schema.org JSON-LD.
Content is marked up so a reader can find it. All 4 pages read pass. The homepage marks its content root, its heading outline and its landmarks.
Navigation links expose usable destinations. 7 of 7 assessed homepage navigation links expose usable destinations.
Links and buttons have accessible names. 76 of 76 assessed homepage links and buttons have a nonempty accessible name.
Form fields have names and recognizable semantics. 1 of 1 assessed homepage form fields meet the static naming and field-semantics checks.
Controls expose roles, states and relationships. 79 of 79 assessed homepage controls and role declarations meet the static role, state and relationship checks.
Each page declares one usable canonical URL. All 4 pages read pass. The homepage declares itself as its canonical URL.
Section links reach an element on the page. All 4 pages read pass. The homepage has 1 section link, and every one reaches an element on the page.
llms.txt is present and well formed. /llms.txt is well formed: 41 links across 3 sections.
llms.txt is descriptive, not a bare link list. /llms.txt is descriptive: a summary plus descriptions on 100% of links.
Serves markdown at its own URL. /llms-full.txt serves the site's content as markdown (19 KB).
Serves markdown when asked for it. None of the 4 pages read pass. Asking the homepage for markdown still returns text/html. +10 with its prompt.
States a position on AI crawlers. robots.txt names no AI crawlers, so every operator has to guess. +5 with its prompt.
Declares AI usage preferences. No usage declaration found in robots.txt or the final successful homepage response header. +2.5 with its prompt.
Advertises machine-readable resources with typed links. None of the 4 pages read pass. The homepage's links are all ordinary page furniture; none point an agent anywhere. +1.3 with its prompt in Pro.
Earned
The whole readable base above the line, 31 of the 50 agent-layer points below it.
3 prompts away
Still open
Behind the checks below, with prompts in Pro.
For the owner of devsexy.com
3 prompts, 18 points
They are in the owner view, ready to paste into Claude Code, Cursor or Codex, beside the badge and rescans.
All 36 checks
Evidence for each, in Markdown →Select a check to see what we found and how it is graded.
Readable base
50 / 50
3.3 of 3.3 points.
robots.txt is valid, with 1 user-agent group.
8.3 of 8.3 points.
Sitemap declared in robots.txt, listing 129 URLs.
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.
10 of 10 points.
All 4 pages read pass. The homepage marks its content root, its heading outline and its landmarks.
4.2 of 4.2 points.
76 of 76 assessed homepage links and buttons have a nonempty accessible name.
2.5 of 2.5 points.
1 of 1 assessed homepage form fields meet the static naming and field-semantics checks.
2.5 of 2.5 points.
79 of 79 assessed homepage controls and role declarations meet the static role, state and relationship checks.
1.7 of 1.7 points.
All 4 pages read pass. The homepage declares itself as its canonical URL.
0.8 of 0.8 points.
All 4 pages read pass. The homepage has 1 section link, and every one reaches an element on the page.
Agent layer
31.3 / 50
11.3 of 11.3 points.
/llms.txt is well formed: 41 links across 3 sections.
7.5 of 7.5 points.
/llms.txt is descriptive: a summary plus descriptions on 100% of links.
12.5 of 12.5 points.
/llms-full.txt serves the site's content as markdown (19 KB).
0 of 10 points.
None of the 4 pages read pass. Asking the homepage for markdown still returns text/html.
0 of 5 points.
robots.txt names no AI crawlers, so every operator has to guess.
0 of 2.5 points.
No usage declaration found in robots.txt or the final successful homepage response header.
0 of 1.3 points.
None of the 4 pages read pass. The homepage's links are all ordinary page furniture; none point an agent anywhere.
Penalties
− 0
Penalty: 0 of 15 points.
Our crawler reaches the page without being challenged.
Penalty: 0 of 20 points.
Nothing on the homepage tells a crawler to skip it or to withhold its snippet.
Penalty: 0 of 25 points.
The captured homepage HTML contains 748 content words; completeness is not assessed.
Penalty: 0 of 25 points.
robots.txt allows every known search and user-fetch crawler to reach the homepage.
Penalty: 0 of 10 points.
The homepage is served over HTTPS and returns HTTP 200.
Penalty: 0 of 3 points.
The homepage provides both a non-empty title and meta description.
Penalty: 0 of 3 points.
The homepage is reached in 0 redirects.
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.
Adds +1 to the badge when found.
No API catalog published.
Adds +1 to the badge when found.
No /auth.md published.
Adds +1 to the badge when found.
No AI Catalog published, so no MCP server card can be discovered.
Adds +1 to the badge when found.
No A2A Agent Card at /.well-known/agent-card.json, and none listed in an AI Catalog.
Adds +1 to the badge when found.
No usable Agent Skills index was found at either well-known path or in the AI Catalog.
Adds +1 to the badge when found.
No WebMCP declarations were found in the collected HTML or inline scripts. External scripts were not inspected.
Adds +1 to the badge when found.
No Web Bot Auth key directory at /.well-known/http-message-signatures-directory.
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.
Adds +1 to the badge when found.
No ACP discovery declaration established at /.well-known/acp.json.
Adds +1 to the badge when found.
No UCP discovery declaration established at /.well-known/ucp.
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://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/
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
Observed · Direct request
- GoodForBotsBot/1.0 (+https://goodforbots.com/bot)
Our request received HTTP 200. A status alone does not identify a WAF.
Our recorded direct transport attempt; intermediate attempt URLs are not retained
https://devsexy.com
HTTP 200
Observed · Final homepage response
- GoodForBotsBot/1.0 (+https://goodforbots.com/bot)
GoodForBotsBot received HTTP 200 via a direct request.
homepage response
https://devsexy.com/
HTTP 200 Transport: direct
Serves the homepage over HTTPS with HTTP 200Serves our crawler without a challenge
Indexing directives
No indexing restriction was observed in the supported homepage directives.
Sources and scope: indexing directives
Not observed · Homepage directives
No indexing restriction was observed in the supported homepage directives.
homepage response
https://devsexy.com/
Search snippets
No snippet restriction was observed in the supported homepage directives.
Sources and scope: search snippets
Not observed · Homepage directives
No snippet restriction was observed in the supported homepage directives.
homepage response
https://devsexy.com/
Search usage
No applicable preference for this use was established.
Sources and scope: search usage
Unstated · AIPREF Content-Usage
- 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 applicable AIPREF preference was established for this purpose.
Purpose: search; applicable robots group/path and this response's header
https://devsexy.com/
AI input and use
No applicable preference for this use was established.
Sources and scope: ai input and use
Unstated · AIPREF Content-Usage
- 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 applicable AIPREF preference was established for this purpose.
Purpose: ai-use; applicable robots group/path and this response's header
https://devsexy.com/
AI training
No applicable preference for this use was established.
Sources and scope: ai training
Unstated · AIPREF Content-Usage
- 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 applicable AIPREF preference was established for this purpose.
Purpose: train-ai; applicable robots group/path and this response's header
https://devsexy.com/
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
Good for Botsgoodforbots.com - 2
ProxyJamproxyjam.com - 9
DevSexy · this reportdevsexy.com
The prompts in the owner view 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.
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
Do you run devsexy.com? Open the owner view → Removing the listing is free. Remove →