Forwarded from Telegram Info English (Sominemo)
The .me registry has blocked the t.me domain
Telegram users worldwide have encountered an outage: short t.me links have stopped opening in regular browsers. The problem affects users in the entire world.
At the same time, within the mobile and desktop Telegram clients themselves, clicks on links are processed correctly, and redirects work without any problems. As a temporary alternative for posting on external resources, you can use telegram.me links.
Technical details
At the moment, the exact causes of the incident remain unknown.
According to WHOIS data, the t.me domain has been completely removed from the DNS zone by the administration of the .me domain registry.
This status is set not by the registrar (GoDaddy), but directly by the main operator of the domain zone — the Montenegrin company doMEn d.o.o., which manages the entire
#outages #bans
Telegram users worldwide have encountered an outage: short t.me links have stopped opening in regular browsers. The problem affects users in the entire world.
At the same time, within the mobile and desktop Telegram clients themselves, clicks on links are processed correctly, and redirects work without any problems. As a temporary alternative for posting on external resources, you can use telegram.me links.
Technical details
At the moment, the exact causes of the incident remain unknown.
According to WHOIS data, the t.me domain has been completely removed from the DNS zone by the administration of the .me domain registry.
This status is set not by the registrar (GoDaddy), but directly by the main operator of the domain zone — the Montenegrin company doMEn d.o.o., which manages the entire
.me zone. This organization is a joint venture of Identity Digital, GoDaddy, and ME-net.#outages #bans
🤯45😱4❤3🤡2🕊1
Forwarded from Telegram Info English (Sominemo)
The t.me Domain Has Been Restored by the .me Registry
Checks by the @tginfo editors show that the .me zone's main server has returned the DNS records for the t.me domain.
Since DNS records are cached at the level of various DNS services and providers, it may take up to 24 hours for service to be restored on users' devices.
#outages #bans
Checks by the @tginfo editors show that the .me zone's main server has returned the DNS records for the t.me domain.
Since DNS records are cached at the level of various DNS services and providers, it may take up to 24 hours for service to be restored on users' devices.
#outages #bans
⚡23👍1
Forwarded from Telegram Info English (Sominemo)
The .me registry commented on the suspension of the t.me domain
A representative of the .me domain zone administration commented on Twitter about the situation regarding the ban of the t.me domain, which belongs to Telegram:
The .me zone is allocated to the government of Montenegro, but on its behalf, the infrastructure is managed by a joint venture between Identity Digital, GoDaddy, and the local company ME-net.
#outages #bans
A representative of the .me domain zone administration commented on Twitter about the situation regarding the ban of the t.me domain, which belongs to Telegram:
The .ME Registry works closely with law enforcement to monitor and mitigate issues across the .ME domain in accordance with applicable laws, including sanctions requirements.As a reminder, on July 13, the .me registry disabled the DNS records for the t.me domain without any public statements from the zone administration or Telegram. On July 14, Identity Digital support explained the ban as compliance with OFAC requirements, and a link to a Telegram channel was found in the service's sanctions lists, which the messenger soon deleted, after which the domain was restored.
On 13 July, First VPN Service (1VPNS) was included as a sanctioned entity by the U.S. Department of the Treasury. A Telegram channel using the t.me domain was among 1VPNS identified infrastructure. Accordingly, the t.me domain was suspended.
On 14 July, Telegram provided confirmation that it had removed its links and affiliations with 1VPNS. Once the confirmation was reviewed and verified, the suspension was removed from the t.me domain.
We appreciate Telegram’s prompt cooperation in resolving this matter.
The .me zone is allocated to the government of Montenegro, but on its behalf, the infrastructure is managed by a joint venture between Identity Digital, GoDaddy, and the local company ME-net.
#outages #bans
🤡24❤2
Forwarded from Telegram Info English (Sominemo)
Telegram Is Working on Experimental WEB-Proxy
A new experimental proxy type titled “WEB” was found in Telegram Desktop's code. The discovery was publicized by teleLakel.
The server code for the WEB-proxy is still under development, and Telegram hasn't endorsed any implementations yet, so there is no good way to try the technology at the moment.
Why is this necessary, and why not just use MTProxy?
The already existing MTProxy can also mask to appear as HTTPS traffic using the FakeTLS extension. However, modern Deep Packet Inspection systems (DPI) can already tell such connections apart, since FakeTLS still has some differences from real HTTPS traffic that can be seen from the outside.
The new WEB transport makes detection much harder: to talk to the server, the messenger uses the built-in browser (WebView). It establishes a real TLS/HTTPS connection using standard browser cryptography, which makes Telegram traffic less different from regular web surfing.
The independent Telemt community is working on detection-resistant protocols. Earlier, thanks to the community's research into Russian DPIs, Telegram developers updated the MTProxy in their clients to adapt them to new detection methods.
The community notes that the messenger should spend more time developing new censorship-resistance methods. If the messenger doesn't keep improving the new WEB proxy, it might stop working in the future — typical Telegram traffic may have uniquely identifying properties even inside a real TLS connection if additional masking methods are not used on it.
#Desktop #proxy #bans
A new experimental proxy type titled “WEB” was found in Telegram Desktop's code. The discovery was publicized by teleLakel.
The server code for the WEB-proxy is still under development, and Telegram hasn't endorsed any implementations yet, so there is no good way to try the technology at the moment.
Why is this necessary, and why not just use MTProxy?
The already existing MTProxy can also mask to appear as HTTPS traffic using the FakeTLS extension. However, modern Deep Packet Inspection systems (DPI) can already tell such connections apart, since FakeTLS still has some differences from real HTTPS traffic that can be seen from the outside.
The new WEB transport makes detection much harder: to talk to the server, the messenger uses the built-in browser (WebView). It establishes a real TLS/HTTPS connection using standard browser cryptography, which makes Telegram traffic less different from regular web surfing.
How does it work
• The messenger opens a special page on the proxy server domain using a hidden browser
• This domain can also continue to work as a regular website. The hidden Telegram channel only activates if the request contains the correct secret key.
• Inside the unitary web channel, the encrypted MTProxy traffic is enveloped into WEB-proxy frames and sent to the proxy server. Currently, this is done using WebSocket.
• HTTP/WebSocket traffic is repackaged and relayed to the MTProxy server without being decrypted.
Currently, the feature is under active development, so by the time it gets released, the protocol may change.
The independent Telemt community is working on detection-resistant protocols. Earlier, thanks to the community's research into Russian DPIs, Telegram developers updated the MTProxy in their clients to adapt them to new detection methods.
The community notes that the messenger should spend more time developing new censorship-resistance methods. If the messenger doesn't keep improving the new WEB proxy, it might stop working in the future — typical Telegram traffic may have uniquely identifying properties even inside a real TLS connection if additional masking methods are not used on it.
#Desktop #proxy #bans
❤52🤡9❤🔥1🤔1