A claim is free and narrowly defined

A claim associates a representative’s account with a listed tool after evidence of domain control. It does not certify the business, validate every product claim or let the representative bypass editorial review. Payment for review or sponsorship neither proves control nor resolves a competing claim. An ordinary existing but unclaimed listing can use the self-service claim path.

Sign in, choose the exact listed tool and begin a claim. The challenge belongs to your account and that domain. Do not reuse a token from a screenshot, another account or a different tool. Do not share your registrar password, mailbox password or API key with SendCost.

Publish the challenge, then request verification

The claim screen provides a unique token, its expiry and the permitted DNS or website-file method. Follow the displayed name or path exactly. With DNS, create the required TXT record in the domain’s authoritative DNS service. With the file method, serve the exact challenge through the specified HTTPS path on the authorized public host.

Ask the person who controls DNS or the website to perform this step if it is outside your role. DNS propagation and hosting caches can delay visibility. The verification must observe the current token; a screenshot saying a record exists is not equivalent to a successful check. Expired challenges must be renewed rather than treated as permanent proof.

Understand failure and conflict

A failed verification gives a reason that you can address, such as a missing value or expired challenge. Check the domain, record name, token and method before trying again. SendCost does not follow arbitrary proof URLs into private networks. A redirect to another host or an inaccessible proof file does not establish control through the file method.

If another account already controls the listing, the conflict enters review. Do not replace someone else’s claim through payment or a repeated request. Supporting business documents can help explain a dispute, but they cannot alone substitute for current domain-control evidence. The editor may request a new challenge or other controlled resolution.

After a successful claim

You can suggest changes to the associated profile and respond to evidence requests. An editor still verifies material facts, prices, source dates and plan restrictions. A domain-control badge must not be described as SendCost having tested the product or endorsed a commercial relationship.

Keep your account secure and tell support if control changes or your access should be removed. Use the contact route for a disputed association, with the listing and claim reference. Avoid uploading unrelated personal records. Historical payment, editorial and sponsorship records retain their own status when a claim changes; control is one independent part of the service.

Before you retry the challenge

Copy the current record name or file path and the token from your own claim screen. Check the displayed expiry. Ask the DNS or hosting administrator to confirm the public result, not just that the value exists in an internal dashboard. If the challenge has expired, create a fresh challenge and replace the old value.

A verified representative can suggest facts through the contribution route. Keep the exact listing reference when requesting a correction or reporting a conflicting association. Never send an account password or registrar API key to resolve it.

Source-based editorial research. Vendor terms can change; confirm the current contract before purchase.

Continue your research