jest7325

This tool will help you find weaknesses in your website setup. It will also make sure that your website is powerful enough to receive spikes of users. If you are using Cloudflare it will make sure that your Cloudflare is configured properly.

Clouflare and none Cloudlare users are welcome to try.

Can you please try the free test and send me some feedback?

How many qubit does it take to crack an AES 192 key?

It might be fast but does it handle load? Did you try to benchmark it with a service like https://ddostest.me

Don't be afraid to shake things or the industry but always stay on the bright side. The line is very thin between: I am trying to help and improve security in contrast with I am threatening you. Some people or Business could feel threatened depending on the wordings used when approaching them.

Genius is one percent inspiration, ninety-nine percent perspiration. - Thomas Edison

It's not so original and it sounds like it was copied/pasted from an old quote 100 years ago

I wonder if it would make sense to front-end that with nginx. It has nice http2 and the latest SSL/TLS implementation. Just curious what other think about this approach.

I believe there are times when you can also learn from others' mistakes. I remember the book The count of Monte Cristo and it's about a long and slow revenge. I hope your story will have a good ending!

Interesting talk and I am wondering if the op tried load-balanced algorithm like "leastresponsetime" and "leastconnection"? Today LB are pretty advanced and sometimes are even not even used in technology like ecmp.

I use Vultr and there are some DC that are more stable than other. Generally speaking it's worth what you pay for and I can't complaint.

It's a bit strange that the VPS would have something to do with it. What I mean is that Digitalocean is basically sitting side by side with google. I ping'ed google from the NY3 and I get really fast response time.

booteNg1iethahb8uh

Oops that was my password that I pasted... here is the good paste.

root@debian-512mb-nyc3-01:~# ping www.google.com PING www.google.com (172.217.4.36) 56(84) bytes of data. 64 bytes from lga15s46-in-f4.1e100.net (172.217.4.36): icmp_seq=1 ttl=59 time=2.36 ms

64 bytes from lga15s46-in-f4.1e100.net (172.217.4.36): icmp_seq=2 ttl=59 time=2.44 ms