Enhancement of the datasets to identify Phishing sites

[payallenka]

We can add on to the data set where we add the phishing sites details. So if an AD leads to a phishing site or if the user ends up going to a phishing site then they can just be warned for it.

[ivedmohan]

We can add on to the data set where we add the phishing sites details. So if an AD leads to a phishing site or if the user ends up going to a phishing site then they can just be warned for it.

@payallenka seems like an intresting feature how will you implement it ?

[payallenka]

So as per the laws there are certain laws for a site to be secure like the use of https.
One, is check the use of http via the regular expression check.
Second, check if the site uses IP address instead of domain name.
Third, use of regex to count the number of subdomain.
Fourth, typo squatting check via the use of Levenshtein distance.
Fifth, the length of exceeds 75
Sixth, maintain a list of url shortness and return a phishing site leads to these
Seven, Maintain a database (mongoDB) to maintain DB of all the sites that were phishing site so next time if the same website url is inputed then we return it phising site straight away.

These were my thought process if I have missed any you can please add on to it. Will integrate it too.

[ivedmohan]

So as per the laws there are certain laws for a site to be secure like the use of https. One, is check the use of http via the regular expression check. Second, check if the site uses IP address instead of domain name. Third, use of regex to count the number of subdomain. Fourth, typo squatting check via the use of Levenshtein distance. Fifth, the length of exceeds 75 Sixth, maintain a list of url shortness and return a phishing site leads to these Seven, Maintain a database (mongoDB) to maintain DB of all the sites that were phishing site so next time if the same website url is inputed then we return it phising site straight away.

These were my thought process if I have missed any you can please add on to it. Will integrate it too.

@payallenka seems like an intresting approach you can and if it's working it would be amazing try experimenting it and create a PR

[payallenka]

Sure !
Kindly add the hacktoberfest tag to it and assign the issue to me.

[payallenka]

Hi, Unfortunately there is a slight issue as I won't be able to complete this task due to some academic work from the college and personal reasons. Please close the issue to re-assign to someone deserving . I deeply apologise for the inconvenience caused. Regards Payal Lenka

…

On Wed, Oct 9, 2024 at 11:54 PM Ved Mohan ***@***.***> wrote: So as per the laws there are certain laws for a site to be secure like the use of https. One, is check the use of http via the regular expression check. Second, check if the site uses IP address instead of domain name. Third, use of regex to count the number of subdomain. Fourth, typo squatting check via the use of Levenshtein distance. Fifth, the length of exceeds 75 Sixth, maintain a list of url shortness and return a phishing site leads to these Seven, Maintain a database (mongoDB) to maintain DB of all the sites that were phishing site so next time if the same website url is inputed then we return it phising site straight away. These were my thought process if I have missed any you can please add on to it. Will integrate it too. @payallenka <https://github.com/payallenka> seems like an intresting approach you can and if it's working it would be amazing try experimenting it and create a PR — Reply to this email directly, view it on GitHub <#16 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AT6EWIYVZBXFEM2DYH4LOWLZ2VYGFAVCNFSM6AAAAABPHAX2E6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBSHE4TOMRRGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[ivedmohan]

Okay no problem, Anyone wanna work on this issue can work