Skip to content
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: Special Rules for ChangeIP.com #311

Closed
smed79 opened this issue Oct 24, 2022 · 0 comments
Closed

FEATURE: Special Rules for ChangeIP.com #311

smed79 opened this issue Oct 24, 2022 · 0 comments

Comments

@smed79
Copy link
Contributor

smed79 commented Oct 24, 2022

Description

Changeip sub-sites disabled for abuse are shown by PyFunceble as ACTIVE.

$ PyFunceble -d 2776.4pu.com

Subject            Status      Source
------------------ ----------- ----------
2776.4pu.com       ACTIVE      DNSLOOKUP
$ curl -I 2776.4pu.com
HTTP/1.1 404 Not Found
Server: nginx/1.14.1
Date: Mon, 24 Oct 2022 09:10:33 GMT
Content-Type: text/html
Content-Length: 252
Connection: keep-alive
$ dig @88.198.70.38 2776.4pu.com SOA

2776.4pu.com.	30	IN	SOA	ns1.changeip.com. abuse.changeip.com. 1 3600 150 604800 30

Possible Solution

Considire domains that has in AUTHORITY abuse.changeip.com as INACTIVE.

Additional context

Example of INACTIVE hosts

ChangeIP platform domains

@funilrys funilrys moved this to To do in #PyFunceble Features Oct 25, 2022
@funilrys funilrys moved this to 🆕 New in PyFunceble Backlog Oct 25, 2022
@funilrys funilrys moved this from To do to Waiting for Triage in #PyFunceble Features Oct 25, 2022
@funilrys funilrys moved this from Waiting for Triage to To do in #PyFunceble Features Nov 26, 2022
@funilrys funilrys moved this from 🆕 New to 📋 Backlog in PyFunceble Backlog Nov 26, 2022
funilrys added a commit that referenced this issue Dec 1, 2022
This patch fixes #311.

Also:
  * Introduction of checker/availability/extras/dns.py

From now on any changeip platform domains that were disabled for
abuse will be switch to the `INACTIVE` status.
To do that, this patch looks at the SOA record of the domain and
look for `abuse.changeip.com` in the response.

Contributors:
  * @smed79
@funilrys funilrys moved this from 📋 Backlog to 🏗 In progress in PyFunceble Backlog Dec 3, 2022
Repository owner moved this from 🏗 In progress to ✅ Done in PyFunceble Backlog Dec 3, 2022
Repository owner moved this from To do to Done in #PyFunceble Features Dec 3, 2022
iam-py-test added a commit to iam-py-test/my_filters_001 that referenced this issue Jan 27, 2023
funilrys added a commit that referenced this issue May 29, 2023
Fixed:
  * Security / Dependency Management: cryptography
    Mitigation of CVE-2023-0286 & CVE-2023-23931 through
    version bump.
  * Fatal Error: When no nameservers are configured or provided by the
    hosting system. (#328)
  * Semantic: git.io (#341)
    URLs with git.io were replaced with other one.
  * New linting issues.

Improved:
  * SPECIAL Rules: weebly.com
    We now take down subdomains that return the 406 status code.
  * SPECIAL Rules: wordpress.com (#321)
    We now recognize subjects that were took down by Wordpress.
  * SPECIAL Rules: internal
    Uniformiization of the method for better and quicker development.
  * Dependency Management: sqlalchemy
    We upgraded to SQLAlchemy v2.x+.
  * Converters: internal
    Convertion can now be performed directely without initialization of
    subjects through the convet method.

Removed:
  * Python Support: <=3.7
    We do not test or support any usage of PyFunceble with python<=3.7.

New:
  * Python Support: ~=3.11
    We now test (CI/CD) and support python~=3.11.
  * Testing: pytest (#328)
    pytest can now be used by packager to tests pyfunceble before
    deployment.
  * Database: PostgreSQL
    We now support PostgreSQL as database type.
  * Filesystem: IPs as first-class citizens in plain text outputs (#268)
    From now on, IPs will be stored into the `ips` subdirectory when the
    plain text format is active.
  * SPECIAL Rules: subject-switch (#185 | #185#issuecomment-1290866362)
    We now support the subject switch from any domains.
    For example:

    - m.example.com -> example.com
      Outcome: m.example.com as INACTIVE
    - m.example.com -> example.org
      Outcome: NO status switch.
    - m.example.com -> a.example.com -> example.com
      Outcome: m.example.com as INACTIVE.
    - m.example.com/hello/world -> example.com/hello/world
      Outcome: m.example.com/hello/world as INACTIVE.
  * SPECIAL Rules: changeip (#311)
    When one of the known changeip domains provides `abuse.change.com`
    in the SOA record, the subject will be flagged as INACTIVE.
  * SPECIAL Rules: imgur.com (#319)
    We now flag removed images.
  * SPECIAL Rules: eToxic (#334)
    When a blog from the eToxic infrastructure (known domains) doesn't
    exists anymore, we flag them as INACTIVE.

Contributors:
  * @Nilsonfsilva
  * @smed79
  * @spirilln
  * @T145
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

2 participants