Self-Signed Certificate & Dev CA Generator
Create private development trust material with explicit SANs.
Try before you buy.
- Free preview: the rules, dates and checks that apply to your figures, with every computed amount hidden.
- Locked until you unlock it: download and copy.
- Unlock: Pro pass, ₹179 for 30 days or ₹79 for 1 week, a one-time payment that never renews. Unlock: Pro pass, $5.99 for 30 days or $2.99 for 1 week, a one-time payment that never renews.
Ways to unlock shows how to get the full result.
Printing this result is locked in the free preview.
| Quantity | Value |
|---|
Format, privacy and use notes
Locked in the free preview. Opens the ways to unlock this result.
Locked in the free preview. Batch runs unlock with a pass.
Locked in the free preview. Query results unlock with a pass.
About the Self-Signed Certificate & Dev CA Generator
Create a self-signed leaf for development, or a new local development CA together with a signed leaf certificate. Choose EC P-256 or RSA 3072/4096, DNS/IP SANs, validity and server/client purpose. PEM key/certificate files are available, with an optional password-protected leaf PFX.
These artifacts are for private development/testing and are not publicly trusted. Installing a development CA is a deliberate trust change. The free preview hides key material and full details; a Pro pass opens complete files, copy and reports.
How to use it
- Choose a self-signed leaf or a new development CA plus leaf.
- Enter the common name and every DNS/IP SAN your local test will use; choose key type, purpose and validity.
- Optionally include a protected leaf PFX with a nonempty password, then create the material.
- With a pass, download the artifacts. Install only the public CA certificate in an isolated development trust store when required, and remove it after testing.
Format and verification
The leaf has explicit SAN, basic constraints, key usage and extended key usage. A generated CA can sign the new leaf and has a zero intermediate-CA path length. Device time supplies validity, including a short not-before tolerance.
Use a development trust store
Create a separate test browser profile, keychain or application trust store. Open that profile’s certificate manager, import only mysmartcopilot-dev-ca.pem as an authority and enable it for your local TLS test. Configure the test client to use that isolated store, then connect using one of the leaf’s SAN names.
For a client with an explicit CA-file option, point that option at the public CA certificate instead of changing system-wide trust. Keep mysmartcopilot-dev-ca-key.pem separate and secret. After testing, remove the imported authority and retire the test profile or store.
Sources
X.509 certificate profile, PKCS#12 packaging and public TLS baseline context.
Limitations
- These certificates are not for public website visitors and do not gain public trust by being generated.
- A development CA private key can issue trusted development identities; keep it secret and separate from its public certificate.
- Only the leaf key and public chain go into the optional PFX. PEM private files are unencrypted; trust-store installation and server configuration are deliberate local steps.
Privacy
On this device; its files download once
Inputs, passwords, generated private keys and selected files stay on this device. The tool makes no domain/authority lookup, upload or persistent key store. Reset or leaving the page discards its result.
Frequently asked questions
What do I get without a pass?
Without a pass, Self-Signed Certificate & Dev CA Generator shows the rules, dates and checks that apply to your figures, with every computed amount hidden. Until you unlock it, the result can’t be downloaded or copied. A Pro, Premium or Ultimate pass, a one-time payment that never renews, unlocks the full result. The pricing page lists the passes and their prices.
Can this serve a publicly trusted website?
Public visitors need a certificate from an authority their clients trust. These generated certificates are intended for private development/testing.
Which CA file should I install?
Only the public development CA certificate, in an isolated test trust store if needed. Never install or distribute its private key, and remove the trust entry after testing.
What does the optional PFX include?
The leaf private key, leaf certificate and optional public CA chain. The CA private key remains a separate secret PEM artifact.