| title | Frequently Asked Questions |
|---|---|
| description | Common questions about CertWatch |
We connect to your domains over HTTPS and retrieve certificate information. We check expiration dates, validate the certificate chain, verify revocation status via OCSP and CRL, and detect weak cryptographic configurations.
Depending on your plan, certificates are checked every 5 minutes to 6 hours. You can also trigger manual checks anytime from the dashboard.
We support Email, Slack, PagerDuty, and custom webhooks. Discord support is coming soon.
Yes. We use 256-bit encryption for all data. We only store certificate metadata—never your private keys. All API communications use TLS 1.3.
Kubernetes integration is coming soon! Our Helm agent will auto-discover cert-manager Certificate resources and TLS Secrets. Sign up for the beta to get early access when it launches.
After 75 days, you can upgrade to a paid plan with exclusive perks as an early adopter, or continue on the free tier with limited features.
This usually means we couldn't connect to your server. Common causes:
- Domain is not publicly accessible
- Firewall blocking our connection
- DNS not resolving
- Server not responding on the specified port
See Troubleshooting for detailed solutions.
Not yet. Currently, certificates must be publicly accessible over the internet. We're working on an agent-based solution for internal certificates—coming soon.
Go to Settings → Team → Invite Member. Enter their email address and select a role. They'll receive an invitation email to join your organization.
Yes! CertWatch has a full REST API for programmatic access. Create API keys from the API Keys page in your dashboard. API keys support granular scopes (read, write, cloud:sync, or full access) and can be used to integrate CertWatch with your CI/CD pipelines, AWS Lambda functions, or custom tooling. See API Documentation for details.