How to verify domain ownership in one minute and independently audit Streebog-256 receipts
While Step-1 express checks read only public homepage metadata without setup, Step-2 deep domain inspection confirms administrative authority via a standard verification token identical to search-console ownership proofs. Generate or download the token file in one click below, follow the three-step placement guide, and verify any GOST R 34.11-2012 audit receipt.
indra-verify.txt for a domain on the left, or paste any audit receipt JSON below to recompute its 256-bit RFC 6986 digest and test tamper rejection.Inspect Raw JSON API Response & Ledger Entry
{}DNS / Records / Add record, choose type TXT, set Name: _indra-verify, paste indra-site-verification=... into Content, and click Save.TXT record on host _indra-verify with TTL 300, paste the issued verification string, and apply changes./var/www/site/.well-known/indra-verify.txt with zero Nginx reload required.1. Three-step domain ownership authorization and ledger verification flow
Cryptographic proof of administrative authority prior to Step-2 inspection, paired with independent GOST R 34.11-2012 (Streebog-256) hash recomputation.
2. Step-by-step token placement for Cloudflare, reg.ru, and Nginx
Confirming domain control creates an auditable record that the security check was initiated by an authorized administrator under computer-misuse compliance standards. Neither placement option alters application code, TLS certificates, or live user traffic, and either method can be completed in under sixty seconds.
In DNS control panels such as Cloudflare, Route 53, or reg.ru, open the zone editor, add a new TXT record with host name _indra-verify, paste the issued indra-site-verification=... string into the value field with a short TTL, and save. Because the verifier queries public authoritative resolvers directly over UDP and TCP, propagation typically finishes within seconds.
When DNS administration belongs to a separate department, click the download button to save indra-verify.txt and place it inside the static webroot directory at /.well-known/indra-verify.txt so that HTTPS returns status HTTP 200 with the token line. Each daily HMAC token remains valid across a forty-eight-hour UTC grace window.
3. Independent mathematical verification without trusting the platform
Every express and authorized check writes an append-only record hashed under GOST R 34.11-2012 (RFC 6986). Modifying even a single digit inside the summary object changes the recomputed 256-bit digest and triggers an immediate tamper verdict; offline air-gapped ledger packages (iss-ledger-117) and enterprise pilots are provided via isslab.ru.
4. Engineering reference notes for verifier TOOL-GST-06
Safety and lawfulness of publishing indra-verify.txt or _indra-verify
The token is a read-only public string containing zero secrets or executable code, using the exact same ownership-proof mechanism employed by certificate authorities and search-engine webmaster consoles.
Offline verification of a Streebog-256 receipt without calling this website
Download the open Apache-2.0 package iss-ledger-117 from the Open Packages page and run iss_verifier.py locally on any machine with Python 3.10 or newer.
Enterprise pilot packages and air-gapped delivery
Perimeter posture, transport security & localization
Streebog-256 verification passport.Air-gapped interface verification (indra-core)
OpenAPI schemas and an isolated staging container as input, delivering a thirty-class paired decoy assessment with zero false positives, compiled mcp-sentinel contracts, and a full ledger passport.Autonomous agent runtime gate (MITR)
mcp.json manifests and tool schemas as input, delivering compiled satisfiability policies and pre-socket parameter enforcement.Request the offline kit or schedule a pilot
--no-index --find-links) and standalone verifier scripts are provided for isolated laboratory testing and enterprise pilot evaluations. Submit a work email below without page reload or write directly to af@isslab.ai.
Institutional developer and platform operator
OGRN 1267700083617, INN 9731161602, KPP 773101001, 18 Davydkovskaya Street, Suite VIII, Moscow, 121352). Under the Security 3.0 research and engineering program, the institute develops and operates the MITR runtime action gateway and the INDRA verification stand, publishes the monograph Proven Action, and maintains open Apache-2.0 software packages with zero outside subcontractors.