ftps

[1] c# - Connect to ftps:// URL - Stack Overflow ( (2017-03-26 04:27:59 +09:00)) http://stackoverflow.com/questions/30082054/connect-to-ftps-url

Anyway, the ftps:// is still recognized by some software to refer to an FTP over TLS/SSL protocol (secure FTP). This mimics https:// scheme, which is an HTTP over TLS/SSL (https:// is a standard scheme).
Though the ftps:// is NOT recognized by the .NET framework.

[2] c# - Connect to ftps:// URL - Stack Overflow ( (2017-03-26 04:28:30 +09:00)) http://stackoverflow.com/questions/30082054/connect-to-ftps-url

Note that the ftps:// prefix commonly refers to an implicit mode FTP over TLS/SSL. The .NET framework supports only an explicit mode. Though even if your URI is indeed referring to the implicit mode, most servers would support the explicit mode too anyway. So this won't be a problem typically. For the explicit mode, ftpes:// is sometimes used.

[3] Session URL :: WinSCP ( (2017-03-26 04:29:32 +09:00)) https://winscp.net/eng/docs/session_url

sftp|ftp|ftps|ftpes|http|https|scp :// [ <username> [ : <password> ] [ ; <fingerprint> ] @ ] <host> [ : <port> ] /

[4] Session URL :: WinSCP ( (2017-03-26 04:31:05 +09:00)) https://winscp.net/eng/docs/session_url

You should also always explicitly specify a protocol (sftp, ftp, scp, for FTP over implicit TLS/SSL use ftps, for FTP over explicit TLS/SSL use ftpes, for WebDAV use http, for WebDAV over TLS/SSL use https).1) For all protocols WinSCP-specific alternative is supported, with winscp- prefix.

[5] FTP over TLS - FileZilla Wiki ( (2017-02-22 17:13:19 +09:00)) https://wiki.filezilla-project.org/FTP_over_TLS

For a client to connect to a server using SSL, then the host for that connection needs to be set to FTPS. In FileZilla client this means prefixing the host with "FTPES://" for "explicit" FTPS, or "FTPS://" for the legacy "implicit" FTPS.