How custom domains are kept safe
How Delsivo checks that a domain is yours before connecting it, re-checks it daily, and stops sending founders to a domain that lapses.
Putting your portal on your own domain means founders type and trust an address you control. Delsivo checks that the domain is really yours before connecting it, keeps checking while it's live, and stops sending founders there if it stops being yours. To set one up, see connect your own domain.
Ownership is proved before anything is connected
When an Admin adds a domain, Delsivo gives your fund a TXT record to publish at _delsivo.<your domain>. The domain isn't connected to anything until two separate DNS services both see that exact value. A record that only one of them sees, or a value given to someone else, doesn't count.
This stops anyone from claiming a domain they don't control. The value is generated for your fund and that domain, so a record published for another fund, or for an earlier attempt that was removed, doesn't work for a new claim.
One domain, one fund
A domain can be connected to only one fund portal on Delsivo. If you try to add a domain another fund uses, you see That domain is connected to another portal on Delsivo. If it belongs to your fund, contact support. Delsivo also keeps a list of domains that can't be used, such as lookalikes of Delsivo or of other organisations.
Daily checks and lapsed domains
A domain your fund stops renewing can be registered by someone else. If we kept sending founders there, they could land on a site you don't control. To prevent this, every live domain is checked once a day:
| What we check | If it's wrong |
|---|---|
| Your TXT record is still published | Counted as a failed check |
| The domain still points at Delsivo | Counted as a failed check |
| After | What happens |
|---|---|
| A failed check | The domain stays live; the side panel in Settings → Domains says what's wrong |
| 3 days of failed checks | The domain shows Needs attention. Links and emails to founders use your delsivo.app address straight away |
| 14 more days | The domain is disconnected. Add it again once its DNS is fixed |
If the records come back before then, the next check brings the domain back to Live.
What answers on your domain
- HTTPS only. Each domain gets its own certificate. Before a domain goes live we check over HTTPS that your portal, and no other, answers on it.
- Portal pages only. Your application form, the founder workspace and guest links answer on your domain. The investor workspace, the Delsivo backoffice and staff sign-in never do: those paths simply don't exist there.
- Your other addresses redirect. Only your chosen primary address serves pages. The others send founders there, so links in emails always point at one address you chose, never at whatever address someone typed.
- Separate sign-in per address. Founder sessions are tied to the address they signed in on and can't be reused on another fund's portal.
- Bot protection works on your domain too. Live custom domains are added to the bot check on your application form.
Who can change domains
Only fund Admins can add, remove or change the primary address. Every change is recorded in the activity log with who made it and when. The Delsivo team can disconnect a domain or suspend a portal if it's reported for abuse, and records why.
Frequently asked questions
Is the TXT value a secret?
No. It's published in your DNS for anyone to see. It only proves ownership for your fund and that domain.
Can I delete the TXT record once the domain is live?
Keep it. The daily check looks for it, and removing it counts as a failed check.
We're moving our DNS to another provider. What should we do?
Copy the TXT and CNAME (or A) records to the new provider before you switch. If the records are missing for less than 3 days, nothing changes for founders.
Something unclear or missing? Tell us