Privacy

What we collect from visitors, and what we publish about domains.

issued.live is operated by Tuxxin LLC. This page covers two separate things that are easy to confuse: information about you, the visitor, and information about domains, which is drawn from public sources.

Information about visitors

Analytics

We use two analytics systems.

Umami, self-hosted by us at analytics.tuxxin.net, counts page views. It is cookieless and does not track visitors across sites. It records the page visited, the referring page, and coarse details such as browser, operating system, screen size and country. It does not store your IP address, and we cannot use it to identify you.

We also record machine-facing requests on the server side, into a separate Umami property kept apart from browser traffic. This covers requests that run no JavaScript and therefore cannot be counted by the tag above: the JSON API, the .md surfaces, the export endpoints, the MCP server, and files such as robots.txt and llms.txt. For those requests we send the calling client's IP address and User-Agent to analytics.tuxxin.net, along with the path, the HTTP method and the response status. A browser visitor can opt out by blocking the analytics script, and an API client cannot. Tuxxin LLC operates both this site and analytics.tuxxin.net; no third party receives this data. We do not record page views by ordinary visitors this way, and the monitoring health check is excluded entirely.

Google Analytics 4 (measurement ID G-9QTD25PWZ7), operated by Google. Unlike Umami it does set cookies (see below) and it sends data to Google, who process it as described in Google's privacy policy. Google uses your IP address to derive approximate location and states that it does not log or store it in Google Analytics 4; we have no access to it either way. We do not enable Google Signals, advertising personalization, or ad remarketing.

To opt out of Google Analytics, install Google's browser opt-out add-on. Any tracker-blocking extension, or a browser sending Global Privacy Control, also blocks it.

Server logs

Our servers record requests for operational and abuse-prevention purposes: the URL requested, the response status, timing, and the requesting address. We keep these for at most 30 days and often less, because the log is also capped by size and rotates sooner when it fills. We do not use them to build profiles.

We log sign-in attempts the same way. A successful sign-in records the label of the API key used; a failed one records only the requesting address, so that repeated guessing can be rate-limited. The key itself is never written to a log, never placed in a URL, and never echoed back to the page. The server holds only its SHA-256, and compares a submitted key against that.

Cookies

Google Analytics sets cookies. They are first-party cookies named _ga and _ga_G-9QTD25PWZ7, they hold a randomly generated identifier used to recognize a returning browser and to group page views into a session, and they expire after about two years. They are not used for advertising and we do not join them to anything else.

Signing in sets two cookies, and only if you sign in. Browsing this site does not create a session. Nothing is set when you look up a domain, read a page, or open the sign-in form. Only a successful sign-in at /login writes them, and only for subscribers, who sign in with a code emailed to them.

It is named il_session. It contains an account number and an expiry time, signed so it cannot be altered. It does not contain your API key, your email address, your name, or any identifier we could use to track you across sites. We do not join it to analytics. It lasts 12 hours, or 30 days if you tick "stay signed in". It is marked HttpOnly (no script on the page can read it), Secure (never sent over an unencrypted connection) and SameSite=Lax (another site cannot use it to act as you). Signing out at /logout deletes it immediately, and so does clearing your site data.

The second is named il_signed_in, and its entire value is the character 1. It carries no account number, no identity and no expiry of its own, and it grants nothing: every page that shows account data checks the real session above, on our servers. It exists so the page itself can tell whether to write "My account" instead of "Sign in", and to leave out the sponsor slots for subscribers, who do not see ads. That is why it is the one cookie here not marked HttpOnly: the script on the page has to be able to read it. It is Secure and SameSite=Lax, it expires with your session, and signing out deletes it. If you are signed in and it has been cleared, the next page you load writes it again.

Nothing else served by issued.live sets a cookie. Umami is cookieless. The sponsor creative described below is a plain image served from issued.live, and sets nothing. The frame described above comes from worldip.io's servers rather than ours, and anything it stores is under its own domain.

The light/dark toggle stores your choice in your browser's local storage under the key il-theme. That is not a cookie: it is never transmitted with a request, we cannot read it, and it holds nothing but the word light or dark. Clearing your browser's site data removes it.

If you hold an account

Accounts exist only for paid plans, and there is no password. We store your email address, your plan, your subscription status, and an API key. The email address is what the account is: it is how you sign in and the only way we can reach you about billing.

Sign-in codes. Signing in sends a six-digit code to your email, valid for fifteen minutes and usable once. We keep a short-lived record of the code's fingerprint and its expiry so it cannot be replayed, and we log the requesting address for failed attempts so that guessing can be rate-limited. We delete codes once they are used or expired.

Your API key. We store only a SHA-256 of the key, never the key itself. The API has always held keys this way. We can confirm a key is valid and see which account it belongs to; we cannot recover or re-display it. Rotating the key replaces the stored hash immediately.

