Your team is preparing a new customer portal. There is no link to it on the main website, and the announcement is still being written. Someone says, “Nobody can find it yet.” Then the team obtains a public web certificate for the new name.
A portal is a website through which customers use a service, for example by signing in to view invoices. Your browser, the program used to open websites, asks a server for that page. The server is the computer system that answers.
For a protected web connection, the server presents a certificate. This signed digital document connects the website name to public information used to check its identity. The issuing organisation checks the applicant’s entitlement to obtain it.
A domain is an internet name, such as example.com, under which the owner can arrange services. If a mistaken or unauthorised certificate is issued for that domain, the owner needs a way to discover it. Making issuance visible serves that purpose. 5 9
That name may now be discoverable in public certificate records, even without a link from your homepage. The system behind those records is called Certificate Transparency, or CT. Its purpose is to make certificate issuance visible and checkable. An important consequence is that a website name should not be treated as a secret simply because you have not advertised it. 8
Why publish certificate information?
A web certificate helps a browser verify a connection to a named service. The issuing organisation, called a certificate authority, is trusted to perform the relevant checks. But what if a certificate is issued for your domain without your authorisation? You need a way to discover that it exists. 9
Think of public noticebooks in which entries can be added but not quietly erased. CT uses several independent logs of certificate information, not one central register of domain names. Their design allows the recorded history to be checked. Other systems, called monitors, watch these logs for entries of interest. 8
A log is a collection of records, not the website itself. In this system, records about certificates are added to logs run by different operators. Someone can read those records independently of visiting the named website. The logs provide mathematical checks for the recorded history, so an observer can check that an entry was included and that a newer history consistently extends an older one. The point is not simply “trust the log operator”; the published structure lets other programs check its behaviour. A beginner need not perform those calculations to understand why public, checkable history is useful. 8
A monitor is another program that reads the logs and looks for records of interest, such as names belonging to your business. It can notify an operator who then decides whether an entry is expected. A search website makes some collected records easier for people to find. These roles are different: the certificate authority issues, the log records, and the monitor looks for relevant entries. None of them is automatically the computer hosting your invoice portal. 8
If you arrange monitoring for your domain, an unexpected certificate can become a question to investigate rather than an invisible event. The system helps reveal incorrect issuance; logging does not itself prevent an authority from making a mistake. That difference explains both the value and the limits of transparency. 8 9
This is not a reason to avoid HTTPS. Public records support scrutiny of the system that helps browsers trust connections. The preparation of your own service must account for that visibility instead of depending on a private launch date.
What goes into the record
Certificate information includes names and a public key. The public key is meant to be shared; the corresponding private key is secret and is not part of the certificate. Logging a certificate does not, by itself, publish a password, an invoice or the private key. The disclosure is about the certificate and its identifiers. 5
There is a small but useful distinction in the publication process. An authority can submit a preliminary certificate record, called a precertificate, to a log. It contains certificate information but is not itself a certificate that a browser should accept for the ordinary website connection. The log returns a signed promise to include it within a specified period. That promise is not the same thing as checking that inclusion has already happened. 8
Requesting a certificate, promising a log entry, adding the entry and using the finished certificate on a website are different events. A record of one does not automatically demonstrate the others. 8
In our launch example, the team requests a certificate containing test-portal.example.com. A preliminary record goes to a log as part of that process. Once that record is included and collected by a search or monitoring service, someone can find the name there. The record does not have to wait for a homepage announcement, a customer’s first visit or the team’s permission to publicise the launch. That is the causal link between obtaining the public certificate and possible early visibility. It is not a claim that every search service instantly receives every new record. 8
A monitoring or search service also has its own coverage. It examines particular logs and processes their records. The search box you use is not the whole CT system. No result should therefore be read as “no certificate or service can exist,” unless the much narrower question of coverage has been addressed. 8
What an observer can learn
Suppose a certificate includes the illustrative name test-portal.example.com. Someone reading the public record can learn that name without visiting the portal. The words suggest a test service, but a name is not proof of what the system contains. It might be planned, retired or used differently from what its name suggests. CT records certificate information; it does not continuously test whether each named service is running. 8
A certificate can also cover a wildcard name such as *.example.com. That does not list every individual service that might use it. The star has a limited role in name matching; it is not a complete list of the company’s systems. This is another reason that certificate searches cannot replace the operator’s knowledge of its services. 3
Nor does a public name mean anyone has entered the service. Knowing an address, reaching a login page, finding a weakness and successfully using that weakness are separate steps. A certificate record alone does not establish the later steps. The logging mechanism gives information about names and issuance, not evidence of an intrusion. 8 9
Even if a scanner contacts the service soon after a certificate record appears, the timing alone does not show how it learned the name or whether it got inside. Access restrictions should be ready before the service becomes reachable, regardless of how someone discovers it.
Prepare for visibility, and use it yourself
For the new portal, the practical question is whether access is restricted before it becomes reachable from the internet. Until the team is ready, use invented test data rather than customer documents. Do not put secrets or sensitive customer descriptions into names intended for public certificates. A less revealing name may disclose less, but it is not a replacement for controlling who can enter.
For an existing domain, certificate monitoring can help you notice unfamiliar issuance. Give alerts to someone who knows how the website is operated. A new certificate might be an ordinary renewal or an authorised hosting change. If nobody can explain it, investigate with the operator and issuing authority instead of simply clearing the notification. 8
Confirmed unauthorised issuance needs a response to the underlying access problem, as well as the relevant revocation process. Let’s Encrypt’s guidance, for example, discusses certificates issued after someone gains control of a server or domain settings. An unexpected record is a starting point for that investigation, not its conclusion. 7
Finally, do not promise to erase a published name by removing a website or replacing its certificate. These logs are designed to retain their history. Correct the access problem and future naming practice rather than depending on the old entry disappearing. A sensible launch plan assumes the address may become known and makes that an ordinary, manageable event. 8
Sources
[3] IETF RFC 9525 — Service Identity in TLS
[5] IETF RFC 5280 — X.509 Certificates and Revocation
[7] Let’s Encrypt — Revoking Certificates
[8] Certificate Transparency — How CT Works
[9] IETF RFC 9162 — Certificate Transparency Version 2.0 (Experimental)