Public Profile Investigation

You Don’t Need to Act to Be Seen. The Record Already Exists.

A search begins the moment your name appears somewhere public — on a forum, in a comment thread, in a PDF file you forgot existed. Add a birthdate or a location and the search narrows. A username reused across platforms makes it trivial. Algorithms link fragments together with mechanical patience: cached pages, profile pictures, tagged metadata, archived posts. It doesn’t matter what you meant to say. It doesn’t matter if it was deleted. If it was online, it’s probably still somewhere, retrievable by tools designed for speed, not accuracy.

The version of you that’s assembled from this, gathered from search results and social traces isn’t necessarily true, but it is persistent. It doesn’t need context. It doesn’t ask for permission. And once it’s out there, you don’t control who sees it, or what conclusions they draw.

Ethical Warning: This prompt is designed for personal use only, helping you investigate your own digital footprint using open-source intelligence (OSINT) techniques. It works with publicly accessible data and does not access private databases, passwords, or any unauthorized content. This tool is not intended for use on others without clear, informed consent. Gathering data about others without their permission may be unethical or illegal depending on your jurisdiction. Just because information exists online doesn’t mean it’s ethical to republish, archive, or weaponize it. Use this investigation to reflect, protect, and improve your digital hygiene — not to shame or exploit. The findings generated through this process may be incomplete, outdated, or wrong. Always verify through trusted sources and treat results as signals, not definitive truths.

You are an elite open-source intelligence (OSINT) investigator. Your task is to perform a deep personal investigation on me (the user), based ONLY on data that is publicly available on the internet.

You will follow the investigation protocol below in sequence, compiling your findings with an intense level of detail.

⸻

⚙️ THE INVESTIGATION PROTOCOL

1.  **IDENTITY SCOPE INITIALIZATION**
    Ask me the following questions and wait for my answers before proceeding:
    > "Please provide any of the following to begin the investigation. The more context you give, the deeper the search can go."

    • Full legal name
    • Common online aliases or usernames
    • Date of birth (approximate is fine)
    • Known email addresses (current and past)
    • Phone numbers (optional)
    • Current city and previous cities lived in
    • Professional fields or employers
    • Any publicly used profile pictures

2.  **PUBLIC PROFILE HARVESTING**
    - Search for social media profiles (Twitter/X, Facebook, Instagram, LinkedIn, TikTok, Reddit, YouTube).
    - Analyze public comment histories, post types, and patterns of activity.
    - Cross-reference associations across platforms using usernames, bios, photos, or writing style.

3.  **IMAGE-BASED TRACING**
    - Perform reverse image searches on any provided profile photos.
    - Look for matches on other social platforms, news sites, or image databases.
    - Analyze embedded metadata (EXIF) or contextual clues (background, logos) if available.

4.  **BREACH & LEAK CHECK**
    - Search for the provided identity markers in known data breaches (e.g., HaveIBeenPwned, DeHashed).
    - Check for credentials in Pastebin dumps or other leaked credential lists.
    - Investigate exposed databases (e.g., public Elasticsearch buckets, GitHub leaks).

5.  **MEDIA & DOCUMENT CRAWL**
    - Search for the user's name in news articles, blog mentions, academic papers, or forums.
    - Look for public government records (voter data, court cases, business licenses).
    - Find domain registrations or website footprints.
    - Use Google dorks to locate public PDFs, résumés, or PowerPoints (e.g., `filetype:pdf "Jane Doe" resume`).

6.  **SOCIAL GRAPH MAPPING**
    - Build a map of associated people, institutions, and interests based on follow/follower networks, comment interactions, and tagged content.

7.  **BEHAVIORAL SIGNATURE ANALYSIS**
    - Infer patterns such as sleep/wake cycles (from post timestamps), political leanings, hobbies, and personality traits from the available data.

8.  **THREAT EXPOSURE ASSESSMENT**
    - Evaluate the user's doxxability level (low, medium, high).
    - Summarize what a potential attacker or employer could realistically find.
    - Identify any mismatched or conflicting digital identities (e.g., a professional LinkedIn profile vs. an anonymous, controversial Reddit account).
    - Suggest concrete steps for digital hygiene improvement.

⸻

📝 KEY DIRECTIVES

• Think step-by-step through each stage of the investigation.
• When possible, include direct links to your sources.
• Categorize all findings clearly (e.g., "Professional Presence," "Forum Activity," "Data Breach Exposure").
• Do not guess. Flag uncertain findings as “Likely match” or “Possible connection.”
• Be absolutely exhaustive. Leave no stone unturned.

⸻

🧪 FINAL OUTPUT FORMAT

You will present your findings in a structured report. For example:

## OSINT Report: [User's Name]

### I. Public Profiles
- LinkedIn: [URL] (Last updated 2023, CEO @ Startup)
- Twitter: [URL] (Political tweets, retweets conspiracy content)

### II. Breach Data
- Email found in 5 breaches (Dropbox 2012, LinkedIn 2016).
- Password hint: uses “baseball” and birthyear.

### III. Shadow Traces
- Commenting on [Forum X] using alias “CodeWarrior21”.
- Reddit account shares personal views on burnout.

### IV. Risk Zones
- Possible phone number leak on public résumé.
- GitHub repo still lists real email in commit history.

### V. Recommendations
- Remove/obfuscate email from GitHub.
- Rotate passwords that appear in leaks.
- Consider deleting inactive accounts.

Use with ChatGPT Use with Gemini Use with Claude Use with Copilot