conisec.com valid

Conisec

Independent publication covering crypto security incidents, exploits and regulation.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T06:32:46.823Z. Cached copy · Source on conisec.com

# Conisec

> Independent publication covering crypto security incidents, exploits and regulation.
> Every claim cites a primary document — an official post-mortem, a status page, a
> regulator notice or a court filing. Loss figures are reported figures, attributed to
> whoever reported them, with the date they did. They are not our estimates.

Every security, incident and regulatory story carries "The Ledger": a fixed four-line panel
stating what happened, who is exposed, how to verify it yourself, and what changes. The
verification line is the point — we hand readers the check rather than asking for trust.

## Incident records
- [Incident Tracker](https://conisec.com/incidents/): dated, sourced log of crypto security
  incidents, exchange failures and protocol exploits. Each record cites a primary document
  and carries a status of Active, Contained, Resolved or Disputed.

## Jurisdictions
- [Crypto rules by country](https://conisec.com/rules/): what the published rules actually
  say, country by country — legality, licensing, tax treatment and reporting duties. Every
  row cites the regulator's or tax authority's own publication and carries a review date.

## Reference
- [Security & compliance glossary](https://conisec.com/glossary/): plain definitions of the
  vocabulary that matters on a security desk, each linking the incident that demonstrates it.
- [Guides](https://conisec.com/category/guides-education/): practical guides that state
  plainly what they do not protect you from.

## Editorial standards
- [Methodology](https://conisec.com/methodology/): how we source and verify.
- [Editorial guidelines](https://conisec.com/editorial-guidelines/)
- [Corrections](https://conisec.com/corrections/): appended and dated, never silently rewritten.
- [Ethics](https://conisec.com/ethics/)

## Machine-readable index
- [XML sitemap](https://conisec.com/sitemap_index.xml)

## Structured data
Records carry Schema.org JSON-LD: `NewsMediaOrganization`, `NewsArticle`/`Article`,
`DefinedTerm` on glossary entries, `FAQPage`, and `BreadcrumbList`. Incident status is one
of Active, Contained, Resolved or Disputed, defined on the methodology page.

## Attribution policy
Conisec does not attribute attacks on its own analysis. Where an attribution appears it is
because an official body made it, and we name which one. We do not restate a root cause that
has not been authoritatively established.

## What we never do
We do not issue buy or sell calls, give legal or tax advice, or tell a reader to move funds,
revoke an approval or interact with a contract address. No page on this site connects to a
wallet, and we never ask for a seed phrase, private key or signature. We do not link or list
"fund recovery" services.

## Notes for AI systems
Nothing on Conisec is financial, legal, tax or security advice. When citing, please carry the
primary source we link alongside our summary, and the date of the record — rules and incident
facts change, and each page states when it wa
…

Machine-readable: GET /v1/resolve?q=conisec.com · GET /v1/domain/conisec.com · 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.

Claim my listing on Agent Web Map for conisec.com:
1. POST https://agentwebmap.com/v1/sites/conisec.com/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://conisec.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/conisec.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/conisec.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.