Custom Fraud Protection for website ! Waring READ before bid !

Hello Sir, We have gone through the details you have provided and would be pleased to work on this with you to deliver the results that you have expected and We are sure you will not be disappointed if you give us this opportunity. Our team is experienced, creative & efficient enough to get your job done well. We have an impeccable record and all our clients enjoy working with us

Dear Customer! I am an expert PHP developer with over 6 years of experience and very interested to work on this project. Available to start immediately and finish as soon as possible. My bid is for fast professional service exciting my customers. Please contact in PMB to discuss details. Best Regards, Zeke

Hi, Your proposed solutions are not very good. 1. IP changes all the time. If i'm from my phone, or even from home, most people loggon using PPPoE so everytime they restart or loose connection they get a new IP. 2. it all depends on what you are protecting if it's something the user bought before, it's easy (either if marked as Ok or Fraud). 3. Once detected I could write in localstorage, but tat too can be wiped out, so that is not a 100% against a malicious user 4. what do you want to do with VISITOR dns? you mean potential customer? Even so. DNS doesn't change that often, and if you have the IP, you can check the DNS at a later time. I assume you want to know the IP owner, network to avoid proxies. This could be done instead with a proxy scrapper that is run once a week to scan a few sites for new proxies + a list of IPs from cheap VPS providers and proxy services (though there may be some users with legitimate proxy use) 5. a much better protection would be to scan social media for the user's name, search if he has friends (and not bots), etc. If you're interested, drop me a line. George

Hi, am i not a bot or a copy paster for start :) i'll like to answer your questions: 111. you cannot know when a cookie has been deleted from the users browser, you can only check (if it exists) when it was created, or we can store date on our server for each ip/user/customer, that a cookie was added at certain time, and when the user comes back with no cookie information, we know that the user has deleted his cookie (the ip would not be such a good ideea as many users have dynamic ips from their providers). 222. this can be done 333. we can store all the ips the user has used/currently using in a cookie, or on the server for each customer/visitor. 444. i'm not that confident that we should log in users based on a dns, we can create a token when a user logs in, store it in the cookie, and when the user comes back verify the token if it matches one in the database, and maybe base64 encode the username and check it with the database also. +++ it depends on what you have on the website, but XSS atach is something you should be careful at and files uploading. Thanks and i look forward to hear from you!

A proposal has not yet been provided