REQUEST: add wildcards support to websites whitelist

[hexaae]

Please add wildcards support (*, ?, etc...) to website whitelist to be able to exclude from wrong detection entire domains like *.abcd.com

[don_dolarson]

I am also contributing to the request

[jayman1000]

I second this. It's about time this feature gets implemented.

[exile360]

Greetings,

The request has been submitted once again to the Product team for consideration.

If any of you have any further requests or suggestions please let us know.

Thanks

[iHearU]

I vote for this feature as well, expecially since your system has decided to block a primary domain that is a DynDNS provider, and I use sub-subdomains to manage access to different things

For example:

You have dyndnsprovider.com blocked (which in and of itself, I don't have a major issue with, as I do realize that bad actors use these types of services to phish)

My subdomain:
mysubdomain.dydnsprovider.com (as an example, has a current IP of 1.2.3.4) which is the only thing that actually gets set, which means all subdomains of this are effectively the same IP as my primary subdomain

My subdomains off that:
sub1.mysubdomain.dydnsprovider.com IP address gets resolved by the DynDNS providers DNS server as the same IP as my primary subdomain.
sub2.mysubdomain.dydnsprovider.com IP address also gets resolved by the DynDNS providers DNS server as the same IP as my primary subdomain.

Right now, in order to unblock it, I would have to set each subdomain as a standalone exclusion rule in Nebula, which is just absurd. There is no justifiable reason to not allow wildcards.

[hexaae]

This is getting VERY ANNOYING. I have encountered a number of subdomains blocked by MwB with different names e.g. this1.domain.com, this2.domain.com etc. and I can't exclude random numbering one by one by hand.
A *.domain.com wildcard would be much more useful.

PLEASE ADD THIS FEATURE ASAP

[Porthos]

6 hours ago, hexaae said:

I have encountered a number of subdomains blocked by MwB with different names e.g. this1.domain.com, this2.domain.com etc. and I can't exclude random numbering one by one by hand.

You should submit those to research so the can be tested and whitelisted if it is warranted. https://forums.malwarebytes.com/forum/123-website-blocking/

 

[AdvancedSetup]

100% agree with @Porthos

We do not want to block any sites that should not be blocked. I've been using the product since before we even blocked websites and I have visited thousands of websites over that time and I've submitted several myself that were not bad. They were unblocked the same day. That way the block is removed for all users.

I do not have a single exclusion, or allow in my list period. Again, if it's a false positive we don't want the block either.

 

[hexaae]

I believe that if a request has been made by many users it should be implemented, or at least consider a survey...
Really, this is the only big disappointment with MalwareBytes I have (beside a slow UI ;)) and is something all other anti-malware solutions already have.

[AdvancedSetup]

The feedback has already been logged.

Thank you for your feedback