If the site can be accessed via internet, use the Ssltest.
The site will generate a giant report with various information about what the server supports, for example:
- Protocols
- Ciphersuites
- Certificate Chain (chain of certificates?)
You can check here the report pro google site.
If the site is only accessible on an internal network, you can use nmap.
No stackexchange de security the question has already been answered:
Translating:
"
You can use nmap to scan the server:
# nmap --script ssl-enum-ciphers example.com
tarting Nmap 6.47 ( http://nmap.org ) at 2014-10-15 03:19 PDT
Nmap scan report for example.com (203.0.113.100)
Host is up (0.090s latency).
rDNS record for 203.0.113.100: edge.example.com
Not shown: 997 filtered ports
PORT STATE SERVICE
80/tcp open http
443/tcp open https
| ssl-enum-ciphers:
| **SSLv3: No supported ciphers found**
| TLSv1.0:
"
Only replaces the example.com
in the pro address command of your website.
Your website is made in what language?
– perozzo
@Perozzo , Apache PHP
– Daniel Santos
Received e-mail from whom? From Amazon?
– Dherik