Bridge SSL
About Bridge SSL: who writes this, and how it is checked
Bridge SSL is the certificate layer of Bridge CDN, and this site is its documentation: how certificates and encrypted connections work, written by the team that operates them. This page says who writes the material and how it is checked, because documentation you might act on should be willing to answer that.
Who writes this
The Bridge CDN team writes this site, and the same team builds the platform it describes. Pages are published under the team rather than under individual names: accuracy is a shared responsibility here, and a page is held to the same standard whoever drafted it.
How this site is written and checked
Four rules govern what gets published, and they explain absences you may notice.
Protocol behaviour is traced to specifications. Where a page says how certificates or connections behave, that comes from the standards rather than from repetition, and a specification number appears with a link where it helps a reader.
Values that change are dated or omitted. Certificate lifetimes, rate limits, deprecation deadlines and browser behaviour all move. Where a figure cannot be attributed to a source and dated, the page describes the mechanism and leaves the number out.
Product claims are kept apart from protocol claims. How encryption works and what Bridge CDN does are different kinds of statement, and the second kind is checked against the product before it is published.
Boundaries are respected. Certificate pages cover certificates. Questions that belong to naming or to delivery are named as such and left to the sites that cover them.
What you will not find here
Configuration that ages badly. Server pages give the directives that have been stable for years and leave out protocol and cipher settings, which change on schedules set by browser vendors. A page listing exactly which ciphers to enable would be wrong within a year and would be followed anyway.
Instructions built on interface names. Where a platform renames its menus, an instruction written around those names breaks, so pages describe actions and models instead.
Comparisons that pretend the other side has no strengths. Where a page compares, the other option’s advantages come first, and where the honest answer is that the choice barely matters, the page says so.
Corrections
Every page shows when its text last changed, and that date moves when the text does. A specific report about one sentence is worth more than a general impression, and a technical correction is applied on its merits whoever sends it.
Contact
Bridge SSL has no separate contact address. The team is reached through Bridge CDN, where the product and the account live, and reports about this site go the same way.
The platform
Bridge SSL is not sold on its own: certificate issuance and renewal are part of a Bridge CDN account, run by the team that writes this site. Wildcards follow the same rule: there is no separate wildcard SSL certificate to buy, and *.example.com is issued when the domain’s DNS is on Bridge DNS. Technical pages describe how certificates work without reference to any provider, and product statements appear as product statements.
Several pages argue against paying for things that do not differ, and one argues that automated renewal does not remove the need for an independent check. If a page ever reads as though a protocol fact were a reason to buy something, that is a defect worth reporting.
Where to start
Three entry points cover most of the material: SSL errors if something is broken right now, certificates for what they contain and how the lifecycle works, and ACME for automated issuance and renewal. If you are installing for the first time, installation covers the five steps that apply on every server.
FAQ
Who writes Bridge SSL documentation?
The Bridge CDN team, the same people who build the platform, which is why the pages describe failures from the side that has to repair them. Material is published under the team rather than under individual names, so responsibility for a correction sits with the team that can make it.
Why do some pages not give specific numbers?
Because the numbers in this subject move: certificate lifetimes, issuance limits and vendor deadlines all change on schedules nobody here controls. Where a figure cannot be attributed to a source and dated, the page describes the mechanism that produces it instead, since the mechanism outlasts the value.
Why is there no cipher configuration here?
Because configuration advice ages faster than anything else in this subject and is still followed years later. A setting that was correct when written can weaken a server once vendors move, and nothing in a copied block says when it was written.
How do I report a mistake?
Through Bridge CDN, which is where the team is reached. A report that quotes the sentence and says what is wrong with it is the fastest to act on, and every page shows when its text last changed.
Is the documentation independent of the product?
The technical pages describe how certificates and connections behave without reference to any provider, because the behaviour is the same whoever issues them. Where a statement is about Bridge CDN rather than about the technology, it is presented as such and kept apart from the explanation.