Skip to content
Tidehawk Docs

Add domains

A domain in Tidehawk is a hostname and a port that you want watched. Adding one starts a certificate scan and a registry expiry lookup for it.

The hostname and port model

Section titled “The hostname and port model”

Each tracked domain is a pair: the hostname, and the port Tidehawk connects to for the active TLS scan. The port defaults to 443 and is written as a suffix when it is anything else.

example.com
mail.example.com:25
portal.example.com:8443

Hostnames are normalised before they are stored. They are lower-cased, a trailing dot is removed, and international domain names are converted to their ASCII form, so Example.COM. and example.com are the same domain.

Two things are rejected outright. An IP address is not a domain, and a single-label name such as localhost or an internal server name is not a fully qualified domain. Tidehawk also checks the ending against the real list of top-level domains, so a typo like example.con is caught at the point of entry and, where it can, the message suggests what you meant.

Add domains to an existing client

Section titled “Add domains to an existing client”
  1. Open the client.
  2. Select Add Domains.
  3. Enter one hostname per line, with an optional :port suffix.
  4. Select Add domains.

The result tells you how many were added, how many were skipped, and lists any line that could not be used. Add more keeps the box open; Done closes it and refreshes the client.

You can also add domains while creating the client. See add a client.

What counts as a duplicate

Section titled “What counts as a duplicate”

A hostname and port pair that your workspace already tracks is a duplicate. Re-adding it does nothing: the existing domain is kept and the line is reported as skipped rather than treated as an error. Repeating the same line twice in one paste is skipped the same way.

The same hostname on two different ports is not a duplicate. example.com and example.com:8443 are two separate tracked domains.

What counts as an overlap

Section titled “What counts as an overlap”

An overlap is a new hostname that sits inside, or contains, the subdomain tree of a domain your workspace already tracks. Adding mail.example.com when example.com is already tracked is an overlap, and so is adding example.com when mail.example.com is already tracked.

Overlaps are refused, and the message names the existing hostname and the client that holds it. Nothing is added: a bulk paste containing one overlap adds none of its lines, so you never end up with a half-applied batch.

The reason is that certificate transparency lookups cover the whole subdomain tree from the parent, so a tracked parent already finds the child’s certificates. Tracking both would mean scanning the same tree twice and attributing the same certificates in two places.

One registrable domain per client

Section titled “One registrable domain per client”

Every hostname on a client must share the same registrable domain, the part you actually register, such as acme.com or acme.co.uk. Adding a hostname whose registrable domain is new to that client is refused with a message naming both, and the suggested fix is to create a separate client for it.

Removing a domain

Section titled “Removing a domain”

On the client’s Domains tab, select Delete on the row and confirm. The confirmation says the domain will be removed from the client and that certificates already discovered stay in the inventory. It does not delete those certificates.

Section titled “Related”