Find the subdomains of any domain in public certificate logs. For each one: whether any certificate naming it is unexpired, when it first appeared, and whether the name looks like a test site. Passive: we never contact your servers.
AI Rankiaexample.com
www.example.com2026-08-02 → 2026-10-31shop.example.com2026-09-14 → 2026-12-13staging.example.com2026-07-20 → 2026-10-18old-blog.example.com2023-03-01 → 2023-05-30*.cdn.example.com2026-06-10 → 2027-06-10We search public certificate logs for names under your domain. Nothing is sent to your servers. It usually takes 5 to 50 seconds.
This tool on airankia.com, Oct 10, 2026. Every publicly-trusted TLS certificate that browsers accept has to be logged, so each new tool, test site or client demo served over HTTPS leaves a name behind.
We ask crt.sh for every certificate naming a host under your domain. Your servers are never contacted.
Look-alikes such as notexample.com are dropped, repeated names merged, and wildcard names listed apart.
First seen, latest expiry date, how many certificates, the latest issuer, and a label if the name looks like a test or infrastructure host.
Every certificate logged for names under your domain, expired ones included. Asked first, retried once if it fails fast.
The marks in the result table. None of them is a check of the live site: they come from the certificates and from the name itself.
*.shop.example.com certificate covers every host one level under it without naming any: a.shop.example.com but not x.a.shop.example.com (RFC 6125). Those hosts won't appear here.Chrome requires "all publicly-trusted TLS certificates" to be CT compliant to validate (Chrome CT policy).
Certificate Transparency logs are public by design, so anyone can audit what was issued (RFC 9162).
A free search over those logs by Sectigo.
We group those certificates by host, date each one and label test or infrastructure names.
Content Hub's Domain Footprint, in the Action Center, starts from the same certificate logs and adds what this free tool can't.
AI Rankia runs your tracked prompts on AI engines with live web search and shows whether they mention or cite your site.
www. and nothing else. For blog.example.co.uk we search under that host; type example.co.uk for the whole domain.We wait about 50 s and retry once if it fails fast. If it still fails, the result says why (timeout or error code), there's no list, and the attempt counts as a run. Failed searches aren't kept, so a retry later asks again.