TLDTrack helps you identify which websites depend on your servers by suggesting domain-to-server links from DNS and displaying the associated server on the domain's page.
For an agency or web team, start with a practical goal: choose a server and produce a reviewed list of the websites to check if that server needs attention. Keep suggested relationships separate from confirmed ones, and record anything you still need to investigate. Use the workflow below to build that list without treating an initial match as the final answer.
Where should I start mapping websites to servers?
Begin with a server inventory rather than a list of website addresses alone. For each server, record the cloud account, provider, server name, IP addresses and the person responsible for it. Then work through the websites you manage and review their relationship to that inventory.
TLDTrack connects to AWS, Azure and DigitalOcean accounts using read-only access, discovers servers and databases, and updates the inventory as resources are added or removed.
Before reviewing domain links, check that you have included every account within the scope of your work. For a client portfolio, agree whether that scope includes production sites only or also staging and development sites. Give similarly named servers clear labels in your working notes so you do not confuse one client's infrastructure with another's.
How should I review suggested domain links?
Use TLDTrack's DNS-based suggestions as a starting point for review. Ask the person responsible for the hosting setup to confirm each relationship before relying on it for maintenance planning or client communication. Do not label a suggested link as confirmed simply because it appears in the initial review.
For your own dependency register, use a spreadsheet or another shared record with these fields:
- Website and client: record the domain, client name and whether the site is production, staging or development.
- Infrastructure: record the provider, account and server identifier, plus any database relationship you have verified separately.
- Verification: mark the relationship as suggested, confirmed or unresolved, with a review date and reviewer.
- Response: name the technical owner, client contact and first website checks to carry out.
Keep unresolved entries visible. Assign each one to a named person rather than leaving a blank field that could be mistaken for a completed check. For database relationships, request confirmation from the person responsible for the application rather than assuming the domain suggestion establishes that relationship too.
What if my websites are on a WHM/cPanel server?
For WHM/cPanel hosting, TLDTrack lists the server's cPanel accounts and lets you choose which domains to import, with optional addon, parked and subdomains. Imported domains are grouped by server, and new accounts appear for you to add.
If this matches your hosting setup, review the WHM/cPanel integration before starting a separate manual inventory. Decide explicitly whether to include the optional domains, then reconcile the selected accounts with your client list.
How do I use the map when a server needs attention?
TLDTrack checks supported cloud servers and databases every five minutes and sends an alert when a resource stops or fails.
When investigating an alert, use the reviewed dependency register to decide which websites to inspect first. Treat the register as a checking list, not a declaration that every listed website is down. Check the websites themselves before describing the impact to clients.
- Identify the affected resource by provider, account and server identifier.
- Review its confirmed website relationships and investigate any unresolved entries.
- Check the relevant websites and important journeys, then record what is actually affected.
- Contact the responsible technical owner and send clients a factual update based on those checks.
When should I review the dependencies again?
Make a dependency review part of your handover checklist whenever you move a website, change its hosting or retire a server. Revisit the unresolved entries during routine portfolio reviews, and date each confirmation. Before planned maintenance, ask a colleague to check the affected-site list rather than relying solely on an older record.
Start with one server and the websites you believe it supports. Review TLDTrack's cloud server monitoring, connect the relevant account and work through the suggested domain relationships before expanding the exercise across your portfolio.
