Try the TrueLink exact-address example
Compare a submitted URL with an example record of declared business destinations.
A practical buying guide
TrueLink publishes a business record after a DNS domain-control check. Customers can compare the complete submitted URL with the destinations in that record, including paths, queries and fragments.
A business wants a shareable source record for customers checking its website and booking links.
Worked planning example · fictional data
Illustrative URL review using a reserved example domain: a business publishes a booking page and later receives a link with a different path.
Matching the hostname alone does not make these complete URLs identical.
Confirm which destination the business intends to declare. An unlisted URL needs checking with the business; a mismatch alone does not prove fraud.
A match confirms the address is declared in that record; it does not guarantee safety or independently verify social account ownership. A mismatch is not proof of fraud.
It establishes that the complete submitted URL matches a destination declared in the current business record by the domain controller. Compare the path, query and fragment as well as the domain. A match does not independently certify the legal identity of the business, inspect a destination for malware or guarantee that a future page remains unchanged.
Link to this answerReview the destination whenever a booking page, social profile or payment route changes. Check the full address and the record revision that customers will see. TrueLink provides domain-control evidence and publication controls; agree who maintains the record and removes obsolete links before sharing it from customer-facing pages.
Link to this answerThe path, query and fragment can identify different destinations even when the domain is identical. Compare the complete submitted address with the declared TrueLink destination. Use a fictional booking link and a changed query in the demonstration so staff can explain the result without reducing the check to the domain name alone.
Link to this answerConfirm the new complete destination with the domain controller, update the declared record through the supported process and review the published result. Then check customer-facing buttons and printed materials that still use the old link. Updating a declaration does not automatically replace every copy of the address elsewhere.
Link to this answerExplain that the submitted address was not an exact match to the destinations in the current record. Check for an outdated address or a meaningful path or query difference. Do not call the destination fraudulent solely because it is unmatched; ask the business to confirm its intended destination through an established channel.
Link to this answerKeep the approved destinations, the responsible owner and the revision that customers were directed to use. Review the supported domain-control evidence and its freshness in TrueLink. The record is a statement by the domain controller, so staff should distinguish that evidence from independent checks of legal identity, account ownership or website safety.
Link to this answerCheck the scheme, domain, path, query and fragment against the current declared destination. A familiar domain alone is not the complete address.
Link to this answerCheck the full intended address with the business owner and update the authorised record process. Explain a match as a declaration, not a guarantee of payment safety.
Link to this answerCompare the complete changed address with the declared one and inspect the result. The exercise tests exact destination matching rather than broad domain similarity.
Link to this answerNo. The record reflects what the domain controller declared. Independent account ownership and destination safety are separate questions.
Link to this answerCheck the current record and complete address, then investigate through the business's procedure. A mismatch alone is not proof of fraud.
Link to this answerIdentify the authorised domain administrator and confirm access before setup. Publication depends on current domain evidence and an active subscription.
Link to this answerUpdate the declared address through the authorised process and test the current public record. Check customer-facing references that still use the old destination.
Link to this answerThe published scope does not include monitoring or takedowns. Evaluate domain-control evidence, record publication and exact URL checks against your actual requirement.
Link to this answerName the domain administrator and record maintainer, review current destinations and agree the update process. Include the record in normal operational handover.
Link to this answerWhether the submitted address matches a destination in the current record. Explain the result's scope without turning a match into a general safety certification.
Link to this answerCompare a submitted URL with an example record of declared business destinations.
Review the distinction between domain control, a declared URL and a wider identity or safety claim.
Prepare your country, language and handover requirements with a relevant regional checklist. Each section is also available in Arabic.
VCMP TrueLink publishes a domain-controlled business record so customers can compare submitted URLs with the destinations its controller has declared.
Explore VCMP TrueLinkSolo by VCMP brings a business website, online bookings, customer records, quotes and invoices into one workspace for independent service businesses.
Explore Solo by VCMPVCMP Growth helps businesses organise contacts, research opportunities and prepare campaign drafts in a focused outreach workspace.
Explore VCMP GrowthHelp us improve VCMP
We use optional analytics cookies to understand which pages people visit and how they discover VCMP. We do not use these analytics cookies unless you accept them.
Read our privacy policy