Topic starter
25/06/2026 10:38 pm
TL;DR: Publicly trusted TLS certificates can authenticate organisations on .onion sites, with EV-only issuance, wildcard support, and a 15-month validity cap under CA/B Forum guidance, according to DigiCert. The practical issue is not anonymity itself, but whether identity proofing and certificate lifecycle controls can keep pace with Tor-facing trust decisions.
Editorial analysis by NHI Mgmt Group, based on content published by DigiCert: “Ordering a .Onion Certificate from DigiCert”.
Key questions
Q: How should teams govern identity proofing for .onion services?
A: Treat .onion identity proofing as a certificate governance problem, not a Tor networking problem.
Q: Why do .onion certificates reduce phishing risk on hidden services?
A: They give users a cryptographic way to verify that a hidden service is operated by the organisation it claims to be.
Q: What breaks when certificate validity is too long for hidden services?
A: A long validity period lets an identity claim outlive the operational context that justified it.
Practitioner guidance
- Map .onion services to a certificate owner Assign a clear business and technical owner for every hidden service that will receive a certificate, and tie issuance to that ownership record.
- Use EV validation as the minimum proofing threshold Require Extended Validation for any .onion service that needs to present an organisational identity to users, and retain the validation artefacts with the certificate record.
- Track the 15-month lifecycle as a hard control Build renewal alerts and approval checkpoints around the validity cap so certificates cannot silently drift past their intended trust window.
Bottom line: .onion certificates show that Tor-based services still need identity proofing if they want users to trust the organisation behind the hidden endpoint.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
25/06/2026 11:15 pm
Identity proofing does not disappear on Tor, it becomes more selective: A .onion address hides location, not organisational accountability. That means the certificate becomes the trust anchor for who operates the service, while Tor handles where it is hosted. The identity control problem is therefore narrower but more demanding: proofing must be strong enough to carry the trust decision when the network layer provides no normal browsing cues.
A question worth separating out:
Q: What is the difference between Tor anonymity and certificate-based identity proofing?
A: Tor anonymity hides the location and origin path of the service, while certificate-based identity proofing tells users which organisation is operating it. They solve different problems, and a hidden service can only be trusted properly when both layers are governed deliberately.
👉 Read our full editorial: Onion certificates show how identity proofs work on Tor sites