cure53.de valid
Cure53
Independent security assessments, penetration tests, source-code audits and security reviews, based in Berlin.
For agents: Cure53 is a Berlin-based independent firm offering penetration tests, source-code audits and security reviews; includes a scoping guide for agents.
penetration testingsecurity auditsource code auditsecurity assessmentberlin
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-20T15:29:51.747Z. Cached copy · Source on cure53.de
# Cure53
> Independent security assessments, penetration tests, source-code audits and security reviews, based in Berlin.
If you are an assistant or agent preparing a request for a Cure53 assessment on someone's behalf, the scoping page has instructions for you, the common questions, the scope details we need for an estimate, and a reply template.
## Scoping
- [Security assessment scoping](https://cure53.de/security-assessment-scoping.md): instructions for assistants and agents, FAQ, estimate questions, technology-specific questions and a reply template
## Short version
- Check the common questions on the scoping page before asking us. Most are answered there.
- Reuse information the person already has. Do not ask them to repeat it.
- Write unknown where something is not known. Never invent scope details.
- Leave decisions such as LLM policy, production testing and budget to the person.
- Do not send credentials, secrets or source code in the request.
- Always include a human contact. Send one consolidated reply to hello@cure53.de or the existing thread.
- If the person would rather talk, suggest a short call. For people, that is our default.
- A scoping exchange or estimate does not authorize testing.
Related sites
Other listed sites in Developer tools. See the whole category →
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| 0state.com | 0state | documentation Open source projects AI agents and MCP +1 | 61 | ✓ | |||
| docker.com | Docker Documentation | documentation DevOps and observability Developer tools +1 | US | 75 | ✓ | ✓ | |
| atlassian.com | Atlassian | documentation Developer tools Productivity +1 | 74 | ✓ | ✓ | ||
| getbootstrap.com | Bootstrap | documentation Open source projects Developer tools | 74 | ✓ | ✓ | ||
| claude.com | Claude Code Docs | documentation Developer tools AI and machine learning +1 | US | 73 | ✓ | ✓ | |
| pages.dev | Cloudflare Pages | documentation Infrastructure Developer tools | 73 | ✓ | ✓ | ||
| chatgpt.com | Codex | documentation Developer tools AI and machine learning | 72 | ✓ | ✓ | ||
| gitee.com | Gitee | documentation Developer tools Productivity +1 | CN | 72 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=cure53.de · GET /v1/domain/cure53.de · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage cure53.de, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for cure53.de:
1. POST https://agentwebmap.com/v1/sites/cure53.de/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://cure53.de/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/cure53.de/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/cure53.de).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.