Skip to content
Velloreth
Cybersecurity 10 min read

How to Audit Your Digital Footprint

A practical, step-by-step audit of every account, data broker, and exposure you have online. Includes tools, a repeatable checklist, and what to cut first.

By

Your digital footprint is everything an attacker, a data broker, or a curious stranger can assemble about you without ever meeting you: email addresses, phone numbers, old forum accounts, breached credentials, public records, and the data broker profiles that stitch those together. Auditing it does not mean disappearing from the internet. It means knowing what is out there, closing what should not be, and reducing what gets created in the first place.

This is a maintenance task, not a one-time project. Plan for an initial audit of a few hours, then a short quarterly pass.

What counts as footprint

People focus on social media posts and miss the categories that actually cause harm. The full inventory:

CategoryExamplesWhy it matters
Primary identityEmail, phone, legal name, addressesEverything else links back to these
AccountsSaaS, shopping, forums, developer profilesBreach source; account takeover vector
Credential exposuresBreached passwords, reused loginsDirect attack material
Data broker recordsPeople-search sites, marketing databasesAggregation makes targeting easy
Public tracesGit commits, old blogs, forum posts, DNS recordsReconnaissance material for social engineering
Device and browser dataTracking cookies, ad IDs, extensionsPassive profiling

Step 1: Search your own identifiers

Open a private browser window and search for each of these:

  • Your full name in quotes
  • Your primary email address in quotes
  • Any old email addresses
  • Your phone number
  • Your most-used username
  • Your home address (if you want to know what is public)

Also check the sites that do not rank well in Google but hold the most structured data: Whitepages, Spokeo, BeenVerified, TruePeopleSearch, and your country’s equivalent. In the US, these are the major people-search sites; elsewhere, search for “[your country] people search” and work through the top five.

Record every hit in a spreadsheet with three columns: URL, what is exposed, and action (keep, remove, monitor). This spreadsheet is your audit inventory. Update it each quarter.

Step 2: Take inventory of accounts

Your password manager already has most of this. Export the list of domains. If you do not use a password manager, that is your first fix — install one (Bitwarden, 1Password, or KeePassXC if you want local-only), and start importing saved passwords from your browser.

For every account, note:

  1. Is the password unique? Reused passwords are the highest-severity finding in almost every audit.
  2. Does it have MFA? Prioritize your email, cloud, banking, code host, and domain registrar.
  3. Do you still use it? Dormant accounts are free attack surface.

Then act in this order:

  • Email first. Your primary email is the reset key for everything else. Unique password, hardware-key or app-based MFA, and a recovery method you control.
  • Domain registrar and DNS. If someone takes over your domain, they can intercept email and impersonate you. Unique password, MFA, and lock the registrar transfer if available.
  • Cloud and code hosts. AWS, GCP, GitHub, GitLab — same treatment.
  • Everything else. Rotate reused passwords as you go. A password manager with a breach-report feature (Bitwarden and 1Password both have one) will tell you which of your passwords have appeared in known breaches; fix those first.

Step 3: Deal with data brokers

Data brokers aggregate public records, marketing data, and scraped sources into a profile: your name, relatives, addresses, phone numbers, sometimes income estimates and purchasing habits. Removing yourself is free but tedious, because brokers re-add records.

The process:

  1. Find your listing on each major broker site.
  2. Use their opt-out or removal form (usually linked in the footer as “Privacy” or “Do Not Sell”).
  3. Use a unique alias email for the request — you will get confirmation emails, and you do not want to give brokers more signal.
  4. Save the confirmation and set a calendar reminder for 30–45 days to check whether the listing returned.
  5. Repeat quarterly.

A shortlist of the largest US brokers to start with: Whitepages, Spokeo, BeenVerified, Intelius, TruePeopleSearch, Radaris, and MyLife. Many smaller brokers resell from the big ones, so removing yourself from the top tier eliminates a large share of downstream copies.

If the manual process is not sustainable, paid services (DeleteMe, PrivacyDuck, or similar) handle removals and re-checks for roughly $100–150 per year. That is a reasonable trade if your threat model includes harassment, stalking, or public-facing work.

Step 4: Reduce what gets created

The audit only matters if the footprint stops growing. Three structural changes do most of the ongoing work:

Alias emails. Services like SimpleLogin, Firefox Relay, or Apple’s Hide My Email give you a unique address per signup. When one gets spam or breached, you disable that alias, not your primary address. This also stops services from correlating your accounts by email.

Separate identities where it counts. Your public developer identity (GitHub, blog, conference talks) does not need to share a phone number with your banking identity. Use different emails, and do not reuse the same username across high-risk and low-risk contexts if you can avoid it.

Say less in profiles. Birthday year, employer, city, and phone number in a public profile are all social engineering inputs. Keep them off public accounts.

Step 5: Check breach exposure

Two free sources cover most of it:

  • Have I Been Pwned (haveibeenpwned.com): enter your email addresses and see which breaches they appear in. The site tells you what data was exposed — passwords, phone numbers, addresses.
  • Your password manager’s breach monitor, if it has one: flags reused or exposed passwords in your vault.

For each breach hit: change the password on that service if you still use it, and anywhere you reused that password. A password manager’s generator makes this a ten-minute task once the vault exists.

Do not pay for “dark web monitoring” as a consumer product. HIBP and your password manager cover the actionable part.

Step 6: Phone numbers deserve their own section

Phone numbers are the weak link in most account recovery chains, and they attract attacks that email does not.

