llm-txt.ru Agent Ready Scan bronze

llm-txt.ru

“Russian-first AI readiness audit service with llms.txt, markdown, discovery, MCP, and protocol checks.

a2a https://llm-txt.ru/scan/ talk to it https://llm-txt.ru/.well-known/agent.json its card

✓ 🇷🇺 RU · JSC IOT ✓ Checked 3d ago “ notifications, streaming

✓ we checked this   “ the operator says this

Verified by agenttru.st

Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.

Certificate

Issued by Let's Encrypt domain-validated

Valid until 9 Jan 2027 as of our check on 11 Nov 2026.

Control of the hostname was checked; nothing about who operates it.

Key ECDSA P-256, signed ECDSA-SHA384, issued via YE1 under ISRG Root X2 — classical, as every publicly trusted certificate is today.

Names on this certificate (1)

llm-txt.ru.

Connection

TLS 1.3 · X25519MLKEM768 — post-quantum hybrid key exchange, agreed with our checker on 11 Nov 2026. What this means

DANE / TLSA

Not verified (TLSA query returned RCodeNameError)

Discovery

Well-known document

AI use policy

Search: yesAI input: yesAI training: no

What this site's robots.txt says about how AI may use its content. Recorded as the operator wrote it, not enforced — these are preferences about use, not access, and agenttru.st only reads the agent's own discovery documents.

AI-facing documents

Publishes a Web Bot Auth key directory (1 key, ES256) — the operator publishes keys so their agent's signed requests can be verified. agenttru.st recorded that the directory exists; it has not verified a signature.

Fetched from this host during verification. Neither document is how this agent was discovered.

First seen

21 Oct 2026

What this agent says it can do

Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks — the operator of llm-txt.ru controls every word below.

Technical agent card

Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.

Protocol

a2a

Version

2.0.0

Card completeness

a2a.proto v1.0 requires eight top-level fields. This card omits:

supportedInterfaces

Missing fields do not affect listing — they describe how much the operator has published, not whether the agent was verified.

Operate this agent and would rather not be listed? Request removal.