Feature request: Add support for wildcard trusting to 3-rd level domain

[izh1979]

Currently it is possible to add ...example.com to the trusted list to trust to all subdomains like foo.example.com. However, in some cases, the domains hierarchy is deeper. One example is CDN services, which are often named like server-123.company-subdomain.some-cdn.com.

Another example is the Microsoft websites, which are using dozens of subdomains with lot of telemetry and unnecessary scripts. I don't want to allow entire *.microsoft.com as well as *.office.com. But I would like to allow, e.g., *.teams.microsoft.com.

So, my suggestion, is displaying 3rd-level wildcard option alongside with 2nd-level. For example,

...microsoft.com
...teams.microsoft.com

P.S. I've tried to add manually ...teams.microsoft.com to Per-site Permissions in the settings, but UI doesn't allow to do it (nor with triple dots, nor with dedicated Unicode character, nor with *.something).

[jtotht]

Have you tried NoScript Options → Appearance → List full addresses in the permissions popup (https://www.noscript.net)? It’s not exactly what you asked for, but close: it allows you to configure each subdomain individually, i.e. teams.microsoft.com, example.teams.microsoft.com and www.teams.microsoft.com are three different configuration entries; but so are teams.microsoft.com and login.microsoft.com as well, so it may be good enough for you.

[izh1979]

Yes, I've tried it. (Moreover, I've enabled this feature since long ago.) But it doesn't help with the sites, where you have, e.g., lot of CDN hosts like cdn-45.cdn.example.com alongside with lot of tracking and ad subdomains like ad.example.com. So, you cannot allow only only *.cdn.example.com with just one click without allowing ad.example.com too.