Https Private Http

[nighton]

172.104.241.29:80
172.105.25.190:80
178.124.189.174:3128
20.230.193.232:80
103.145.76.44:80
3.120.178.136:17777
103.117.192.174:80
103.115.26.254:80
174.138.116.12:80
103.115.252.18:80
103.117.192.14:80
103.197.251.202:80
206.81.0.107:80
67.212.186.99:80
120.196.186.248:9091
183.239.62.251:9091
222.89.229.197:9091
58.221.154.46:9091
223.84.240.36:9091
117.158.218.133:9091
112.14.40.137:9091
183.239.38.216:9091
112.25.185.171:9091
117.159.23.120:9091
113.194.88.13:9091
123.163.48.229:9091
117.160.140.198:9091
223.96.90.216:8085
103.127.1.130:80
183.89.8.70:8080
178.252.175.22:8080
183.239.62.59:9091
144.76.241.45:7890
218.64.253.196:9091
82.114.118.142:1256
14.141.209.11:8080

 

[Avizura]

works

 

[Kostiska]

thanks for sharing this

 

[Mantikor]

"Https is already private as it uses SSL/TLS encryption. Using Https over Http won't provide much added security unless you're working on a legacy system that can't handle the encryption. What's the actual context behind this question?"

 

[sigor65]

"yo, I think the main point here is that HTTPS is just a protocol that encrypts data between your browser and the server, it doesn't necessarily make the data private. Think about it like a secure conversation in a crowded cafe - anyone can still overhear your conversation, they just won't be able to understand what you're saying."

 

[Rvorozhok]

"HTTPS is still the way to go, even if you don't have sensitive info on your web app. It's all about setting user trust and security expectations from the get-go. Plus, Google's algorithms favor HTTPS sites in search rankings."