I propose the following data to be a new case:
| Fields | Data |
|---|---|
| Name | All Traffic is unencrypted (no https) |
| Description | The service doesn’t employ TLS/SSL encryption to secure the traffic between your browser and the website you’re visiting. As a result the data transmitted may be monitored by unauthorized third parties. |
| Classification | blocker |
| Topic | Topic Security (ToS;DR Phoenix) |
| Weight | 100 |
Examples:
Not needed
A blocker because https is standard these days and free to use everywhere
I agree with the proposal, although the weight may be too high in my opinion.
For the description, I think it should be longer to explain what https exactly means:
The service doesn't employ TLS/SSL encryption to secure the traffic between your browser and the website you're visiting. As a result the data transmitted may be monitored by unauthorized third parties.
Good call, fixed the description.
Though I think the weight is justified since SSL encryption is a standard these days and there is no excuse to not support it.
The only time I am aware of missing SSL encryption is some government sites as they deem the cost-usage factor too high, which justifies the weight too.
Thank you for good call 
No adverse opinions have been expressed, so the case has been added to Phoenix: Case 491: All Traffic is unencrypted (no https)
I’ll close the topic in a few days!
This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.