'http://timestamp.verisign.com/scripts/timstamp.dll not available

When the following URL is not available, what other timestamp URL can I use in my setup authoring tool? The specific error I get is: SignTool Error: The specified timestamp server either could not be reached or returned an invalid response.

http://timestamp.verisign.com/scripts/timstamp.dll



Solution 1:[1]

Try these servers

http://tsa.starfieldtech.com
http://timestamp.globalsign.com/scripts/timstamp.dll
http://timestamp.comodoca.com/authenticode
http://www.startssl.com/timestamp
http://timestamp.verisign.com/scripts/timstamp.dll
http://timestamp.sectigo.com

With a retry script such as the one included here: Alternative timestamping services for Authenticode

Solution 2:[2]

http://timestamp.verisign.com/scripts/timstamp.dll has limped along for the last few years and had been working in a sort of depreciated state, but the new owners of the certificate issuing business, DigiCert, have issued a migration alert.

They have officially put the old services to EOL as of the back end of 2019.

(article no no longer exists 18/11/2020) https://knowledge.digicert.com/alerts/migration-of-legacy-verisign-and-symantec-time-stamping-services.html

DigiCert TSA

New services can be found at

http://timestamp.digicert.com?alg=sha1

http://timestamp.digicert.com?alg=sha256

Troubleshooting time stamping

Solution 3:[3]

For jarsigner users:

As of 4/24/2017, Verisign knowledge base article AR185 recommends the jarsigner arguments "-tsa http://sha256timestamp.ws.symantec.com/sha256/timestamp". This works for certificates issued by Symantec, and presumably all of Symantec's subsidiaries, at least. http://timestamp.verisign.com/scripts/timstamp.dll does not work.

Solution 4:[4]

This list of time servers seems to be getting regular updates: https://gist.github.com/Manouchehri/fd754e402d98430243455713efada710

Solution 5:[5]

You can use "http://timestamp.digicert.com" without quotes. for more info: https://knowledge.digicert.com/solution/SO912.html

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution Source
Solution 1 Mitch Wheat
Solution 2
Solution 3
Solution 4
Solution 5 Vijesh V.Nair