spirillen

> We are missing clc.to you should add it to it's own issue, this thread is dead, but `clc.to` is already listed

Sounds more likely, that your edition of [weechat](https://weechat.org/) is a malicious software, as [weechat](https://weechat.org/) do not depend on qq. However you should always connect over the tor network for privacy...

it seems "safe" to only blacklists ``` gscounters.au1.gigya.com gscounters.eu1.gigya.com gscounters.gigya.com gscounters.us1.gigya.com socialize.eu1.gigya.com ``` I'm not sure about, this list is the only one holding these. I blacklist the entire domain...

That issue is very very old in this case as things are changed faster than I can breath. However I can see in my [search project](https://github.com/Import-External-Sources/hosts-sources) that @UltimateHostsBlacklist also blocks...

Thanks for the heads up @emidaniel

same as https://github.com/mitchellkrogza/Phishing.Database/issues/861 and https://github.com/mitchellkrogza/phishing/pull/379 (merged 3 days ago)

`pyfunceble -f phishing-domains-ACTIVE.txt --filter "\.000webhostapp\.com$"` Dead (HTTP 410) records with @pyfunceble 4.2.0 ```python Status Percentage Amount ----------- ------------ ------------ ACTIVE 8% 584 INACTIVE 92% 6729 INVALID 0% 0 ``` INACTIVE...

> Haven't tested these lists in a long time, don't have time at present. Hopefully @funilrys can think of a way to do it and push back here, I'm too...

PS: @mitchellkrogza don't you have some crawler log file I could get insight to, so I can see why a domain might have been marked for phishing, [working](https://github.com/mitchellkrogza/Phishing) i the...

Invalid records in ALL-phishing-links.txt ```css https://aarif.coi5sbo7qhrd6j96gk4c9ub6y0.php?rand=13InboxLightaspxn.1774256418&fid&12528996464553465768746876856538783098286354564542676887987936786765536767657535677634653565767635779832&fid.1&fav.1 http://%20%25**)(**@fbrasil.com/OLD/LqJJ0UKuvg1e0H2F/qiye https://472a4http://app-list-72182.work/login/login.html ```