Closed PeterDaveHello closed 8 months ago
This one is probably a bug cause I only find 240.112.0.101.static.digitalpacific.com.au
240.112.0.101.static.digitalpacific.com.au
resolved to 101.0.112.240
then 🤣 (sometimes reversed order when the IP address is in the domain name)
BTW, 101.0.112.240
actually existing in some databases:
https://www.virustotal.com/gui/ip-address/101.0.112.240
I also found it in another commercial database that not listed on VirusTotal.
VirusTotal
@PeterDaveHello interesting. Let's whitelist that single IP and I'll take care of the IP range within the PyFunceble project.
Okay, cool! That could help to find out abnormal data and fix them to the correct one earlier 👍
FYI @PeterDaveHello:
Upon checking, I remember that Python already implements those through the std ipaddress.IPv4Address
or ipaddress.IPv6Address
classes. Therefore, PyFunceble should already be able to handle such IP ranges. In fact, PyFunceble already refuses to check such IPs.
So, this is a local issue with this project script... Let me keep this open as I'll probably do some refactoring next year.
Thank you for your time, feedback, and support @PeterDaveHello.
Describe the bug
Just found
240.112.0.101
in https://github.com/mitchellkrogza/Phishing.Database/blob/master/phishing-IPs-ACTIVE.txtMaybe
240.112.0.101
shouldn't be in the database because240.0.0.0/4
is reserved for future use?Not sure if it's a special situation when the IP was recorded, but the IP can't be described in many different dabases, even the geolocation database, which is very special I think.
Reference: