Insights:Renewal & Asset Ledger Issues: First Check These 5 Steps
Step 1: Determine the Scope of the Anomaly
- Is the entire site inaccessible, or only specific pages?
- Can only you not access it, or are users in multiple regions affected?
- Is it an HTTP error or a timeout?
The scope determines the troubleshooting direction.
Step 2: Check DNS Resolution
- Does the domain still resolve correctly?
- Does the resolved IP point to the correct server?
- Is the domain expiration date approaching or already past?
If resolution is abnormal, the issue is at the domain layer.
Step 3: Check Certificates
- Has the certificate expired?
- Does the domain match the certificate?
- Do only some devices show alerts?
Certificate issues usually present as site-wide warnings while the service itself remains functional.
Step 4: Check the Host
- Has the host shut down due to non-renewal?
- Is the disk full?
- Are the service processes running?
Host-layer problems typically cause timeouts or 5xx errors.
Step 5: Check the Application and Third-Party Services
- Are there anomalies in application logs?
- Have dependent third-party services (CDN, forms, analytics) expired?
Troubleshooting Checklist
| Symptom | Priority Check |
|---|---|
| Domain resolution failure | Domain expiration / resolution configuration |
| Site-wide alerts | Certificate |
| Connection timeout | Host expiration / load |
| Partial feature failure | Third-party services |
Update Records After Recovery
- Document the cause of this incident.
- Add any missing asset entries to the register.
- Adjust the advance notice period for reminders.
Troubleshooting without a post-mortem review will lead to the same issues recurring.
Scope
This article is organized around common web site structures. Multi-node or cloud-native architectures follow different troubleshooting paths and require monitoring data.
Related reading: