What SSL Certificate does
Create a short-lived RSA certificate for local HTTPS, private services, reverse proxies, containers, and integration testing. ParseNest detects whether the target is a domain or an IPv4/IPv6 address and writes it into the correct X.509 Subject Alternative Name field.
Common uses
- Enable HTTPS on an internal domain or IP during development
- Create PEM files for Nginx, Caddy, Docker, and test services
- Verify DNS SAN and IP SAN behavior before requesting a CA-signed certificate
Privacy and limitations
In trusted mode the private key stays in the current browser tab and only the public CSR reaches ParseNest. ACME order data is temporary. Self-signed mode generates material in server memory and returns it once.
Frequently asked questions
Will browsers trust this certificate automatically?
No. It is self-signed. Browsers and operating systems will show a trust warning until you explicitly trust it. Public websites should use a certificate issued by a trusted CA.
Can the certificate be generated for an IP address?
Yes. IPv4 and IPv6 values are encoded as IP SAN entries rather than DNS names, so standards-compliant TLS clients can match them correctly.
Which files should I configure in Nginx?
Use the downloaded certificate PEM as ssl_certificate and the private-key PEM as ssl_certificate_key. Keep the private key readable only by the service account.