In enterprise environments, it's (more or less) common to restrict on the proxy or packet filter the ports that the client is allowed to connect to. This makes it impossible to use the above tests and gives false results in the dashboard.
It would be great if https://badssl.com could spare separate IP addresses and make the tests available on port 443.
This is not an issue with badssl.com, but rather an enhancement request.
The following tests use non-standard ports for https: https://tls-v1-0.badssl.com:1010/ https://tls-v1-1.badssl.com:1011/ https://tls-v1-2.badssl.com:1012/
In enterprise environments, it's (more or less) common to restrict on the proxy or packet filter the ports that the client is allowed to connect to. This makes it impossible to use the above tests and gives false results in the dashboard.
It would be great if https://badssl.com could spare separate IP addresses and make the tests available on port 443.
This is not an issue with badssl.com, but rather an enhancement request.