dolaai.pro
AI agent that edits Unreal Engine 5.7 Blueprints, C++ and levels in the open editor

Checks Chrome extensions against LinkedIn's detection list, with code teardowns of outreach tools
Safe Outreach is a website that checks whether a Chrome extension appears on LinkedIn's Active Extension Detection (AED) list, a set of 4,934 extension IDs that the input says is embedded in LinkedIn's frontend code as of its November 2026 snapshot. Visitors can type an extension's name or Chrome Web Store URL to see whether it is listed. The site also publishes code teardowns of LinkedIn automation, scraping and outreach extensions, covering where each tool sends a user's LinkedIn session: to a vendor's cloud or stays in the browser. The input says the publisher has read the code of 100+ tools. The homepage refers to people who worry about LinkedIn restrictions, though it does not state pricing or a formal audience.
“Safe Outreach is a site that checks whether a Chrome extension is on LinkedIn's Active Extension Detection list and publishes code-level teardowns of LinkedIn automation and outreach extensions, including where each sends a user's LinkedIn session.”
Simulated from the response GoodForBotsBot received on , not a live answer from any AI assistant.
The homepage text covers LinkedIn's AED list and its 4,934 entries, the checker, a set of popular LinkedIn automation extensions with user counts and detection status, the difference between local-scrape and cookie-bridge session handling, data-flow diagrams for individual tools, LinkedIn search-volume figures, and a list of teardowns. The text is attributed to Safe Outreach and dated November 7, 2026. The Markdown version repeats this content with front matter that adds publication and modification dates and a canonical URL. The llms.txt file gives a short summary of the site and a list of key pages, including a line for each extension covering AED listing and where the session goes. The JSON-LD adds the site name, description, organisation logo and a search action for checking a tool name. Together these give a model the same subject matter as the homepage in more structured form, without pricing or contact details.
A model reading this input cannot find what the checker or the teardowns cost, or whether they are free. The input gives only the publisher name Safe Outreach, with no contact address or named author. The homepage shows only a sample of tool verdicts, so it cannot tell whether a given extension is covered. The methodology and the reasoning behind each verdict are only summarised, and they sit on linked pages that were not read.
Good for Bots report
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 158 URLs.
Describes itself to machines with schema.org JSON-LD. All 4 pages read pass. The homepage describes itself to machines as WebPage, Organization, ImageObject 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. 15 of 15 assessed homepage navigation links expose usable destinations.
Links and buttons have accessible names. 610 of 610 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. 613 of 613 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. Both pages read pass. The page at /best-linkedin-automation-tools has 65 section links, and every one reaches an element on the page.
llms.txt is present and well formed. /llms.txt is well formed: 278 links across 4 sections.
llms.txt is descriptive, not a bare link list. /llms.txt is partly descriptive: only 43% of links carry a description. 115 of 120 descriptions follow the link with something other than ":", the separator the format specifies (`- [name](url): notes`). +3.8 with its prompt.
Serves markdown at its own URL. llms.txt points at 278 markdown versions of pages.
Serves markdown when asked for it. All 4 pages read pass. The homepage serves markdown on `Accept: text/markdown`.
Declares AI usage preferences. Declares AI usage preferences via Content-Signal (robots.txt): ai-train, ai-input, search.
Advertises machine-readable resources with typed links. All 4 pages read pass. The homepage points at a markdown version of itself through a Link header.
States a position on AI crawlers. robots.txt states AI usage preferences, but names no AI crawler individually. +5 with its prompt.
Earned
The whole readable base above the line, 41 of the 50 agent-layer points below it.
2 prompts away
For the owner of safe-outreach.com
They are in the owner view, ready to paste into Claude Code, Cursor or Codex, beside the badge and rescans.
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 158 URLs.
8.3 of 8.3 points.
All 4 pages read pass. The homepage describes itself to machines as WebPage, Organization, ImageObject 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.
610 of 610 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.
613 of 613 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.
Both pages read pass. The page at /best-linkedin-automation-tools has 65 section links, and every one reaches an element on the page.
Agent layer
41.3 / 50
11.3 of 11.3 points.
/llms.txt is well formed: 278 links across 4 sections.
3.8 of 7.5 points.
/llms.txt is partly descriptive: only 43% of links carry a description. 115 of 120 descriptions follow the link with something other than ":", the separator the format specifies (`- [name](url): notes`).
12.5 of 12.5 points.
llms.txt points at 278 markdown versions of pages.
10 of 10 points.
All 4 pages read pass. The homepage serves markdown on `Accept: text/markdown`.
0 of 5 points.
robots.txt states AI usage preferences, but names no AI crawler individually.
2.5 of 2.5 points.
Declares AI usage preferences via Content-Signal (robots.txt): ai-train, ai-input, search.
1.3 of 1.3 points.
All 4 pages read pass. The homepage points at a markdown version of itself through a Link header.
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 2606 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 49 ms.
Agent capabilities
3 of 11 · no points
Each one found adds +1 to the badge.
+1 on the badge.
Publishes an API catalog describing 1 API.
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.
+1 on the badge.
Publishes an A2A Agent Card at /.well-known/agent-card.json, with 1 A2A interface; the card departs from the A2A specification in 1 place.
+1 on the badge.
Publishes an Agent Skills index with 1 usable entry. Skill artifacts and digests were not verified.
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.
It decides which conditional checks apply. “Not established” means no proof in what we read, not proof of absence.
Access & usage policy
GoodForBotsBot received HTTP 200 via a direct request. No indexing restriction was observed in the supported homepage directives.
Sampled URL: https://safe-outreach.com/
No matching refusal for this URL was found for the listed identities.
Declared allow · Scan admission
The recorded robots admission decision allowed our crawler to proceed.
GoodForBotsBot admission along the homepage request chain
https://safe-outreach.com/
Declared allow · robots.txt
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://safe-outreach.com/
https://safe-outreach.com/robots.txt
User-agent: * allow: /
robots.txt is present and validStates a position on AI crawlersAllows search and user-fetch crawlers
GoodForBotsBot received HTTP 200 via a direct request.
Observed · Direct request
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://safe-outreach.com
HTTP 200
Observed · Final homepage response
GoodForBotsBot received HTTP 200 via a direct request.
homepage response
https://safe-outreach.com/
HTTP 200 Transport: direct
Serves the homepage over HTTPS with HTTP 200Serves our crawler without a challenge
No indexing restriction was observed in the supported homepage directives.
Not observed · Homepage directives
No indexing restriction was observed in the supported homepage directives.
homepage response
https://safe-outreach.com/
No snippet restriction was observed in the supported homepage directives.
Not observed · Homepage directives
No snippet restriction was observed in the supported homepage directives.
homepage response
https://safe-outreach.com/
A preference allowing this use applies to at least one listed identity.
Unstated · AIPREF Content-Usage
No applicable AIPREF preference was established for this purpose.
Purpose: search; applicable robots group/path and this response's header
https://safe-outreach.com/
Declared allow · Content-Signal
The applicable crawler group declares these Content Signals. They are separate from permission to fetch and from AIPREF.
Purpose: search; applicable crawler group for https://safe-outreach.com/
https://safe-outreach.com/robots.txt
Content-Signal: search=yes, ai-input=yes, ai-train=yes
A preference allowing this use applies to at least one listed identity.
Unstated · AIPREF Content-Usage
No applicable AIPREF preference was established for this purpose.
Purpose: ai-use; applicable robots group/path and this response's header
https://safe-outreach.com/
Declared allow · Content-Signal
The applicable crawler group declares these Content Signals. They are separate from permission to fetch and from AIPREF.
Purpose: ai-use; applicable crawler group for https://safe-outreach.com/
https://safe-outreach.com/robots.txt
Content-Signal: search=yes, ai-input=yes, ai-train=yes
A preference allowing this use applies to at least one listed identity.
Unstated · AIPREF Content-Usage
No applicable AIPREF preference was established for this purpose.
Purpose: train-ai; applicable robots group/path and this response's header
https://safe-outreach.com/
Declared allow · Content-Signal
The applicable crawler group declares these Content Signals. They are separate from permission to fetch and from AIPREF.
Purpose: train-ai; applicable crawler group for https://safe-outreach.com/
https://safe-outreach.com/robots.txt
Content-Signal: search=yes, ai-input=yes, ai-train=yes
In its category
Category average 69. The percentile appears once the catalogue holds a few hundred sites.
Every scan is kept. Pro draws the history as a chart →
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.
More like Safe Outreach:Research & ReferenceSalesSecurity & Privacy
dolaai.pro
AI agent that edits Unreal Engine 5.7 Blueprints, C++ and levels in the open editor
saascubes.com
Curated SaaS directory offering permanent do-follow backlinks for modern software products
Also Excellent
goodforbots.com
Evaluates website readability for AI crawlers and language models with a scoring rubric
Also Excellent
contentspilot.com
AI co-pilot that plans, drafts and schedules Instagram carousels and posts in brand style
Also Excellent
brivoy.com
Community site where makers launch new products and early adopters discover them
vouchgeo.com
Tracks how AI assistants mention a brand across multi-question buying conversations
Do you run safe-outreach.com? Open the owner view → Removing the listing is free. Remove →