It is working from our office in California.
Given your other recent thread, I suspect that this is more to do with the network setup in your non-California office than the timestamp service itself.
The timestamp service is an HTTP server available at timestamp.apple.com
. I recommend that you try running some standard network diagnostics in the office where you’re having problems. For example:
% curl http://timestamp.apple.com
<html>
<head><title>302 Found</title></head>
<body>
<center><h1>302 Found</h1></center>
<hr><center>Apple</center>
</body>
</html>
The 302 response means that the request made it through to the origin server.
And:
% telnet timestamp.apple.com 80
Trying 17.32.213.129...
Connected to timestamp.pki-apple.com.akadns.net.
Escape character is '^]'.
^]
telnet> q
Connection closed.
The telnet
tool is no longer built-in to macOS but you can either install it yourself use use nc
.
And:
% host timestamp.apple.com
timestamp.apple.com is an alias for timestamp.pki-apple.com.akadns.net.
timestamp.pki-apple.com.akadns.net has address 17.32.213.129
And:
% traceroute timestamp.apple.com
traceroute to timestamp.pki-apple.com.akadns.net (17.32.213.129), 64 hops max, 52 byte packets
…
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"