Delisting

You can ask us to stop showing your endpoint on this site. This page says what that achieves and what it does not, because the difference is real and a page that implied otherwise would be promising something we cannot deliver.

What we will do

Write to [email protected] from an address at the domain in question.

What we cannot do, stated plainly

Delisting cannot un-publish history. It removes a server from this site going forward. It does not reach the snapshots already published, and it cannot, for a reason that is structural rather than a matter of willingness.

Each published snapshot commits to its records through a single root, published at the time it was made. Every record inside that snapshot contributes to that root. So an already-published observation of an endpoint remains committed to by a root that is already in public hands — removing the row now would change the root, and a root that changes is not a commitment. The archive can grow. It cannot retract.

Two further limits worth knowing, since they are the ones people are surprised by:

What we will not pretend

We are not going to write that we will delete all data about a server on request. It would read better and it would be false. The honest offer is the one above: we control what this site shows going forward, and we do not control what has already been published — including by us.

If the problem is that a specific observation is wrong rather than that you would prefer not to appear, corrections is the better route: a correction carried forward is more useful to you than a removal, because it leaves the record saying something accurate rather than saying nothing.