Also its funny, you people are shilling sites in your footer that have many user complaints as scams.
https://www.sportsbookreview.com/forum/sportsbooks-industry/3492681-scammed-sportsbet-io.htmlhttp://bittrust.org/sportsbetiohttps://bitcointalksearch.org/topic/sportsbetio-scam-beware-2482179Also no license to operate?
https://game-protect.com/curacao-license-scam/And there are a bunch more.. So really who is the scammers? In addition since you clearly do not understand what our use case is let me explain it to you in a way that you understand. I looked at each of the sites in your sigs. You are running wordpress websites with outdated plugins to run betting sites? Crazyness... You do not even have HSTS on your SSL, this is bad for what your shilling. If i can tell your webserver that i do not support your level of ssl and it downgrades to meet what i say i support that opens you up to a whole lot of attacks. You also need to use those X-Frame Options. Learn what it is. You also don't understand to delete the PHPINFO files from your site which tells everyone in the world about your backend. This sports bet site doesn't even run mod security on it with owasp top 10 rules. In addition these services and sites are not even firewalled. This is very poor all they way around. Also you use insecure cookies. Little bit about this.
When a cookie is set by the server (sent the header of an HTTP response) there are several flags that can be set to configure the properties of the cookie and how it is to be handled by the browser.
One of these flags is known as the secure flag. When the secure flag is set, the browser will prevent it from being sent over a clear text channel (HTTP) and only allow it to be sent when an encrypted channel is used (HTTPS).
But you want to sit here and call everyone scammers while you , yourselves shill sites that suffer from click hjacking, many other issues including scamming users of funds. Maybe you should look at your own stuff first instead of robo scam call everything. The amount of money that is lost by people using this service is not ok. But you people sit here and say that everyone else will lose money buy investing in our coin. Do you not think that is a double standard?
At least your using cloudflare. butt.. lol.. Also understand what cloudbunny does. It bypasses cloudflare to get your real ip address of your hosting. So yea we have looked at that too.
Also your using github to store your files and sync them over. you should prob remove .git folders... just saying...
And what are those? NoSQL Injections? Yea i would run from this site and anyone that shills it in the footer.. Totally unsafe for anything...
Little bit about that one...
A NoSQL injection occurs when a value originating from the client’s request is used within a NoSQL call without prior sanitisation.
This can allow cyber-criminals to execute arbitrary NoSQL code and thus steal data, or use the additional functionality of the database server to take control of further server components.
Next we looked at bitwings.org
This site does not even use cloudflare. It leaks all the site data to the internet. And again this is a wordpress site with outdated plugins. No HSTS, X Frame Options again. Click Jacking, insecure cookies, etc... But your running a money site off this.. hummm.. Did the same person set these up?
213.136.67.13
m4693.contaboserver.net
Contabo GmbH
Added on 2019-08-04 09:18:54 GMT
[Germany] Germany
HTTP/1.1 301 Moved Permanently
Date: Sun, 04 Aug 2019 09:20:37 GMT
Server: Apache/2.4.10 (Debian)
X-Pingback:
http://bitwings.org/xmlrpc.phpSet-Cookie: pll_language=en; expires=Mon, 03-Aug-2020 09:20:37 GMT; Max-Age=31536000; path=/
X-Redirect-By: WordPress
Location:
http://bitwings.org/...
Yummy Apache 2.4.10 thats nice and exploitable...
Here are the CVE for this version
https://www.cvedetails.com/vulnerability-list/vendor_id-45/product_id-66/version_id-177881/Apache-Http-Server-2.4.10.htmlOk nice.. look at this .. open ssh and telnet... thats real safe...
Nmap scan report for m4693.contaboserver.net (213.136.67.13)
Host is up (0.097s latency).
PORT STATE SERVICE
21/tcp closed ftp
22/tcp open ssh
23/tcp closed telnet
80/tcp open http
110/tcp closed pop3
143/tcp closed imap
443/tcp open https
3389/tcp closed ms-wbt-server
Nmap done: 1 IP address (1 host up) scanned in 0.31 seconds
Next we looked at Wolf.bet
Same stuff it seems...
So basically your sitting here railing on a honest group of crypto people, while at the same time promoting sites that users can be robbed, and frauded on. These sites have alot of user complaints on them. But you call me the scammer? Have you even read our white paper?