SIM swap is the serious one: an attacker persuades (or bribes) a carrier employee to move your number to their SIM, then receives SMS one-time codes for your accounts. If any of your accounts use SMS as an MFA factor or as the recovery method, SIM swap converts a phone theft into an account takeover chain.

Mitigations:

  1. Port-out PIN / account passcode with your carrier. Call and set one; most major carriers support it, and it is the single control that blocks the simplest swap.
  2. Remove SMS as an MFA factor wherever an authenticator app or passkey exists.
  3. Use a VoIP number (Google Voice, and similar) for account registration instead of your mobile number, with the understanding that VoIP numbers have their own recovery weaknesses.
  4. Freeze credit in jurisdictions that offer it. A credit freeze at the major bureaus does not stop SIM swap directly, but SIM swappers frequently pair number theft with financial fraud, and the freeze closes that second door cheaply.

During your audit, list every account where your phone number is a recovery method. That list is the order in which you replace SMS with app-based factors.

Step 7: Browser and extension hygiene

Your browser is the surface where footprint accumulates passively.

  • Extensions. Every extension has permissions over every page you load. Audit installed extensions; delete anything unused. Prefer extensions from known publishers with narrow permissions. A compromised or abandoned extension is a full browsing-history siphon.
  • Tracking protections. Enable enhanced tracking protection (Firefox) or equivalent in your browser of choice. Consider a content blocker with a maintained filter list.
  • Old profiles and sync. Browser profiles synced to a cloud account carry history, cookies, and passwords. If you once synced a work profile to a personal account, check what is still syncing.
  • Saved passwords in the browser. If you are adopting a password manager (step 2), clear the browser’s saved passwords afterward so there is one vault, not two, and the browser copy is not the weaker one.

Step 8: Public traces

Developers in particular leave a long trail. Worth checking:

  • Git commits. Old commits may contain personal emails or even secrets. git log --author across your public repos is a quick sweep. For secrets, tools like gitleaks or GitHub’s secret scanning will flag committed credentials.
  • Old blogs and forums. Delete or anonymize accounts you no longer want tied to your name. Many forums allow username changes; some allow account deletion.
  • WHOIS and DNS. If you own domains, use registrar privacy (usually free now) so your name and address are not in public WHOIS records.
  • Public cloud storage. S3 buckets, Google Drive links, and old test deployments occasionally expose files. List what you have publicly reachable and close what should not be.

The math on data broker removals

A common question: why bother with brokers if breaches and accounts are the real risk? Two reasons.

First, brokers aggregate. A single people-search profile combines your name, relatives, addresses, phone numbers, and sometimes employment and income estimates into one page. An attacker doing targeted phishing pulls from that page instead of scraping ten sources. Removing the profile does not delete the underlying data, but it removes the convenient index.

Second, brokers resell. Records flow between the big aggregators and hundreds of smaller sites, so removing yourself from the top tier reduces downstream copies too. The reverse is also true: if you only remove yourself from a small site, the big brokers will re-add you from their existing data.

The realistic expectation is not zero records. It is: major listings gone, re-check quarterly, and new smaller sites handled as you encounter them. Services that charge for “complete removal” are selling the same free process at scale; whether the labor is worth paying for depends on how much time you have and how sensitive your exposure is.

What a good outcome looks like

You are done with the first audit when:

  • No major people-search site returns a current listing for you.
  • Every account on your inventory list has a unique password, and your top ten have MFA.
  • HIBP shows no unaddressed breaches with exposed passwords.
  • Your primary email — the reset key for everything — has a hardware-key or app-based MFA factor and a recovery method you control.
  • Your browser has no extensions you do not recognize and no old synced profiles.
  • The spreadsheet exists, and you have a calendar reminder for the quarterly pass.

That is a meaningful reduction in the practical ways strangers assemble information about you. Perfection is not the bar. Coverage of the high-value identifiers is.

A repeatable quarterly checklist

Print this or keep it in your notes:

  1. Search your name, emails, phone, and usernames in a private window. Log new hits.
  2. Check HIBP for new breaches. Fix any exposed passwords.
  3. Run your password manager’s reuse report. Rotate any reused passwords.
  4. Re-check the top five data broker sites for new listings. Submit removals.
  5. Review account inventory: delete anything new and dormant.
  6. Check that MFA is still enabled on your top ten accounts.
  7. Glance at your public repos and profiles for anything that should not be public.

The first pass is the long one. After that, this is a half-hour job every three months.

What this does not fix

A footprint audit reduces exposure; it does not make you unfindable. Public records, court filings, and anything you legitimately publish will remain. If your threat model is serious — stalking, a high-profile job, adversarial harassment — the next level is legal name changes on accounts, a PO box for anything physical, and professional help. For everyone else, knowing what is out there, closing the obvious doors, and cutting off the data flow is the entire game.

Frequently asked questions

How long does a full digital footprint audit take?
The first pass takes three to five hours spread over a few days. You will spend most of that time on password resets and data broker opt-out forms. Follow-up passes take under an hour once your inventory exists.
Are data broker removal requests really free?
Yes, in the US and many other jurisdictions you can request removal without paying. The work is in repeating the requests, because brokers re-add records. Services like DeleteMe do this for a fee, but you can do it yourself with a calendar reminder.
Should I delete old accounts or keep them?
Delete accounts you no longer use, especially on services that have had breaches. Every dormant account is a login that can be cracked and a data record that can leak. Keep accounts you actively use, but make sure they have MFA and a unique password.
Does a VPN hide my digital footprint?
A VPN hides your IP address from the sites you visit, which reduces some tracking. It does nothing about the accounts, broker records, and public posts tied to your identity. Footprint reduction is mostly account hygiene, not network tools.