Every hosting customer leaves a trail of public signals about what they are doing with their website: where their DNS points, who handles their email, what the site is built with, when the domain renews. Most hosts never look at it. The ones that do can time an offer to the week a customer actually needs it, which is the difference between an upsell that converts and one that gets unsubscribed. This guide covers which signals matter and how to act on them.
The principle: offer at the moment of need
An upsell email sent to everyone on the first of the month converts at a fraction of a percent. The same offer sent to the customer whose domain renews in ten days, whose email is on a free provider, and whose site just installed a commerce plugin converts because it is relevant. Domain intelligence is about finding those moments from data you can observe without asking.
Signals you can read
DNS records. Where the A, CNAME, MX, and TXT records point tells you who is serving the site, handling the mail, and which third-party services are verified (marketing tools, payment providers, Google or Microsoft workspaces). A customer hosting with you but pointing MX elsewhere is an email opportunity. A customer whose A record left your range is a churn alert, not an upsell.
WHOIS and registration data. Renewal dates, registrar, and whether privacy is enabled. A domain renewing in 30 days at another registrar is a transfer-in offer. A newly registered second domain under the same contact suggests a new project, which is a build or migration opportunity.
Tech stack fingerprint. Which CMS, builder, and plugins the site runs, visible from HTML and headers. A WordPress site with a commerce plugin and no caching layer needs a speed tune-up. A site still on a page builder you are phasing out needs a migration offer before it breaks. A site with an abandoned plugin version is a care plan conversation.
Certificate and security posture. Expiring or mismatched certificates, missing security headers, exposed version strings. These are both support prevention and a natural hook for hardening or care.
Site vitals over time. Traffic changes, page count growth, new subdomains. A site that doubled its pages in a quarter is a business that is growing and will buy services.
Turning signals into offers
Map each signal to one offer and one timing window. Keep the table short; three to five rules that run reliably beat twenty that nobody maintains.
| Signal | Offer | When to send |
|---|---|---|
| MX records on a free or consumer provider | Business email on their domain | Immediately, then at domain renewal |
| Domain at another registrar, renewal within 45 days | Transfer-in with a renewal credit | 30 days before expiry |
| New domain registered by an existing customer | Site build, or a second hosting plan | Within a week of registration |
| Commerce plugin detected, no caching or CDN | Speed tune-up, then care plan | Within days of detection |
| Outdated core, PHP, or major plugin | Care plan with an update report preview | Once, then monthly if unresolved |
| Traffic up sharply quarter over quarter | Plan upgrade, SEO retainer | At the next billing cycle |
| Builder or theme at end of life | Migration or redesign | Three months before end of support |
Deliver the offer where the customer is already looking: a banner in the panel next to the relevant setting, a line in the monthly report, or a note from a named person for higher-value accounts. Email alone is the weakest channel.
Worked examples
The bakery with free email. Hosting plan with you, domain with you, MX pointing at a consumer mailbox. The signal is permanent until acted on. The offer is one mailbox on their domain, set up for them, shown on the domain management screen with a “set up in one click” button. Attach rates on this single rule often exceed everything else in a host’s upsell program combined.
The consultant who registered a second domain. Existing customer, new .com registered last week, no DNS set up yet. They have a project in mind. Offer a starter build or a free migration if the site exists elsewhere, with a link to order inside the panel. Timing is everything; two weeks later the domain is parked and forgotten.
The store that got busy. WooCommerce detected six months ago, traffic tripled in the last quarter, still on the entry plan with no caching. The signals compound: plan upgrade to prevent an outage, a speed tune-up, and a care plan because an unpatched commerce site with real traffic is a cleanup waiting to happen. Lead with the upgrade, because it protects their revenue, and follow with services.
Operating it responsibly
- Use public, observable data about domains and infrastructure. Do not scrape customers’ content or enrich with personal data from third parties.
- Make it easy to turn off recommendations.
- Never let a churn signal trigger a sales pitch. A customer moving away gets a human conversation, not an offer.
- Measure each rule separately: sends, conversions, and unsubscribes. Retire rules that annoy more than they convert.
What this needs from your stack
A scheduled scan of customer domains, a rules engine, and a way to surface offers in the panel and in reports. Hosts can build this; most do not, because it sits between the data team and the product team and belongs to neither.
shDI, Seahawk Infra’s domain intelligence platform, is the in-development product for exactly this: upsell intelligence for hosting customers from domain and infrastructure signals, delivered as prioritized offers inside the panel. It is in early access now.
Next step
If you want timed, signal-driven upsells without building the scanning and rules layer yourself, request early access to shDI. Bring your current upsell rules, even if they are three lines in a spreadsheet; the first job is to replace guessing with observed signals.