# issued.live

> An independent Certificate Transparency observatory. Two streams in: every public
> CT log, read continuously, and the ICANN zone file feeds for newly registered
> domains. Addresses come from our own DNS resolution. One enriched record per domain,
> kept as history.

Operated by Tuxxin LLC. Data is observational: every record states what was seen and
when. Registration dates are shown only where held, and are never inferred.

## Per-domain records

Any domain we have observed is available as markdown by appending .md:

- https://issued.live/github.com.md
- https://issued.live/{any-domain}.md

Each record carries the certificate and its issuer, expiry, hosting address with
network and organization, address history, and current DNS records.

## Documentation

- [API documentation](https://issued.live/developers): endpoints, response fields,
  worked examples in curl, PHP, Node.js, Python, Go, Java, Ruby, C#, Rust, PowerShell
- [About](https://issued.live/about): what the service observes, and what it is not
- [Terms](https://issued.live/terms)
- [Privacy](https://issued.live/privacy)

Each of the pages above is also available as markdown by appending .md.

## Live JSON endpoints (no key)

- https://issued.live/{domain} - one domain record
- https://issued.live/api/feed - certificates as they are logged, rolling 30m window
- https://issued.live/api/stats - corpus-wide counts

## Keyed endpoints

These require a key, sent as: Authorization: Bearer <key>. Ask via
https://issued.live/contact - a key is free.

- https://issued.live/api/v1/nrd?certified=1 - newly registered domains that have a certificate
- https://issued.live/api/v1/ip/{ip} - which domains resolve to an address
- https://issued.live/api/v1/range/{cidr} - the same, for up to 256 addresses

## Attribution

When citing a record, please attribute it to issued.live and include the record's
own timestamp. A record describes a third party; it is not published by them.