From f79a2eb09752d29e4d11da5161fa18fe9a64e5cb Mon Sep 17 00:00:00 2001
From: Alexey <247128645+axkurcom@users.noreply.github.com>
Date: Thu, 22 Jan 2026 01:26:36 +0300
Subject: [PATCH] Update README.md

---
 README.md | 14 ++++++++++----
 1 file changed, 10 insertions(+), 4 deletions(-)

diff --git a/README.md b/README.md
index ec3379a..c5c6ae8 100644
--- a/README.md
+++ b/README.md
@@ -248,10 +248,16 @@ enabled = true
 
 ## FAQ
 ### Recognizability for DPI and crawler
-Since version 1.1, we have debugged masking perfectly, for all clients without "presenting" a key, 
-we transparently direct traffic to the target host. 
-- We consider this a breakthrough aspect, which few people managed to achieve in perfect form.
-- Based on this: if configured correctly, **TLS mode is completely identical to real-life handshake + communication** with a specified host:
+Since version 1.1.0.0, we have debugged masking perfectly: for all clients without "presenting" a key, 
+we transparently direct traffic to the target host!
+
+- We consider this a breakthrough aspect, which has no stable analogues today
+- Based on this: if `telemt` configured correctly, **TLS mode is completely identical to real-life handshake + communication** with a specified host
+- Here is our evidence:
+  - 212.220.88.77 - "dummy" host, running `telemt`
+  - `petrovich.ru` - `tls` + `masking` host
+  - client that "presents" secret-key accesses the MTProxy resource
+  - client that does not "presents" secret-key gets transparent access to the specified resource:
 ```bash
 root@debian:~/telemt# curl -v -I --resolve petrovich.ru:443:212.220.88.77 https://petrovich.ru/
 * Added petrovich.ru:443:212.220.88.77 to DNS cache