Keep the full Mastodon account address and the actual public profile link in separate fields. Their domains can legitimately differ. Use the exact shared address or link for an ordinary Mastodon lookup; do not replace the handle domain with the browser host or invent a profile URL. Record whether the permitted lookup leads to the supplied profile, or whether the pairing remains unresolved.
Find public social profile clues with our TraceSeek app.
Split the two identifiers before comparing anything
A Mastodon account address has a local username and a handle domain. A profile web address is a link in a browser, and its host can legitimately differ from the handle domain because an installation may serve account addresses on one domain and the web interface on another. Write the supplied address in one column and the actual public link in another. Keep the username exactly as given; never swap in the browser host, and never assemble a link from the address by yourself. [Mastodon documentation: federation and display configuration]
A two-column comparison using a hypothetical example
Suppose, purely hypothetically, your date shares the address @sam@example.com and a profile link whose host is social.example.net. The correct record is: handle field @sam@example.com, web-host field social.example.net, and a note that the contact supplied both together. That pairing is an observation about what you were given. It is not independent corroboration, because both identifiers came from the same person in the same conversation, and it is not proof of identity, ownership or intent.
| observation | limit | next step |
|---|---|---|
| The supplied address and the actual public link use different domains | A domain difference alone neither confirms nor contradicts the pairing | Record both fields exactly; don't reconcile them by editing either one |
| The shared username appears in the address and, if you open the link, in the profile | This is consistency of presentation, not verification of the person | Ask the contact to confirm which public link is current if anything is unclear |
Why you must not rebuild the link from the address
Mastodon documents lookup using a full username@domain address or a known direct HTTPS profile address. Use the exact input your date shared in ordinary Mastodon search, if available to you, and compare the returned public profile reference with the supplied link. Different implementations can structure account URLs differently, so constructing a path yourself can point to the wrong object. A shared local username alone is not enough to connect the two references. [Mastodon documentation: WebFinger]
Record a resolved destination or an unresolved pairing
Separate three outcomes. If your date merely supplied both strings, record only that they were supplied together. If a permitted lookup of the full account address leads to the supplied public profile, record that observed address-to-profile association. If the address does not resolve, the result is restricted, or the references remain inconsistent, leave the pairing unresolved. In that last case, ask your existing dating contact to confirm the intended current public link.
- Keep both original strings and the observed lookup result in a short dated note.
- Do not treat a matching local name or a domain difference as evidence of another account.
- An observed account association does not confirm who is in the dating chat.
A couple more questions
Does a different domain mean my date gave me two accounts?
Not by itself. An installation can use one domain in account addresses and another for the web interface, so record the handle domain and the browser host as separate fields rather than counting two accounts.
Should I retype the profile link to match the handle domain?
No. Use the address and link exactly as supplied; rebuilding a profile URL from a username risks creating a false match, and the reconstructed link is no longer what your date shared.
Does a matching public profile prove who is in the dating chat?
No. A public candidate found from a voluntarily shared username is not identity, ownership or fidelity proof; it only shows what is publicly presented under that name.
Sources & editorial notes
Official references checked on October 25, 2026. Checklists, comparison tables and example wording are DateClues editorial tools, not official tests or validated risk scores.
General information. No guide or tool can certify a person’s identity, intentions or safety. Read our editorial standards.