Reverse side of locks

    The subject of locks and the recently adopted law is already fed up. However, after the law came into force (from November 1), some new details appeared.

    Earlier in topics about the Federal Law 139-ФЗ it was repeatedly mentioned that in order to block an individual page or domain, many providers will need to implement DPI, which will require updating the equipment. Obviously, blocking the resource by ip-address will result in the inaccessibility of all sites hosted on this server. Actually, the topic is just about that.

    Pastebin recently got an xml file intended for some provider with a list of blocked resources. This site mentioned one site. For many residents of Moscow and Moscow Region, blocking is already in effect - in particular, for providers of TTK,, Beeline, Yota, and some others. She acts with me.

    Remembering the predictions about blocking all sites on this IP at once, I decided to check it out for myself. Here is what came of it.

    One of these sites is blocked, but there is no access to all. As seen from WHOIS , IP belongs to the Ukrainian hosting Mirohost.

    As you can see, expectations regarding the implementation of the law were partially confirmed. By the way, my provider (Rostelecom) does not display any messages about blocking - the browser simply reports a connection timeout. This is also not a positive side of what is happening.

    By the way, there are a few 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 IP points to one of the Cloudflare servers, it can be changed, only the old IP will remain blocked. And there are many sites behind Cloudflare, and many of them may not be available.

    So far, the existing locks do not cause much discomfort (and this is only because they, for the most part, relate to Ukraine), but over time, most likely, it will be necessary to use workarounds.

    Also popular now: