This is a walkthrough of Alex’s fictional report. Every finding and source is invented to demonstrate the experience. No real person was scanned.
An example, with the evidence kept in view. Source addresses ending in .example are fictional and don’t open live pages.
02Example matched sources
01Example uncertain match
04Source families explained
The picture at a glance
In this example, an older profile and an event page connect different parts of Alex’s public history. Neither finding proves that someone has looked at those pages. A separate name match needs review before it belongs in the picture.
The findings, source by source
Public profiles
An old profile still shows a former location
Example match
In this fictional example, a public profile still connects Alex’s name to an earlier city. The profile’s contact link is also visible to visitors.
Example community profileExample only
community.example/alexPublication date unavailable · Observed in example: 25 September 2026
Why this match needs this label
The fictional customer confirmed ownership of this profile.
The profile name agrees with the verified name.
The location is historical context, not a claim about where Alex lives now.
A practical next step
Open the original profile, review its public visibility settings, and remove details you no longer want to share.
Web mentions
An event page connects a name with professional history
Example match
A fictional event programme lists Alex as a speaker. It connects a name, role, and a former organisation in a single public page.
Example event programmeExample only
events.example/programmeExample publication: March 2024 · Observed in example: 25 September 2026
Why this match needs this label
A link from the customer’s verified profile points to this example page.
The customer confirmed the professional context.
Finding the page now would not make it a newly published page.
A practical next step
Check whether the details are still accurate. If a correction is needed, use the publisher’s official contact route.
Possible matches
A similar name appears in a separate listing
Possible match
This example listing shares a name but has no reliable link to the fictional customer. It is kept separate from confirmed findings and from change alerts.
Example public directoryExample only
directory.example/listingPublication date unavailable · Observed in example: 25 September 2026
Why this match needs this label
Name similarity alone is insufficient.
No verified profile connects this listing to the customer.
It must not contribute to a confirmed-finding summary.
A practical next step
Review the source when available. Mark it as someone else if it is not you; don’t supply more personal information to the publisher just to investigate.
What was—and wasn’t—checked
A real report will show the actual status of each source. This table illustrates how gaps stay visible rather than disappearing into a summary.
SOURCE FAMILY
EXAMPLE STATUS
Public profiles
Checked · one example
Indexed web mentions
Checked · one example
Public directory
Checked · uncertain match
Archived pages
Unavailable · not evidence of absence
Private accounts, private messages, and information behind unsupported access restrictions are outside this example. A limited result is not a guarantee that nothing else exists.
A SNAPSHOT IS A STARTING POINT
What shows up next?
The planned monitoring options let you compare future scans with your previous report. Weekly monitoring will add alerts when a completed scan finds a meaningful change.