What's the simplest way to block a Top-Level-Domain (*.ru/* for example )in web protection?

I know this works in UTM hoping XG

https?://[A-Za-z0-9.-]*\.ru/

or

http?://[A-Za-z0-9.-]*\.ru/

You can also use country blocking, you may be aware but figure I would mention it.

Badrobot said:

 https?://[A-Za-z0-9.-]*\.ru/

http?://[A-Za-z0-9.-]*\.ru/

If working with this REGEX Snippets, then the pattern for an URL with Path behind should be added as well (for Example mydomain.ru/mypage/index.php wouldnt be affected by this REGEX Snippets above). Afterwards this Regex Snippet can be used to create an URL Group that afterwards can be used in Webfilter Policy.

By the way... Why do you want to block all *.ru pages? not all of those are bad... I don't se a usecase for something like this :-S

Good Point, I have been playing around with it, https://regex101.com/r/UPBMbG/1/tests  has a nice engine for testing if anyone is interested.

Since we are not really trying to block a TLD but a domain suffix I wonder if this would work 

[.](ru)

Have not tested it though.

It does not. It simply won't accept regex entries.

Custom categories and URL Groups do not support RegEx.

See here for more details:

https://community.sophos.com/kb/en-us/127270

I'm not 100% sure but I believe a URL Group just containing "ru" will do it.

FQDN Host objects appear to not like a top level domain.

You should also consider country blocking (uses GeoIP).  Set the Destination Zone to WAN and the Destination Network to Russian Federation.  This will block anything hosted in Russia but not .ru sites that are hosted elsewhere.

Hmm, maybe you nailed it. "ru" is accepted and seems to block "mail.ru" but not "rushlimbaugh.com" so maybe that will do the trick. Thanks!

I would be careful of Country Blocking, all be it some are obvious i.e. you probably do not do anything with Russia or China and most businesses are not going to establish a data hub there with all the malicious hacking going on from either of them.  However you need to know your countries if you are doing this, for example Microsoft has data hubs in Singapore, Germany and many other countries that can cause issues with Office 365.  Many AWS servers are not always native to the US either, anyway good practice but don't just blanket the planet, do a few at a time and check things in the logs to see what is being blocked.

Additionally not all .ru servers are in Russia some are based in the US.

Ian

These points are understood. We simply don't do any legit business requiring access to many TLDs. There are many phishing and Emotet download attempts using 3rd-world country domains, for example.

In our business users have no need to be on sites outside Australia, Japan, NZ, Singapore etc so for them to be going to China, Russia, etc is really a no no.

That said we all understand not all these locations host bad content.

An interesting fact from a recent Webroot report:

Russia only hosts 3% of the bad URLs and China 5%

The really worrying thing is:

Clearly the problem is the northern hemisphere.  In fact, given that 63% are hosted in the US, just block that country.  :)

LOL yeah that will fix it.

It's bad enough using Office 365 and with the "Load Balancing" we get our data hitting servers in HK and China (I am in Melbourne)

Then there is TeamViewer with servers all over Europe

A few exceptions need to be created to my world of blocking everything LOL

LOL yeah that will fix it.

It's bad enough using Office 365 and with the "Load Balancing" we get our data hitting servers in HK and China (I am in Melbourne)

Then there is TeamViewer with servers all over Europe

A few exceptions need to be created to my world of blocking everything LOL