corednsvsSignal TLS Proxy
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| coredns | Signal TLS Proxy | |
|---|---|---|
| Score | 76/100 | 49/100 |
| Rank in category | #5 of 41 in DNS | #16 of 25 in Proxy |
| GitHub stars | 14 400 | 1 284 |
| Stars, last 30 days | +60 | — |
| Stable releases, 12 months | 10 | 0 |
| Latest release | v1.15.0 · 21 Oct 2026 | — |
| Setup | Moderate | Easy |
| Official Docker image | Yes | No |
| License | Apache-2.0 | MIT |
| Main language | Go | Shell |
Which one should you pick?
coredns scores 76/100 against 49/100 for Signal TLS Proxy, so it is the safer default.
coredns ships more often: 10 stable releases in the past year, against 0 for Signal TLS Proxy.
If you want the quickest setup, Signal TLS Proxy is easier to run; coredns needs more configuration.
coredns is growing faster right now (+60 stars in 30 days).
coredns details →Signal TLS Proxy details →
Swap a project
Keep coredns, compare it with
Keep Signal TLS Proxy, compare it with