WHEN THE RECORD DOES NOT MATCH THE EXPECTATION
Find the failing layer.
Use the narrowest observation you have. A handle, identity directory, hosting endpoint, app session and media file can fail independently. These are diagnostic examples, not reports of incidents in your account.
“The handle resolves, but the reverse check fails.”
The address reader first resolves a readable handle to a DID, then checks whether that DID document names the same handle. AT Protocol requires this two-way relationship for handle verification; see the handle specification. One direction working does not settle the other.
Check for a typo or an old provider-owned name. If you recently changed a handle, compare the currently intended name with the latest saved observation, then use the provider’s official handle instructions. Do not replace unrelated DNS records or remove mail records. Hostpost does not edit DNS and cannot measure how long every resolver will retain an older answer.
“The reader cannot reach the public resolver.”
That means this lookup did not produce a fresh result. It does not establish that your account disappeared. The previous displayed address is retained and labelled as previous. Avoid saving it under a new date as if it were a successful read.
Try the public profile in your normal browser and consult official service status. A network filter, service response or unsupported identity method can also prevent this particular reader from working. This tool supports did:plc; a did:web identity requires a different resolution path.
“The PDS changed, but an old photo is missing.”
A hosting endpoint is an address, not an inventory. Record one affected public post URL and whether its text, thumbnail and full media each load. Compare a recent post with an older example. If the migration UI still indicates copying, keep that fact beside the observation.
Send the specific example to official support. Repeatedly creating accounts or launching moves obscures the original state. The comparison file can document the public address change while your media note documents the separate issue.
“A public page works, but my app does not.”
Public viewing and authenticated app access are different tests. Record the app name, version, time and exact error. Follow that app’s official instructions for a moved account or session renewal. Do not paste app passwords, access tokens or recovery codes into a public checker.
Fictional example: Sol can open a post without signing in, while a phone app shows an account error. This narrows the investigation to the app/session path; it does not demonstrate that the hosting move rolled back.
“Two files show different identities.”
Check the handles, dates and whether either file was captured from a newly created account. A display name is not unique. If the DID differs, report different identities even when the avatar and name match. The three account-change specimens explain rename, move and new-account cases side by side.
Start with a fresh read only when the service can actually be reached. Keep the first file unchanged so the discrepancy remains inspectable. Return to the migration evidence procedure →