SSL Certificate
Deploy an SSL certificate to enable HTTPS encryption of websites, trusted identity authentication and prevent against data leaks or tampering during transmission.
Get SSL Certificate →Check CT Log
Look up all SSL certificates issued to your domains
| Common Name | Subject Alternative Names | Valid from | Valid to | Issuer | operate |
No data | |||||
SCT Inspection‑Related FAQs
01/
How do I use this CT Log lookup tool?
It is extremely easy to use. Simply enter the domain‑name you wish to query (e.g. racent.com) inside the search box and click the search button. The tool will automatically check the CT‑log inclusion status of your SSL certificate across mainstream certificate‑transparency logs.
02/
What does the "Unreachable" status in query results mean?
The unreachable status means our tool failed to establish a connection to the target CT‑Log server during your search. This does not necessarily indicate a problem with your certificate. Possible causes include temporary server maintenance or breakdown, routing failures especially for cross‑region requests, regional‑based access restrictions and local firewall or network‑policy interception.
03/
How frequently should I check my certificate CT status?
Carry‑out status checks one working‑day after deploying new SSL certificates, upon certificate renewal or replacement, once your browser raises certificate‑transparency policy alerts, and during scheduled quarterly security audits.
04/
What is a CT Log (Certificate Transparency Log)?
A Certificate‑Transparency (CT) Log is an append‑only public log system that records every newly‑issued publicly‑trusted SSL/TLS certificate. Pioneered by Google, it has evolved into an industry‑wide standard. Its purposes consist of detecting errors or malicious conduct from certificate authorities, assisting web‑site owners in discovering unauthorised certificates and improving transparency and accountability across the PKI ecosystem.
05/
What is an SCT (Signed Certificate Timestamp)?
A Signed‑Certificate‑Timestamp (SCT) is the reply returned by a CT‑Log server after certificate submission, serving as proof the certificate has been logged. An SCT carries the log‑server digital signature, timestamp, log identifier and version data. Browsers require 2‑3 valid SCTs at minimum to deem a certificate compliant with transparency‑related specifications.
06/
Why must my certificate be logged inside multiple CT Logs?
Per certificate‑transparency policies from browsers such as Chrome, publicly‑trusted certificates need submission to 2‑3 independently‑operated CT‑Log servers. This delivers fault‑tolerant redundancy, prevents manipulation of a single log‑server, satisfies multi‑browser and operating‑system compliance requirements, and enables worldwide access to certificate records via geographically‑distributed logs.
07/
Can expired‑certificate CT‑Log records still be retrieved?
Yes. CT‑Logs hold immutable permanent records. Even once a certificate expires, its log entry created during its valid period remains preserved for publicly accessible history checks, provided it was issued by a trusted public CA.
08/
Are self‑signed or private‑PKI certificates required to support CT‑Logs?
No. Certificate‑Transparency regulations are only applicable to publicly‑trusted SSL/TLS certificates issued by public certificate‑authorities. Internal‑use self‑signed certificates, private‑CA certificates and test‑environment certificates are exempted.
09/
What is the operating principle of the CT‑Log lookup tool?
The tool follows this workflow:
1. Accept search criteria including domain‑name, organisation name or serial number
2. Execute searches on CT‑Log databases operated by Google, DigiCert, Sectigo and other log providers
3. Fetch matching certificate entries covering expired and revoked certificates
4. Parse and extract core certificate‑related metadata
10/
Which CT‑Log servers are supported by the lookup tool?
Our tool supports lookups for most mainstream CT‑Logs operated by providers including but not limited to Google, DigiCert and Sectigo.
11/
Are CT‑Log records updated in real‑time?
Update speeds differ between individual log‑servers. Newly‑submitted certificates are generally searchable within several minutes for near‑real‑time synchronisation. Most logs process newly‑submitted certificates within one working‑day. Log‑servers may implement query‑rate limits to prevent abusive requests.
12/
Will sensitive website information get exposed through tool queries?
Your private website data will never be exposed. CT‑Log is a fully‑transparent public database accessible to all internet users. Our tool only fetches publicly‑available certificate metadata and inclusion status without accessing private keys, session‑data or confidential resources. We also do not store or record your search history.
13/
Does every certificate entry get permanently kept by the CT‑Log system?
Yes, permanent record‑keeping represents one of the foundational rules of Certificate‑Transparency. Once logged, certificate records are non‑deletable and tamper‑proof for permanent public inspection. When a log‑server ceases operation, its dataset gets archived and preserved by alternative CT‑Log services.