ssl-proxy
:lock: Simple zero-config SSL reverse proxy with real autogenerated certificates (LetsEncrypt, self-signed, provided)
Not yet testedsource: GitHubGoMITcommit 7cf7ab6b7bb4
Go, MIT licensed. The project labels itself: autogenerated certificates, certificate, certificate generation, certificates, go, golang, letsencrypt and letsencrypt certificates.
ssl-proxy has not been verified yet.
Measured by Argusic on a fresh machine every time. Every number links to its evidence.
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
No recorded runs.
Topics (from GitHub)
autogenerated-certificatescertificatecertificate-generationcertificatesgogolangletsencryptletsencrypt-certificatesnginxproxies-https-trafficproxyreverse-proxysecurityself-signed-certificatesslssl-certssl-certificatesssl-proxytlstls-proxy
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/ssl-proxy)Questions
- Does ssl-proxy run?
- ssl-proxy has not been fully verified yet. No recorded run has produced a verdict yet.
- How did Argusic test ssl-proxy?
- On a fresh, disposable machine, with every command recorded. 0 attempts are recorded, and the full method is on the methodology page.
- Where is the evidence for ssl-proxy?
- All 0 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.