issued.live
Server Details
Certificate transparency and DNS history: certificates, past IPs, reverse IP and new domains.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- tuxxin/mcp
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- –
TDQS
Score is being calculated.
Available Tools
15 toolscertificates_by_keyCertificates sharing a public keyRead-onlyIdempotentInspect
Every certificate issued for one public key, by the key's SHA-256 (spki_sha256 on a certificate). NEEDS AN API KEY ON THE PLUS PLAN OR ABOVE.
Key reuse across certificates for unrelated names is a strong operator linkage. It searches only certificates first observed in the last 32 hours (the live table); archived certificates are not searched by key, and certificates ingested before 2026-09-07 carry no key hash. So a short answer can mean "not searched" rather than "not reused"; the reply's coverage field says so.
Inputs: spki_sha256 (required).
certificates_on_ipCertificates for the hostnames on an addressRead-onlyIdempotentInspect
Every certificate issued for the hostnames observed resolving to one IP address, in issuance order (valid_from). NEEDS AN API KEY ON THE PRO PLAN.
A certificate qualifies when a SAN names one of the address's hostnames exactly, or is the wildcard one label above it. It is not "certificates whose SAN is the IP": IP-address SANs are not collected. The hostnames are every name ever seen on the address, so a shared host's tenants each bring their own certificates; co-location is not a relationship.
from/to (YYYY-MM-DD, UTC, at most 15 days) is the window of FIRST OBSERVATION in CT, not of issuance; the default is the last 7 days. Each archived day searched costs one read per registrable domain on the address, so a busy address gets a narrower window: the reply's window, budget and coverage say what was searched, and coverage.unavailable_days what could not be. Addresses with more than 5000 hostnames (CDN, parking) are refused. issuer (exact organization, any case), wildcard and order narrow it; page with after=<next_cursor>. archive_day lets get_certificate read one file for the full record.
Inputs: ip (required), to, from, after, +4 more.
corpus_statsCorpus size and coverageRead-onlyIdempotentInspect
How much this corpus holds and how fresh it is: total domains, certificates and log entries seen in the last 24 hours, DNS resolution coverage, CT log health, and the leading issuers and TLDs.
Use this to calibrate a claim about coverage before making one — in particular, "domains_no_dns" is the count of domains for which no address has ever been resolved, and it is a large fraction of the corpus. Most of what certificate transparency shows has never resolved.
as_of is when the figures were computed, which may be up to about ten minutes ago; the figures move by fractions of a percent over that interval.
Inputs: no named parameters. Returns: as_of, domains, top_tlds, certs_24h, +10 more
domain_detailFull domain recordRead-onlyIdempotentInspect
Everything held for one domain in a single call: the record, registration timing, every address it has resolved to (each with the network behind it), and every certificate covering it with its SAN list. NEEDS AN API KEY ON THE PLUS PLAN OR ABOVE; lookup_domain is the free summary.
Each address carries current (resolves there now) and network: ASN, organisation, announced range, country and reverse DNS, with network.status found, none or unavailable. "unavailable" means the enrichment could not be fetched this time, not that the address has no network; network_lookup counts how many of each.
The same caution as lookup_domain applies to nulls: a null registration date is "not held", never "not registered". Accepts a hostname or a URL; a subdomain is answered for its registrable domain.
Inputs: domain (required).
domains_in_rangeDomains in an address rangeRead-onlyIdempotentInspect
Reverse lookup across a small CIDR range: which hostnames have been observed on any address in it. NEEDS AN API KEY ON THE PLUS PLAN OR ABOVE.
THE RANGE IS CAPPED AT 256 ADDRESSES: an IPv4 /24 or narrower. Ask for /24s, and issue several calls rather than one wide one. Paging works as in domains_on_ip.
The same caution as domains_on_ip applies more strongly here: names sharing a /24 usually share a hosting provider and nothing else.
Inputs: cidr (required), after, limit, first_seen_to, +1 more. Returns: count, hosts, limit, order, +6 more
domains_on_ipDomains on an addressRead-onlyIdempotentInspect
Reverse lookup: which hostnames have been observed resolving to one IP address. NEEDS AN API KEY ON THE PLUS PLAN OR ABOVE.
Returns the hostname, its registrable domain, and when the pairing was first and last seen. A hosting or CDN address can carry a very long tail of unrelated names: co-location on an address is not evidence of a relationship between the domains, and should not be reported as one.
last_seen is when the pairing was last confirmed. An old last_seen means the name has moved or stopped resolving, not that it still points here.
A busy address holds more names than one reply: send after="" to walk all of them in stable order, passing each reply's next_cursor back as after. Accepts IPv4 and IPv6; for a range use domains_in_range.
Inputs: ip (required), after, limit, first_seen_to, +1 more. Returns: count, hosts, limit, order, +6 more
domain_timelineA domain's timelineRead-onlyIdempotentInspect
The dated sequence of what has been observed for one domain: when a zone file first listed it, each certificate, the first DNS answer, address changes. NEEDS AN API KEY ON THE PLUS PLAN OR ABOVE.
Every event names its source and its precision, and gap_seconds where a gap between two events is the point (registration to first certificate, certificate to first answer). An event is when WE observed it, which bounds when it happened; it is not a registry's own timestamp.
Inputs: domain (required).
get_certificateOne certificateRead-onlyIdempotentInspect
One certificate by id: issuer, validity, key, and its full SAN list. NEEDS AN API KEY ON THE PLUS PLAN OR ABOVE.
Takes the 32-hex cert_id that lookup_domain and domain_detail publish as ssl_cert, or a 64-hex certificate SHA-256. The SAN list of a shared certificate links names that a reverse proxy would otherwise hide from each other; it is a linkage, not proof of common ownership.
Inputs: id (required).
list_dataset_filesDataset files on your planRead-onlyIdempotentInspect
The bulk dataset files your subscription can download right now: day, dataset, rows, bytes and SHA-256 for each. NEEDS A SUBSCRIBER KEY (any plan).
This lists; it does not download. The files are large (a daily delta can be several GB), so fetch them over HTTPS with the same key: GET https://issued.live/api/v1/files/{day}/{name} with Authorization: Bearer . Column-by-column descriptions are at https://issued.live/developers/files.
Inputs: no named parameters.
lookup_domainLook up a domainRead-onlyIdempotentInspect
What certificate transparency and DNS enrichment hold for one domain.
Returns the certificate record (issuer, SSL expiry, certificate hash, when it was first and last seen) plus every address the domain apex has been observed on, newest first.
Accepts a bare hostname or a pasted URL — "https://www.example.com/path" is reduced to the domain. A subdomain is folded to its registrable domain, so "mail.example.co.uk" is answered as "example.co.uk".
WHAT THE NULLS MEAN. registered and expires come from registry data and are absent for most names in the corpus. first_zone_seen is when a registry zone file first listed the domain, an upper bound on a new domain's registration date. A null is "we do not hold this", NEVER "this domain is not registered" — do not report a domain as unregistered on the strength of a null here. Likewise an empty addresses list means the apex has not been resolved, not that the domain does not resolve.
The address shown is the APEX's, not a subdomain's, which is why it can differ from an address a subdomain resolves to.
Inputs: domain (required). Returns: ip, domain, expires, tracked, +9 more
lookup_domainsLook up many domains at onceRead-onlyIdempotentInspect
Up to 500 domains in one call, answered in the order sent, each with status found, not_found or rejected. NEEDS AN API KEY ON THE PRO PLAN.
include adds sub-lists to every found domain: addresses (the same address objects as domain_detail, with network), certificates, timing. Each one lowers the per-call domain cap because the reply is held in memory; the reply's limit says what applied. A sub-list whose query failed is named in include_failed, so an empty sub-list otherwise means none held.
Inputs: domains (required), include.
new_domainsNewly registered domainsRead-onlyIdempotentInspect
Newly registered domains from the ICANN zone-file feeds, oldest first from a cursor. NEEDS AN API KEY ON THE PRO PLAN.
ASCENDING AND CURSOR-PAGED, which is what makes it safe to resume: pass the next_cursor from the previous call as "after" and you continue exactly where you stopped, with no gap, however long you were away. Omit "after" to start about 48 hours back. caught_up true means this page reached the end of what is available, not that the feed has ended: store next_cursor and call again later.
since/until bound the window and tld narrows it to one TLD. Set certified true to restrict to newly registered domains that have SINCE been seen in a certificate, and max_hours_to_cert to how quickly: a domain registered and certified within a short window is a common pattern in phishing infrastructure. It is a pattern, not a finding; plenty of legitimate deployments look the same.
Inputs: tld, after, limit, since, +3 more. Returns: tld, count, window, domains, +4 more
provisioningDomains provisioned in one burstRead-onlyIdempotentInspect
Domains whose registration, first certificate and first DNS answer cluster inside a short window: the shape of infrastructure stood up in one go. NEEDS AN API KEY ON THE PRO PLAN.
max_hours_to_cert bounds registration to certificate and cert_to_dns_max bounds certificate to first answer, both in hours. first_dns_answer is bounded by our own scan latency, so within 24 hours of registration only some candidates have one yet; the reply's coverage says how many. tld, ns, since and until narrow it; page with after=<next_cursor>. A tight cluster is a pattern, not a finding.
Inputs: ns, tld, after, limit, +5 more.
recent_certificatesRecently logged certificatesRead-onlyIdempotentInspect
Certificates as they were logged, newest first, from a rolling 30-minute window.
This is a live tap, not a search: it answers "what is being issued right now", and there is no way to page backwards through it. A name that was logged an hour ago will not appear. To ask about a specific domain use lookup_domain instead.
Each entry gives the issuer organisation, the first DNS name on the certificate, and how many names that certificate covers — a high name_count is a shared or wildcard certificate covering many hosts.
Inputs: limit. Returns: count, window, certificates
search_domainsSearch domains by name patternRead-onlyIdempotentInspect
Registrable domains whose name matches a pattern, written forwards: agent.com, loop-.com, [a-z]{4,10}agent.com. NEEDS AN API KEY ON THE PRO PLAN.
Naming the TLD makes the search a key range and about 60 times cheaper than a pattern that leaves it open. Every row carries its nameservers (ns) and cert_id; ns narrows the search to domains delegated to a nameserver. Page with after=<next_cursor>. A match is a name that fits the pattern, not evidence of intent: lookalike names are also registered defensively by the brands they resemble.
Inputs: name (required), ns, after, limit.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Certificate Transparency search: subdomains, certificate history and hostname keyword search.
Parsed WHOIS, RDAP, DNS, certificates, nameservers and domain history for any domain.
Passive OSINT and security recon: DNS, TLS, email posture, IP reputation, CVE/KEV, CT logs.
WHOIS/RDAP, DNS, SSL, live subdomains with IPs, and SPF/DMARC/DKIM for any domain.
Related MCP Servers
- AlicenseAqualityBmaintenanceEnables passive subdomain enumeration from certificate transparency logs and DNS, with host resolution, certificate history, and attack-surface summaries for authorized security reconnaissance.4MIT
- AlicenseNot gradedqualityCmaintenanceEnables searching Certificate Transparency logs for TLS certificates issued for a domain and its subdomains, retrieving certificate details like issuer, validity, serial, and SANs, and looking up individual certificates by ID or serial.59 npmMIT
- AlicenseAqualityBmaintenanceSpot what companies are about to launch from new subdomains in certificate transparency logs (crt.sh). No API keys.5MIT
- AlicenseAqualityDmaintenanceDomain intelligence for DNS, WHOIS/RDAP, SSL/TLS, subdomain discovery, availability, valuation, email security, and typosquatting and brand protection.12MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.