-
-
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: Special rule: Wordpress.com #321
Labels
Comments
Repository owner
moved this from In progress
to Done
in #PyFunceble Features
Dec 26, 2022
Repository owner
moved this from 🏗 In progress
to ✅ Done
in PyFunceble Backlog
Dec 26, 2022
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
Description
At
wordpress.com
they it seems like they uses the HTTP 410 code for no longer active subdomains likekatiaescorts.wordpress.com
The alternative option is to fetch the h2 html line
Possible Solution
Considered Alternative
Additional context
The text was updated successfully, but these errors were encountered: