URL Shortener Block/Allow Lists #8996
-
|
If I were to use the URL Shortener Blocklist (to block legitimate and maliciously used domains) but at the same time run the Allowlist (to allow "legitimate" domains) - would it then mean that just the maliciously used domains in the Blocklist would remain blocked and the rest allowed? I presume the difference in domains in the Allowlist is because it doesn't include the ones used for malicious purposes? I see 10046 domains in the Blocklist and 9826 domains in the Allowlist - which i suppose means 220 domains are classed as malicious...?? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 5 replies
-
|
We've discussed this topic here before, but I can't find it. The URL shortener blacklist is checked against SecrueDNS (Cloudflare, Quad9, DNS4EU, Umbrella etc.), and flagged shorteners do not end up on the URL shortener allowlist, but rather on the TIF. Therefore, using the blacklist and allowlist simultaneously does not make sense. The blacklist is intended for use when unblocking the shorteners that you need yourself. |
Beta Was this translation helpful? Give feedback.
-
|
Out of curiosity, I compared the URL Shortener Blocklist vs Allowlist domains and data-matched between them. There's 218 domains on the Blocklist that do not appear on the Allowlist - all good so far. I took those 218 domains and compared it with domains in the TIF, and only 37 of the 218 domains also appear in the TIF, and 181 do not appear in the TIF - is this intentional or an oversight? Domains that do appear in TIF: 00m.in^ Domains that do not appear in TIF: 0987.win^ |
Beta Was this translation helpful? Give feedback.
-
|
That's definitely a bug, I'll have to take a look at it. |
Beta Was this translation helpful? Give feedback.
-
|
This should be fixed in the next release. Outdated data was processed. Currently, there are 94 domains that are not on the allow list and should end up on the TIF. |
Beta Was this translation helpful? Give feedback.
-
|
Will that mean that the difference between the blocklist, allowlist and TIF will now even out? I counted 181 domains not appearing in TIF that were on the blocklist but not the allowlist. |
Beta Was this translation helpful? Give feedback.
-
|
Currently, there are 94 shorteners blocked by Quad9. That is my reference. I had the entire blacklist checked. So the difference is 94 domains, as already mentioned. The whole allowlist is more or less pointless to me, which is why it's not linked in the readme. I would never use it. Someone wanted it, now it's just creating work. |
Beta Was this translation helpful? Give feedback.
-
|
Via build system: |
Beta Was this translation helpful? Give feedback.
We've discussed this topic here before, but I can't find it.
The URL shortener blacklist is checked against SecrueDNS (Cloudflare, Quad9, DNS4EU, Umbrella etc.), and flagged shorteners do not end up on the URL shortener allowlist, but rather on the TIF.
Therefore, using the blacklist and allowlist simultaneously does not make sense. The blacklist is intended for use when unblocking the shorteners that you need yourself.