Usage. We count requests made with your key for rate limiting and record them in the ordinary server logs described above, with the key's label rather than the key. We do not build a profile of the domains you look up, and we do not sell or share any of it.

Downloads. Each daily file carries one download per day, so we record which file your account took and on which day -- the file's name and date, your account number and a timestamp, and nothing about its contents. It is what makes the allowance work and what tells you a file was already taken. It is kept for the life of the account and is removed when the account is removed; ask us if you want it cleared sooner.

Payments

Payments are processed by PayPal. We never receive your card or bank details. Those go to PayPal directly, governed by PayPal's privacy statement. What we hold is the subscription identifier PayPal gives us, its status, the plan, the amounts and dates of payments, and the email address associated with the subscription. That is what the billing page shows you.

We keep payment records for as long as tax and accounting rules require, which is longer than the account itself. Closing an account does not erase the record that a payment was made.

If you close your account

Canceling a subscription ends billing. To have the account itself deleted, ask us at the contact form: we remove the email address, the key hash and the plan record, keeping only the payment history described above. Server logs age out within the 30 days described under Server logs.

The contact form

Messages you send through the contact form reach our support system at support.tuxxin.com. We keep what you send (your name, email address and message) for as long as needed to answer you and to keep a record of the exchange. We do not use it for marketing and do not sell it.

Third parties

Address enrichment on domain pages is provided by worldip.io, also operated by Tuxxin LLC. We query it from our servers for the network and location shown beside a domain's hosting address, so that lookup does not involve your browser.

Separately, the homepage and each domain page embed a "Your connection" widget served by worldip.io in a frame. Your browser loads that frame directly, so worldip.io receives your IP address and User-Agent and may set its own cookies or storage under its own domain. That is a different interaction from the server-side lookup above, and it is the one that involves you.

Sponsors and affiliate links

This site carries sponsor and affiliate slots on some pages, including the homepage, each domain page, the news index and each news post. We label them where they appear. Subscribers on either paid plan do not see them at all.

We serve the creative in a slot (its image and its wording) from issued.live itself, not from an ad network or the advertiser's own servers. There is no ad exchange, no real-time bidding and no third-party ad tag anywhere on the site, so loading a page that carries a slot does not contact the advertiser or its affiliate network, tells them nothing about you and sets nothing in your browser. If a slot is ever filled by a tag that loads in your browser from someone else's server, this page will say so before it does.

Clicking one is different. A sponsor link generally points at a third-party affiliate-tracking URL rather than straight at the advertiser's own site. Following it hands your browser to that third party, which receives your IP address, your User-Agent and the fact that you came from issued.live. It may set its own cookies or storage under its own domain to attribute the visit. Its privacy policy governs what it does with that, not this one. Nothing reaches it until you click.

We are paid for these placements, and some of them are affiliate links on which we earn a commission, per click or on a purchase you make afterwards. That payment buys an advertiser a slot and nothing else: what we publish about a domain is never for sale, is not sponsored, and is not influenced by anyone who advertises with us.

We do not sell personal information, and we do not share visitor data with advertisers. We pass no analytics data, server log or contact-form message to a sponsor or affiliate network. Such a party learns only what your own browser tells it when you follow a link. Google Analytics remains measurement only. Google Signals, advertising personalization and ad remarketing are switched off, and we ask Google to disable them on every page load as well as in our account settings.

Information about domains

We compile the records we publish from sources that are already public:

• Certificate Transparency logs: a public, append-only record that certificate authorities are required to publish.
• ICANN zone file feeds: the published zone data for newly registered domains.
• DNS: the answers domains return to ordinary public queries.

We do not perform intrusive scanning, do not attempt authentication anywhere, and do not collect content from the sites we record.

If a record concerns you

Registration data occasionally contains personal information, usually where an individual registered a domain without privacy protection. If a record we publish contains your personal data and you want it removed, contact us with the domain and what the record contains, and we will remove it from what we publish.

We cannot alter Certificate Transparency logs. They are append-only, run by third parties, and designed so entries cannot be withdrawn. Removing something from issued.live does not remove it from those logs, and the underlying entry remains publicly readable elsewhere.

Retention

We keep observational records as history: the service exists to say what a domain looked like at a point in time. Concretely: certificate detail is queryable live for 48 hours and every daily file we publish is archived permanently and remains searchable; a DNS answer is held for as long as the name still resolves, with 18 months of change history behind it; registration details and address history do not expire. We keep server logs for at most 30 days. We keep contact messages as long as needed to handle the matter.

Your rights

Depending on where you live, you may have rights to access, correct, delete or object to processing of your personal data. Ask via the contact form and we will respond.

Children

The service is not directed at children and we do not knowingly collect information from them.

Changes

We may update this page. The date below records when it last changed.

Contact

Last updated August 30, 2026.