I tried


but it said

Ports other than 443 not supported

I need to check imap.spamarrest.com:993

  • do you need a site or can you run a tool on a machine?
    – schroeder
    Commented Jun 21, 2015 at 20:52
  • I can run a tool on my machine, but I thought a site would be more authoritative and configured correctly, and up-to-date, and easier to use.
    – Chloe
    Commented Jun 21, 2015 at 20:58
  • 5
    I recommend to use sslyze.
    – sebix
    Commented Jun 21, 2015 at 21:06
  • What do you want it to analyze? What results are you expecting? The same range of results that ssllabs.com provides?
    – schroeder
    Commented Jun 21, 2015 at 21:07
  • Vote for SSL Labs feature request github.com/ssllabs/ssllabs-scan/issues/441 Commented Sep 12, 2021 at 18:29

4 Answers 4


2021-02-28 Update: GeoCerts and SSLPing

Two new entries on the list. They've been around for a while. Both of these can do ports other than 443:

I prefer SSLPing for it's "just the essentials!" results interface.

ImmuniWeb (new service; formerly HTBridge)


Example: Report for imap.spamarrest.com:993

There are a few. But none even close to what SSL Labs does.

Here are two sample sites.

Port 443 limit is by design

SSL Labs does this on purpose. I didn't know this. But here's the rationale. It's listed inside their Read This First document:

Commonly Requested Features

  • Checking of IP addresses without hostnames; SSL Labs is designed to test public web servers services. We define public as having a DNS record and running on the official port for the given service (e.g., 443 for HTTPS). We don't allow direct checking of IP addresses because we don't consider such services public.
  • Checking of web servers on non-standard ports; see the previous point.

I use https://testssl.sh/

testssl.sh is a free command line tool which checks a server's service on any port for the support of TLS/SSL ciphers, protocols as well as recent cryptographic flaws and more.

It also works well on Windows 10 if you have the 'Windows Subsystem for Linux' installed https://msdn.microsoft.com/en-gb/commandline/wsl/install_guide


There are some alternatives to Qualys SSL Labs which permit analyzing ports other than 443, but their functionality may much narrower:

or you can use open source software without any restrictions:


For me it didn't work out for any of above.

https://www.sslshopper.com/ssl-checker.html was giving cached old results. Even testssls.sh won't give any output.

ssls.com support has given me new way to check which is working:


https://decoder.link/sslchecker/example.com/8000 //port 8000

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .