Custom Domains
Serve your service-desk portal from your own hostname, with a managed TLS certificate and DNS ownership checks that keep running after go-live.
The problem
You have spent years teaching clients that your company is the one that fixes their computers. Then you send them to a portal at someone else’s address, on someone else’s brand, and every password reset email points there too. For an MSP that is not a cosmetic problem — it is your client relationship being brokered by a vendor your client has never heard of.
The usual fix is a CNAME and a support ticket to your platform vendor, followed by a wait for someone to install a certificate. Nine months later the certificate expires, or a client changes registrars and quietly deletes the record, and nobody finds out until a customer calls to say the portal is throwing a security warning.
What Solidlio does about it
You add a hostname yourself and get two DNS records to publish: a CNAME and a TXT carrying a random ownership token issued for that domain alone. A job runs every five minutes to move domains through provisioning and to re-check the ones already live. Transient DNS errors are ignored, so a resolver blip never takes a working portal offline.
Capabilities
| Capability | What it does |
|---|---|
| Self-service domain setup | Add a hostname and get both DNS records on screen, each with a copy button. |
| Two-record ownership proof | Requires a matching CNAME and a matching TXT before a domain advances — on the button and in the background job. |
| Per-domain random token | Each domain gets its own 24-byte secret, so knowing a hostname never lets anyone else guess its proof. |
| Live provisioning status | A four-step pipeline on screen, refreshing every 30 seconds while a domain is in transition. |
| Continuous re-verification | Active domains are re-checked every 5 minutes and revoked after 3 consecutive definitive failures. |
| Transient-failure immunity | Timeouts and server failures never count against a domain — only ENOTFOUND and ENODATA do. |
| Hostname reclaim | Removing a domain releases the hostname and re-keys its token, so the next holder must prove ownership again. |
| Plan-aware allowance | The screen shows the allowance your plan actually grants, and refuses with an upgrade offer rather than an error. |
| Verified sending domains | Claim an email domain by TXT record to control email sending and domain-based auto-join, re-checked daily. |
Built for MSPs and their clients
A managed client is a separate tenant with its own account, so an MSP and its clients each hold their own domains under their own plans — and an MSP that brands a portal per client needs more than one.
| Organization | MSP | |
|---|---|---|
| Whose hostname | Its own, on its own portal | Its own, plus one per branded client portal |
| Who administers | The organization’s own administrators | The MSP’s administrators, for the MSP’s own domains |
| Default allowance | 1 on a plan that includes the feature | 5 on a plan that includes the feature |
| Entitlement | Its own plan, or the managing MSP’s if it holds no plan | Its own plan |
| Branding served | Platform → MSP → Organization cascade | The MSP’s brand reaches the client portals it pays to brand |
How it works
- Add the hostname — enter
portal.yourcompany.comin Settings. The domain is pinned to your organization so it can resolve, and issued its own ownership token. - Both are shown with copy buttons.
- Verify — Solidlio checks both. If either fails, the response names which one, and the domain stays where it is.
- The screen flags that the TXT value has changed and shows the new one.
- Stays live — the same job re-checks the domain every five minutes for as long as it exists.
Compliance and audit
Every domain row records who owns it, when it was created, when it was last checked, when it was verified, its current certificate state, and the text of the most recent provisioning failure. Removal is a soft delete: the record is retained as DEACTIVATED rather than erased, so a hostname’s history survives its removal.
Turning on a custom domain requires a complete CAN-SPAM/CASL sender identity — legal name, physical address and contact details — for the entity the domain actually brands, checked before any DNS lookup is performed. A brand Solidlio could not legally attribute to a real company is never served.
Ownership verification that falls back to fetching a well-known file will only retrieve a public, registrable hostname whose every resolved address is publicly routable, and never follows redirects.
Editions
MSP partner plans
| Capability | Free | Starter | Growth | Scale | Enterprise |
|---|---|---|---|---|---|
| Custom portal domains | 0 | 0 | 0 | 5 | unlimited |
| Managed TLS certificate | — | — | — | ● | ● |
| Continuous re-verification | — | — | — | ● | ● |
| Verified sending domains | 1 | 2 | 5 | 10 | unlimited |
Direct-customer plans
| Capability | Free | Essentials | Professional | Business | Enterprise |
|---|---|---|---|---|---|
| Custom portal domains | 0 | 0 | 0 | 1 | unlimited |
| Managed TLS certificate | — | — | — | ● | ● |
| Continuous re-verification | — | — | — | ● | ● |
| Verified sending domains | 1 | 1 | 3 | 5 | unlimited |
Domain counts are read from each tier’s maxCustomDomains limit. If a tier grants custom domains but sets no limit, the fallback allowance is 5 for MSP partner plans and 1 for direct-customer plans. A managed client with no plan of its own inherits its managing MSP’s entitlement.
Your clients should see your name, not ours.