HTTP Response Headers
You're missing several security related HTTP headers. You can add a certain level of protection by setting a few of them
You specify in your TOS that the site should not be placed in iframe, but you take no steps to mitigate that risk. To prevent other sites rendering a frame of yours: X-Frame-Options: sameorigin
To prevent MIME attacks add X-Content-Type-Options:nosniff
Force XSS protection (browser based, may or may not make a real difference) X-XSS-Protection:1; mode=block
Remove Server:nginxheader. It improves security through obscurity so that attackers can't see what server type youre running and narrow down their attack vectors
Make a Content-Security-Policy header with this site: https://report-uri.io/home/generate. This site explains why it's a good idea
Posted Nov 18, 2016, 12:19 AM UTC
Very useful information here.
As for the Server:nginx header I was under the assumption that server_tokens off; disabled that but I guess it only removes the version. I'll look into removing it completely.