GoGetSSL Certificate Expiry
Overview
An expired certificate is one of the most visible outages an MSP can let
happen: the client's site or mail shows a browser warning and the client
notices before you do. GoGetSSL holds the record of every certificate bought
through the reseller account, so it is the right source for a monthly expiry
sweep. Every tool here is read tier and none is admin-gated in Conduit.
Anti-triggers
- Pricing a renewal, checking DCV approver emails or decoding a CSR: use
renewal-prep. This skill finds what expires;
that one gets a renewal ready.
- Certificates not bought through GoGetSSL (Let's Encrypt, a client's own
CA account, another reseller): GoGetSSL has no record of them. Only orders
in this reseller account appear.
Key Concepts
| Field |
Source |
Meaning |
order_id |
all order tools |
Numeric GoGetSSL order ID |
common_name |
gogetssl_orders_list, gogetssl_orders_get_status |
Primary domain on the certificate |
valid_from / valid_till |
gogetssl_orders_list, gogetssl_orders_get_status |
Certificate validity, YYYY-MM-DD. null or 0000-00-00 until issued |
expires |
gogetssl_orders_get_statuses |
Expiry date, returned only for active orders |
begin_date / end_date |
gogetssl_orders_get_status |
The order's subscription period, which can be longer than one certificate's validity on a multi-year order |
status |
all order tools |
active, processing, expired, revoked, rejected (plus other vendor statuses on single-order detail) |
Certificate validity versus subscription. Public TLS certificate
lifetimes are capped by the CA/Browser Forum, and that cap keeps shrinking,
but GoGetSSL sells multi-year subscriptions.
On such an order, valid_till is when the current certificate expires and
end_date is when the subscription ends. A certificate expiring inside a
paid subscription needs a reissue, not a new purchase. Check
gogetssl_orders_get_status before telling anyone to buy.
Common Workflows
Monthly expiry sweep
Call gogetssl_orders_list with status: "active". The vendor does not
page this list, so the status filter is what keeps it inside the response
limit. If the response comes back truncated, or fails with the
response-size error, do not report from it; use the paged fallback below.
Drop rows whose valid_till is null or 0000-00-00. Those were never
issued; handle them in the stuck-order check below.
Compute days to expiry from today and sort ascending.
Bucket into tiers:
| Tier |
Days left |
Action |
| Critical |
14 or fewer |
Renew or reissue now; validation can take days |
| Due |
15-30 |
Start renewal this week |
| Upcoming |
31-60 |
Quote the client, confirm the domain is still in use |
| Healthy |
over 60 |
No action |
Group by registrable domain under common_name and map domains to
clients. Flag domains you cannot map.
For each Critical and Due order, call gogetssl_orders_get_status to read
end_date, the reissue and renew flags, and the domains and SANs covered.
That separates "reissue inside the subscription" from "buy a renewal".
Paged fallback for a large account
When gogetssl_orders_list for a status is truncated or too large:
- Page through
gogetssl_orders_list_ssl (limit and offset) to get
every order ID, and keep the ones with the status you were listing.
- Call
gogetssl_orders_get_statuses with those IDs in batches of 100.
For active orders, use expires as the expiry date (valid_till).
Expired orders get no expires, so call gogetssl_orders_get_status
for each expired ID to read valid_till before filtering by date. If
any expiry date cannot be retrieved, mark the expired-orders report
incomplete and list the order IDs you could not date.
- These results carry no domain. Call
gogetssl_orders_get_status for
each order you will report (for the expiry sweep, the ones inside the
planning window) to get common_name and the SANs before grouping.
Reuse any order detail you already retrieved in step 2.
Recently expired certificates
Call gogetssl_orders_list with status: "expired" (or the paged fallback)
and keep rows whose valid_till is within the last 30-60 days. These are
either sites that went dark or certificates that were replaced by a new
order. Before treating one as replaced, read both orders with
gogetssl_orders_get_status and check that the active order covers every
name the expired one did, common_name and SANs. Report any name it does
not cover.
Stuck orders
Call gogetssl_orders_list with status: "processing". An order that has
sat in processing for days usually failed domain validation. Read it with
gogetssl_orders_get_status: the domain validation status and method fields
tell you whether it is waiting on an approver email, a DNS record or an HTTP
file. Fixing it (resending the email, switching the DCV method) happens in
the GoGetSSL client area; this plugin cannot do it.
Checking a known list of orders
When you already have order IDs (from a previous report or a PSA
configuration item), call gogetssl_orders_get_statuses with up to 100 IDs
in cids. It returns each order's status and, for active orders, expires.
That is one call instead of one per order.
Gotchas
gogetssl_orders_list_ssl returns order IDs and statuses but no expiry
dates. Use it only to page through a very large account, then feed the
IDs to gogetssl_orders_get_statuses in batches of 100.
gogetssl_orders_list without a status filter returns every order the
account has ever placed, and on an older account can hit the response size
limit. Always filter.
gogetssl_orders_get_status returns the issued certificate (crt_code)
and CA bundle (ca_code). These are public, but they are long; summarise
rather than echo them. Personal admin and tech contact fields are removed
by the server; organisation names are kept.
- A SAN certificate covers several domains under one
common_name. Read the
SAN list from gogetssl_orders_get_status before telling a client which
of their hostnames are affected.
gogetssl_account_get_total_orders counts active orders only. Use it as a
sanity check against the length of your active-order sweep.
Related Skills
1---2name: gogetssl-certificate-expiry3description: >4 Tracking SSL certificate expiry across every client domain in a GoGetSSL5 reseller account: which order fields carry the expiry date, how to treat6 unissued orders, grouping certificates by client domain, renewal tiers,7 batch status checks for a known set of orders, and reading one order's8 validity and renewal flags.9when_to_use: >-10 When an MSP needs to know which client certificates bought through GoGetSSL11 are expiring, already expired, or stuck before issuance. Use when: ssl12 expiry, certificate expiry report, expiring certificates, cert renewal13 list, which certs expire this month, expired ssl, gogetssl orders, or14 certificate inventory.15metadata:16 source: https://skillmd.com/skills/wyre-ai/gogetssl-certificate-expiry17---1819# GoGetSSL Certificate Expiry2021## Overview2223An expired certificate is one of the most visible outages an MSP can let24happen: the client's site or mail shows a browser warning and the client25notices before you do. GoGetSSL holds the record of every certificate bought26through the reseller account, so it is the right source for a monthly expiry27sweep. Every tool here is read tier and none is admin-gated in Conduit.2829## Anti-triggers3031- **Pricing a renewal, checking DCV approver emails or decoding a CSR**: use32 [renewal-prep](../renewal-prep/SKILL.md). This skill finds what expires;33 that one gets a renewal ready.34- **Certificates not bought through GoGetSSL** (Let's Encrypt, a client's own35 CA account, another reseller): GoGetSSL has no record of them. Only orders36 in this reseller account appear.3738## Key Concepts3940| Field | Source | Meaning |41|-------|--------|---------|42| `order_id` | all order tools | Numeric GoGetSSL order ID |43| `common_name` | `gogetssl_orders_list`, `gogetssl_orders_get_status` | Primary domain on the certificate |44| `valid_from` / `valid_till` | `gogetssl_orders_list`, `gogetssl_orders_get_status` | Certificate validity, `YYYY-MM-DD`. `null` or `0000-00-00` until issued |45| `expires` | `gogetssl_orders_get_statuses` | Expiry date, returned only for active orders |46| `begin_date` / `end_date` | `gogetssl_orders_get_status` | The order's subscription period, which can be longer than one certificate's validity on a multi-year order |47| `status` | all order tools | `active`, `processing`, `expired`, `revoked`, `rejected` (plus other vendor statuses on single-order detail) |4849**Certificate validity versus subscription.** Public TLS certificate50lifetimes are capped by the CA/Browser Forum, and that cap keeps shrinking,51but GoGetSSL sells multi-year subscriptions.52On such an order, `valid_till` is when the current certificate expires and53`end_date` is when the subscription ends. A certificate expiring inside a54paid subscription needs a reissue, not a new purchase. Check55`gogetssl_orders_get_status` before telling anyone to buy.5657## Common Workflows5859### Monthly expiry sweep60611. Call `gogetssl_orders_list` with `status: "active"`. The vendor does not62 page this list, so the status filter is what keeps it inside the response63 limit. If the response comes back `truncated`, or fails with the64 response-size error, do not report from it; use the paged fallback below.652. Drop rows whose `valid_till` is `null` or `0000-00-00`. Those were never66 issued; handle them in the stuck-order check below.673. Compute days to expiry from today and sort ascending.684. Bucket into tiers:6970 | Tier | Days left | Action |71 |------|-----------|--------|72 | Critical | 14 or fewer | Renew or reissue now; validation can take days |73 | Due | 15-30 | Start renewal this week |74 | Upcoming | 31-60 | Quote the client, confirm the domain is still in use |75 | Healthy | over 60 | No action |76775. Group by registrable domain under `common_name` and map domains to78 clients. Flag domains you cannot map.796. For each Critical and Due order, call `gogetssl_orders_get_status` to read80 `end_date`, the reissue and renew flags, and the domains and SANs covered.81 That separates "reissue inside the subscription" from "buy a renewal".8283### Paged fallback for a large account8485When `gogetssl_orders_list` for a status is truncated or too large:86871. Page through `gogetssl_orders_list_ssl` (`limit` and `offset`) to get88 every order ID, and keep the ones with the status you were listing.892. Call `gogetssl_orders_get_statuses` with those IDs in batches of 100.90 For active orders, use `expires` as the expiry date (`valid_till`).91 Expired orders get no `expires`, so call `gogetssl_orders_get_status`92 for each expired ID to read `valid_till` before filtering by date. If93 any expiry date cannot be retrieved, mark the expired-orders report94 incomplete and list the order IDs you could not date.953. These results carry no domain. Call `gogetssl_orders_get_status` for96 each order you will report (for the expiry sweep, the ones inside the97 planning window) to get `common_name` and the SANs before grouping.98 Reuse any order detail you already retrieved in step 2.99100### Recently expired certificates101102Call `gogetssl_orders_list` with `status: "expired"` (or the paged fallback)103and keep rows whose `valid_till` is within the last 30-60 days. These are104either sites that went dark or certificates that were replaced by a new105order. Before treating one as replaced, read both orders with106`gogetssl_orders_get_status` and check that the active order covers every107name the expired one did, `common_name` and SANs. Report any name it does108not cover.109110### Stuck orders111112Call `gogetssl_orders_list` with `status: "processing"`. An order that has113sat in processing for days usually failed domain validation. Read it with114`gogetssl_orders_get_status`: the domain validation status and method fields115tell you whether it is waiting on an approver email, a DNS record or an HTTP116file. Fixing it (resending the email, switching the DCV method) happens in117the GoGetSSL client area; this plugin cannot do it.118119### Checking a known list of orders120121When you already have order IDs (from a previous report or a PSA122configuration item), call `gogetssl_orders_get_statuses` with up to 100 IDs123in `cids`. It returns each order's status and, for active orders, `expires`.124That is one call instead of one per order.125126## Gotchas127128- `gogetssl_orders_list_ssl` returns order IDs and statuses but **no expiry129 dates**. Use it only to page through a very large account, then feed the130 IDs to `gogetssl_orders_get_statuses` in batches of 100.131- `gogetssl_orders_list` without a `status` filter returns every order the132 account has ever placed, and on an older account can hit the response size133 limit. Always filter.134- `gogetssl_orders_get_status` returns the issued certificate (`crt_code`)135 and CA bundle (`ca_code`). These are public, but they are long; summarise136 rather than echo them. Personal admin and tech contact fields are removed137 by the server; organisation names are kept.138- A SAN certificate covers several domains under one `common_name`. Read the139 SAN list from `gogetssl_orders_get_status` before telling a client which140 of their hostnames are affected.141- `gogetssl_account_get_total_orders` counts active orders only. Use it as a142 sanity check against the length of your active-order sweep.143144## Related Skills145146- [renewal-prep](../renewal-prep/SKILL.md): get each expiring order ready to renew147- [api-patterns](../api-patterns/SKILL.md): paging, size limits and errors