-
-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FEATURE: Implement check the availability of website / detection of parked & for sale domains #255
Comments
The trick is to setup your own DNS recursor and then import (Setup, configure) it with the RPZ zone The reason is you then will be blocking through the .rpz-nsdname The next thing you have to do is to disable the http status code and whois check and purely relay on the DNS test. You can now do 2 things with the results file
This is a much safer approach than than trying to keep a up to date set of rules, it will also add the ip to the bot lists. Give it a spin, there are some getting started config for Power dns Recursor here: https://mypdns.org/rpz/dns-rpz-integration/-/tree/master/PowerDNS-Recursor If you having trouble getting it to work, please do open a issue or a discussion |
The idea is good @keczuppp. My problem right now is that the same webpage as in the screenshot gives me the text in German (IP-based). |
I don't know much about these things, I would have to study all that stuff first
|
Another idea, from jawz101 : easylist/easylist#2374 (comment) :
|
Touching #128
You should do that as it will enhance your system performances significantly: you should read Performance test of Hosts file vs DNS-Recursors 😉 |
@keczuppp a early version is available in the Does that fit everyone's needs? If it does, I will proceed with merging the branch to the Asking for inputs: @spirillen @mitchellkrogza @ZeroDot1 and others |
A few thought 💭
I might get back with more, when tested |
Feature has been disabled because I need to gather more intel on how people will use this:
|
Personally I would say the As more things is user optional, the better your modular approach is accomplished. |
Pardon for not writing back sooner, but I have not been very active on github lately, I only noticed yesterday.
Cool.
I'm not sure either, I was merely speculating whether it could be useful or not, for the users to distinguish between reasons for which a domain is inactive, but I have no idea whether such a distinction is useful for the users from a practical point of view, so if it is not, in that case we can stick to marking an inactive domain simply inactive, regardless of the reason.
As for the phrases to look for ( LINK 1 ) they seem good, however it seems this one: Also like I mentioned before ( LINK 3 ), we should search the raw body not only for typical word phrases, but also for other text values because:
|
Description
I have been thinking about it even before I've found this: StevenBlack/hosts#1613 (comment) @AdKiller
As many as dead (non-existent domain etc) domains, there are many parked / for sale zombie domains, which still do exist but are dead at the same time...: "This domain is for sale", "Website is no longer available", currenlty PyFunceble marks such domain as ACTIVE...but PyFunceble could have an option to check whether a real website exists on the domain and mark it "REAL" if not, then "ZOMBIE" label.
Possible Solution
Such feature:
Screenshoot
The text was updated successfully, but these errors were encountered: