Industry-wide SSL certificate validity periods are being significantly reduced:
2026 — 199 days maximum validity (2× renewals per year)
2027 — 99 days maximum validity (4× renewals per year)
2029 — 46 days maximum validity (8× renewals per year)
Action Required: Please ensure your certificate renewal processes are prepared for more frequent updates.
We recommend implementing automated certificate management where possible.
Summary
Metapack places significant focus on platform availability, performance and security. As part of our SSL Certificate solution, we renew certs annually.
The current certs for metapack.com and metapack.net are due for renewal on June 20th 2026 at 23:59 GMT.
We will be updating the certificate prior to this deadline and replace the certificate on June 10th 2026 at 06:00 BST.
You will need to update this certificate if your systems do not allow for automatic certificate updates.
Furthermore if you also install the *.metapack.net x509 certificate locally and it is not configured to auto update, you must manually install the newly renewed *.metapack.net Certificate
MetaPack advises customers to follow best practice guidelines for SSL Certificates, by including Root and Intermediate Certificates in all applications and hardware that support X.509 certificate functionality, including Internet browsers, operating systems etc.
To install the X509 and intermediate certificate locally please follow the instruction below.
Steps to install SSL Certificates
This is a simple guide on how to download and import the ssl certificates.
Alternately you may want to download the certificate from the Certification Authority's(CA) website directly. However you may need to convert the certificate to a format that is compatible with the import tool of choice. MetaPack's CA is Digicert.
Valid until: 15 Jan 2038
Serial #: 03:3A:F1:E6:A7:11:A9:A0:BB:28:64:B1:1D:09:FA:E5
Thumbprint: DF:3C:24:F9:BF:D6:66:76:1B:26:80:73:FE:06:D1:CC:8D:4F:82:A4
In order to tests connections to MetaPack endpoints using the updated SSL cert it is required to modify the hosts file on the machine which tests are running from.
Please edit the hosts file:
Windows:
Getting the IP to use in the hosts file for testing.
ping wildcard.metapack.net.edgekey-staging.net
Output example:
Pinging e3323.b.akamaiedge-staging.net [23.49.58.47] with 32 bytes of data:
Reply from 23.49.58.47: bytes=32 time=23ms TTL=43
Edit the hosts file: C:\Windows\System32\drivers\etc\hosts
[ Test IP - returned from above ] HOSTNAME - this will be the hostname used to connect to Metapack
Example:
23.49.58.47 customer-delta.metapack.com
Save the file.
Using a web browser, browse to the HOSTNAME entered into the hosts file with https://
Example: https://customer-delta.metapack.com
In the address bar click on the padlock -> Connection is Secure -> Certificate is Validated
Check the dates under 'Validity Period' and ensure the 'Expires on' date has updated to December 3rd 2026.
Validity Period
   Issued On Tuesday 19 May 2026 at 01:00:00 BST
   Expires On Thursday 3 Dec 2026 at 23:59:59 GMT
This screenshot is only an example, the date won't reflect that updated certificate.
Linux:
Getting the IP to use in the hosts file for testing.
depth=2 C = US, O = DigiCert Inc, OU = www.digicert.com, CN = DigiCert Global Root G2
verify return:1
depth=1 C = US, O = DigiCert Inc, CN = DigiCert Global G2 TLS RSA SHA256 2020 CA1
verify return:1
depth=0 C = US, ST = Texas, L = Austin, O = Auctane LLC, CN = *.metapack.net
verify return:1
DONE
    Validity
       Not Before: Jun 30 00:00:00 2023 GMT
       Not After : Jun 29 23:59:59 2024 GMT