Exposure report

Phase 14 Test User

A stranger can connect too many dots too easily.

Low visibility Moderate linkage risk High clue density Critical exposure
Submitted
#15
Scan ID
Status
completed_stub
Pipeline state
Evidence cards
8
Captured data points
Action plan
5
Recommended tasks
Exposure score
98
Critical Exposure
Pipeline progress

Scan progress

Open ops

Your scan has completed. The visuals below summarize what was found and why it matters.

0 queued 0 running 4 completed 0 failed
High severity
2
Major identity risks
Medium severity
3
Linkage risks
Surface count
5
Distinct exposure surfaces
Collectors
4
Analysis engines used
What this means
Why you stand out online

High exposure potential. Your identifiers create multiple paths for correlation.

email linkage cross-platform identity correlation direct contact exposure location confirmation business-personal linkage
Most exposed surfaces
email username phone location domain
Collector yield
Which engines found evidence
search_presence · stub
0 hits
username_correlation · stub
0 hits
contact_exposure · stub
0 hits
domain_linkage · stub
0 hits
Exposure footprint
How the trail connects
You
Phase 14 Test User
Location clue
Kuala Lumpur, Malaysia
Email trail
1 submitted email
Username trail
2 submitted usernames
Domain clue
phase14-example.com
This is a visual footprint of how submitted identifiers and discovered evidence sources can cluster together. It is not yet a true geo map; it is a correlation map.
Evidence sources
Where the strongest signals showed up

No evidence domains captured yet.

How an outsider could reason
What someone could infer
  • Someone could pivot from one username to multiple accounts and build a broader identity profile.
  • A phone number can make it easier to connect listings, messaging accounts, and business records.
  • Location clues can be combined with names, usernames, and employer data to narrow identity matches.
  • A domain can act as a hub that links projects, social accounts, emails, and public bios.
Adversary playbook
How the dots get connected
  • Start from a reused username and search across platforms.
  • Use public email traces to connect accounts and contact points.
  • Use a phone number to reinforce identity matches and targeting.
  • Use location clues to confirm which profiles likely belong to you.
  • Use the domain to connect business activity, profiles, and contact details.
Initial findings
What the scan found
  • Email addresses may be publicly searchable
    medium · email_exposure · confidence: high
    1 email(s) could be tied to profiles, breaches, contact pages, and cached search results.
  • Username reuse makes cross-platform correlation easier
    high · username_reuse · confidence: high
    2 username(s) can be checked across social platforms, forums, marketplaces, and old accounts.
  • Phone numbers increase discoverability and scam targeting risk
    high · phone_exposure · confidence: high
    1 phone number(s) can strengthen account lookup, contact tracing, and broker-style matching.
  • Location data strengthens identity confidence
    medium · location_linkage · confidence: medium
    City and country data can validate that scattered profiles belong to the same person.
  • Domains can connect business and personal identity trails
    medium · domain_association · confidence: medium
    The submitted domain (phase14-example.com) may connect websites, profiles, contact points, and project history.
Priority actions
What to do first
  • Separate public and private email usage
    high priority
    Use different emails for public-facing profiles, logins, and personal communication.
  • Reduce username reuse
    high priority
    Change or compartmentalize usernames so one handle does not connect all of your identities.
  • Remove public phone exposure where possible
    high priority
    Remove phone numbers from public profiles, business listings, and searchable pages when not required.
  • Reduce unnecessary location disclosure
    medium priority
    Remove city, neighborhood, and other location references from public bios when they are not needed.
  • Review domain-linked identity leakage
    medium priority
    Check whether your domain, email, and profile links unintentionally connect business and personal accounts.
Collector detail
How each engine contributed
backend

search_presence

completed_live

Live search completed for 2 querie(s) with 0 captured result(s).

Live hits
0
Queries
2
Matched domains
None
Matched platforms
None
full_name_searchable domain_searchable location_searchable
backend

username_correlation

completed_live

Live username correlation completed for 3 querie(s) with 0 captured result(s).

Live hits
0
Queries
3
Matched domains
None
Matched platforms
None
username_reuse_possible multiple_handles_submitted
backend

contact_exposure

completed_stub

Contact exposure stub completed.

Live hits
0
Queries
2
Matched domains
None
Matched platforms
None
email_exposure_possible phone_exposure_possible
backend

domain_linkage

completed_stub

Domain linkage stub completed.

Live hits
0
Queries
2
Matched domains
None
Matched platforms
None
domain_identity_linkage_possible
Evidence gallery
Captured public signals
search_presence

search_presence

Live search ran but returned no parsed top results.

Status
live_no_results
Input
"Phase 14 Test User" "Kuala Lumpur"
Confidence
low
URL
n/a
search_presence

search_presence

Live search ran but returned no parsed top results.

Status
live_no_results
Input
"phase14-example.com"
Confidence
low
URL
n/a
username_correlation

x check for phase14user

Live username search ran for x but returned no parsed top results.

Status
live_no_results
Input
"phase14user" site:x.com
Confidence
low
URL
n/a
username_correlation

instagram check for phase14user

Live username search ran for instagram but returned no parsed top results.

Status
live_no_results
Input
"phase14user" site:instagram.com
Confidence
low
URL
n/a
username_correlation

github check for phase14user

Live username search ran for github but returned no parsed top results.

Status
live_no_results
Input
"phase14user" site:github.com
Confidence
low
URL
n/a
contact_exposure

contact_exposure

Email prepared for exposure and discoverability checks.

Status
generated_stub
Input
phase14@example.com
Confidence
high
URL
n/a
contact_exposure

contact_exposure

Phone number prepared for discoverability and broker-style matching checks.

Status
generated_stub
Input
+60141414141
Confidence
high
URL
n/a
domain_linkage

domain_linkage

Domain prepared for linkage across websites, profiles, and contact surfaces.

Status
generated_stub
Input
phase14-example.com
Confidence
medium
URL
n/a
Submitted identifiers
What you gave the scan
Full name
Phase 14 Test User
Emails
phase14@example.com
Usernames
phase14user, legacyphase14
Phone numbers
+60141414141
City
Kuala Lumpur
Country
Malaysia
Domain
phase14-example.com
Lifecycle
When the pipeline ran
State
completed_stub
Submitted
2026-03-23T21:09:14.917533+00:00
Queued
2026-03-23T21:09:14.917533+00:00
Running
2026-03-23T21:09:14.929073+00:00
Assembled
2026-03-23T21:12:57.287066+00:00
Completed
2026-03-23T21:09:15.195330+00:00
Raw job pipeline
Collector job states

search_presence

completed_stub
Queued
2026-03-23T21:09:14.917533+00:00
Started
2026-03-23T21:09:14.929073+00:00
Completed
2026-03-23T21:09:15.033882+00:00

username_correlation

completed_stub
Queued
2026-03-23T21:09:14.917681+00:00
Started
2026-03-23T21:09:15.040429+00:00
Completed
2026-03-23T21:09:15.171021+00:00

contact_exposure

completed_stub
Queued
2026-03-23T21:09:14.917691+00:00
Started
2026-03-23T21:09:15.177837+00:00
Completed
2026-03-23T21:09:15.183596+00:00

domain_linkage

completed_stub
Queued
2026-03-23T21:09:14.917696+00:00
Started
2026-03-23T21:09:15.189627+00:00
Completed
2026-03-23T21:09:15.195330+00:00