Skip to content

Custom domains

A custom domain puts the handoff page on an address your users recognise — such as secure.yourcompany.com — matching your email footers. It’s a phishing defence: training can say “only ever type your password on this exact address.” For: Admins and Owners.

Custom domains need a paid plan and a verified organisation domain (Settings → Verification), so a trial can’t put a lookalike address in front of recipients.

  1. Go to Settings → Branding and find the Domains card (in MSP mode, open the client’s Branding page under Clients).
  2. Enter the hostname you want (e.g. secure.example.com), with Used for set to Public page.
  3. Add the two records SafeHanded shows you at your DNS provider (each has a copy button): a TXT record that proves you own the domain, and a CNAME that points the hostname at SafeHanded. On Cloudflare, set the CNAME to DNS only (grey cloud), not Proxied; a proxied record hides the CNAME and can’t be verified.
  4. SafeHanded checks the records straight away and then every 10 minutes until they’re found, and issues TLS automatically — no certificates to manage. You can also press Verify now. SafeHanded asks your domain’s own nameservers, so a new record is usually seen within a minute.

A hostname is reserved only once it’s verified. If more than one organisation adds the same hostname, the first to verify it keeps it and the others’ claims are removed. A claim that isn’t verified within 7 days expires; add the domain again to retry.

Until a domain is verified, links use SafeHanded’s own address (safehanded.com). Once it is, new links use your domain, and links on SafeHanded’s address keep working.

Verifying your organisation’s domain (Settings → Verification) also affects how your organisation is shown on the public link checker and handoff pages: a verified issuer is shown by name with its verified domain (with a Trial badge until you subscribe), which is what lets your users confirm a link is genuinely from you.