Track every SSL.com certificate's expiry in one place
See SSL.com certificate expiry alongside every other provider you connect
Connect SSL.com and your certificates show up in InfraNest's certificate list, tracked next to every other provider you manage.
- Certificate expiry tracking: InfraNest imports each certificate's details and expiry date, so you're not checking the SSL.com dashboard to see what's coming due.
- Automatic alerts on certificate issues: trigger on a certificate expiring, expiring soon, changing, being revoked, showing up unexpectedly, or being flagged weak — so problems reach you instead of waiting to be found.
- One label across every provider: tag a certificate and the same tag works for certificates from other providers too, so you can group them by team, environment, or anything else that matters to you.
NoteThis connection only reads certificates into InfraNest — you can't buy, renew or cancel a certificate from here.
What it looks like in InfraNest
What you can do
Once SSL.com is connected, this is what InfraNest can do with it.
- Certificate expiry tracking
- Six certificate health triggers
- Cross-provider tagging
- Multiple SSL.com accounts supported
Not supported
InfraNest doesn't manage cloud infrastructure, DNS, or domain registration through this integration — it only imports SSL.com certificates. You'll still buy, renew, or cancel certificates directly in SSL.com.
How to connect it
- 1
Get your SSL.com API keys
Find your account key and secret key under API Credentials in your SSL.com dashboard.
- 2
Open the SSL.com integration
Go to Integrations and open SSL.com.
- 3
Enter your credentials
Add an optional Account label, then enter your account key and secret key.
- 4
Connect
Leave 'Email me when this integration has problems' ticked if you want email warnings, then select Connect.
That’s it — SSL.com is connected.
Full setup guideSet up with AI
I use SSL.com, and I want to connect it to InfraNest (infranest.io) — it manages domains, DNS, servers and certificates across providers. InfraNest asks for: Account key and secret key. Walk me through creating that in SSL.com: where each setting is in the current interface, whether a read-only option exists, and how to check it works before I paste it in.
What syncs
What InfraNest keeps in sync with SSL.com.
| Certificates | Certificates and their expiry |
Questions
#What happens once I connect SSL.com?
InfraNest imports your SSL.com certificates into your certificate list and tracks their details and expiry. Importing can take a moment because each certificate is fetched one at a time.
#Can I renew or cancel a certificate from InfraNest?
No. This connection is import only, so buying, renewing and cancelling certificates still happens in SSL.com. InfraNest is where you track and get alerted on them.
#What if my account key or secret key is revoked or expires?
Once the credential stops working, InfraNest can't refresh your certificate data and you'll see an authentication error. Reconnect with a valid account key and secret key from your SSL.com dashboard to resume tracking.
#Can InfraNest change anything in my SSL.com account?
No. This integration only reads certificate data out of SSL.com — it doesn't buy, renew, cancel, or otherwise modify anything on the SSL.com side.
#Can I connect more than one SSL.com account?
Yes. Each connection can have its own Account label, and if you leave it blank a second connection to the same provider is labeled automatically so you can tell them apart.
One dashboard for every provider
Add this integration, then the rest of your stack — domains, DNS, servers, certificates and monitoring in one place.
Free plan · No credit card required · Set up in minutes