Reverse side locks
The topic of locks and the recently adopted law is already fed up with it. However, after the entry into force of the law (from November 1), some new details appeared.
Earlier in the topics about the Federal Law 139-FZ it was repeatedly mentioned that in order to block a particular page or domain, many providers will need to implement DPI, which will require equipment upgrades. Obviously, blocking a resource by ip-address will result in unavailability of all sites hosted on this server. Actually, the topic is just about that.
On pastebin recently got an xml-file intended for some provider, with a list of blocked resources. One site was mentioned in this file. For many residents of Moscow and the Moscow region, blocking is already in place - in particular, with providers of TTC, Dom.ru, Beeline, Yota and some others. She acts with me.
')
Recalling the predictions about blocking all sites on this IP at once, I decided to check with myself. That's what came of it.
One of these sites is blocked, but there is no access to all. As can be seen from WHOIS , IP belongs to the Ukrainian hosting Mirohost.
As you can see, the expectations regarding the implementation of the law have been partially confirmed. By the way, my provider (Rostelecom) does not display any messages about blocking - the browser simply reports connection timeout. This is also not the positive side of what is happening.
By the way, there are some more details, for example, some providers have blocked another site from this list. A feature of this site is the use of cloud protection (from DDOS and not only) Cloudflare. The site's IP points to one of the Cloudflare servers, it can be changed, only the old IP will remain blocked. And behind Cloudflare there are many sites, and many of them may not be available.
So far, the existing blocks of special discomfort do not deliver (and this is only because they, for the most part, belong to Ukraine), but over time, most likely, it will be necessary to use workarounds.
Earlier in the topics about the Federal Law 139-FZ it was repeatedly mentioned that in order to block a particular page or domain, many providers will need to implement DPI, which will require equipment upgrades. Obviously, blocking a resource by ip-address will result in unavailability of all sites hosted on this server. Actually, the topic is just about that.
On pastebin recently got an xml-file intended for some provider, with a list of blocked resources. One site was mentioned in this file. For many residents of Moscow and the Moscow region, blocking is already in place - in particular, with providers of TTC, Dom.ru, Beeline, Yota and some others. She acts with me.
')
Recalling the predictions about blocking all sites on this IP at once, I decided to check with myself. That's what came of it.
One of these sites is blocked, but there is no access to all. As can be seen from WHOIS , IP belongs to the Ukrainian hosting Mirohost.
As you can see, the expectations regarding the implementation of the law have been partially confirmed. By the way, my provider (Rostelecom) does not display any messages about blocking - the browser simply reports connection timeout. This is also not the positive side of what is happening.
By the way, there are some more details, for example, some providers have blocked another site from this list. A feature of this site is the use of cloud protection (from DDOS and not only) Cloudflare. The site's IP points to one of the Cloudflare servers, it can be changed, only the old IP will remain blocked. And behind Cloudflare there are many sites, and many of them may not be available.
So far, the existing blocks of special discomfort do not deliver (and this is only because they, for the most part, belong to Ukraine), but over time, most likely, it will be necessary to use workarounds.
Source: https://habr.com/ru/post/284790/
All Articles