The following system requirements apply to Adobe Sign (formerly Adobe Document Cloud eSign services or Adobe EchoSign).
- Microsoft Windows 10 using Microsoft Edge, Internet Explorer 11, or a current version of Firefox, or Chrome
- Microsoft Windows 8 using Internet Explorer 11 or later, or a current version of Firefox, or Chrome
- Mac OS X v10.9 or later using Safari 7 or later, or a current version of Firefox, or Chrome
The Microsoft Edge browser does not natively support 256-bit AES encryption of PDF files.
If you are using the Edge browser, please ensure you are running the latest version of Adobe Reader
Adobe Sign mobile apps support the most recent released versions of iOS and Android:
- Latest version and up to two versions back for iOS
- Latest version and up to four versions back for Android
- Adobe PDF (.pdf)
- Microsoft Word (.doc and .docx)
- Microsoft Excel (.xls and .xlsx)
- Microsoft PowerPoint (.ppt and .pptx)
- Text (.txt)
- Rich Text (.rtf)
- Graphics (.tif, .jpg, .jpeg, .gif, .bmp, and .png)
- Web (.htm or .html)
- Adobe Reader 9.0 or later for documents secured with AES 128-bit encryption or lower
- Adobe Reader 10 or later for documents secured with AES 256-bit encryption
If you explicitly whitelist IP addresses on your network, please add the below IP ranges to your firewall:
If your organization whitelists IP addresses to control connection to your inbound mail servers, add the following IP addresses to your whitelist:
Transport Layer Security (TLS) is the most widely deployed security protocol used today for Web browsers and other applications that require data to be securely exchanged over a network. Connections to Adobe Sign require use of TLS 1.2 and support for at least one of the cipher suites below. These requirements apply both to inbound traffic to Sign servers (browsers, API) and outbound traffic from Sign servers to customer servers (API callbacks used for retrieving agreement source documents, returning status, and webhooks).
For browsers: as long as you adhere to the OS/Browser requirements, you should have no browser related issues. All these OS/browsers are fully compliant with our TLS requirements.
For applications using the Sign API, these frameworks support TLS 1.2:
- Java: use Java 8 or later
- .NET: use .NET 4.6 or later
- OpenSSL: use OpenSSL 1.0.1 or later
For servers used to received callbacks or webhook requests from Sign:
- Support TLS 1.2 and at least one of the cipher suites listed below
- Have a valid TLS certificate, and include all intermediate certificates.
Customers who wish to test that their server is compliant can use a variety of free or commercial tools, including the Qualys SSLLabs Server Test, to ensure that their server accepts TLSv1.2, supports at least one of the cipher suites below and has a valid certificate.
TLS Cipher Suites Required:
Adobe Sign is moving to a new SSL Certificate on May 2, 2018. There is no change to the public key, underlying cryptographic protocols or scheme.
Only the Adobe Sign Certificate (listed below) is changing. The Public Key, Root CA, and Intermediate CA will remain the same.
Please contact Customer Support with questions.