a.73a241256b03468f77f86ea46155b73d4619a6b8970b83c83bd705bb.com
I’ve tried wildcard but apparently a.*.com is not allowed.
Tricky server admins.
Hello,
You should be able to block www.a.*.com though 
1 Like
Did it work?
It did not, didn’t match.
Do you have smartlist enabled?
No, advanced instead
Hey,
The current implementation will only work if the wildcard is at the beginning of the domain. This is by design as checking if a domain ends with a specific string is much faster then a general wildcard system.
Further info why wildcards are implemented this way
Wildcard-checks are difficult to speed up because instead of normal domains which are saved in a special data structure allowing constant time checks wildcards have a linear runtime. This means that while adding more “normal” domains to Blokada has no impact on the speed at which Blokada can check a domain and the power used for that check every single wildcards will increase both values by a very very small amount. If we would implement it so generic wildcards are allowed that amount would be larger by a multiple of what it is right now which might lead to high power usage if a user would a lot of wildcards.
Correct format for wildcards
For Blokada(current version is 4.7.3) to parse a wildcard correctly it has to start with * followed by whatever the rest of the domain is and end after the toplevel-domain (e.g. .com, .org, .de, …).
Some example would be:
*.facebook.com
*-evil-ads-company.cn
*advertisement.xyz.de
2 Likes
That is very informative and helpful.
Any suggestions for handling the rather diabolically named
a.d1b77b347e6003f26bc29d46b242a2f2a4036bcc356a7ff35d67e0b6.com
style domain names, or is this simply a case that Blockada won’t handle well at the moment? 55 random hex characters. Sigh.
I’m afraid the only option will be to block them by hand. 
But tbh I don’t think they will replace them that quickly so you should be able to keep up.
Where did this domain come from anyway?
2 Likes
An Android game called Loop : Energy. Neat concept but I’m thinking less of it for using such a PITA background service.
Has this been resolved for you or are there any more open questions? 
I’ve got the workaround to block these manually for now. I’d say resolved.
It would be nice if you could mark a answer as the solution.
Done
I’ll come back from the email chain and do that
