Most of us have used the same email address for years: to sign up for shops and forums, to sign Git commits, to create a Gravatar, perhaps to publish a PGP key. Each of those leaves a trace, and some of them end up in data breaches. The new Digital Footprint Self-Check shows where your own address is exposed — and only yours.
A self-check, not a lookup of other people
The tool starts with a promise it enforces: you can only check an address whose mailbox you can read.
- You enter your address and confirm that it is yours.
- Before anything is sent, the page lists every service that will be asked and what it receives.
- NetTools emails you a 6-digit code. It is valid for 15 minutes and allows five attempts.
- Only after you enter the code does the check run, in a verified session that lasts 30 minutes.
Without the code nothing is checked. If the NetTools server cannot send email, the tool says it is unavailable — it never skips the verification. That is what makes it a self-audit: you cannot use it to investigate someone else.
What is checked
| Source | What it receives | What it can show |
|---|---|---|
| Have I Been Pwned | your address | data breaches and public pastes that contain it |
| Gravatar | only a SHA-256 hash of your address | a public avatar or profile linked to it |
| keys.openpgp.org | your address | published OpenPGP keys with this verified address |
| GitHub | your address | profiles that show it publicly, and commits that name it |
| Public DNS | only your mail domain | the domain's mail servers and anti-spoofing (DMARC) policy |
| Your mail domain's website | nothing personal | whether its security.txt or DMARC record lists your address |
No social networks are searched or scraped, no leaked databases are queried, and nothing is changed in any account.
Reading the results
The dashboard groups everything into six categories — breaches, public profiles, developer and code activity, cryptographic identity, email infrastructure and other public references — and opens with an overall indicator, the NetTools Privacy Exposure Score from 0 to 100. The formula is shown on the page: a breach counts 8 points (more if passwords or sensitive data were involved), a public profile 10, a developer reference 8, a published key 5, other public listings 3. It is an informational summary, not an industry-standard security rating.
To illustrate (this is a made-up example, not a real person): an address found in two breaches, one of them with leaked passwords, and with a public Gravatar profile would score 8 + 4 + 8 + 10 = 30 out of 100, moderate exposure. The breach timeline would show the two years, the public-vs-private bar would separate the breach data (held by breached services and attackers, not browsable) from the public profile (visible to anyone).
Each finding opens into the details: what was found, why it matters, when it was checked, a link to the source, how confident the match is — and what you can do about it, for example:
- change the password of a breached service and anywhere it was reused, and enable multi-factor authentication;
- remove details from your Gravatar profile, or use another address for public comments;
- switch Git to GitHub's "noreply" address so future commits do not expose your address;
- revoke an old PGP key you no longer use;
- use an alias for future public registrations.
Honest about uncertainty
Two details show how the tool treats its sources:
- Breach data is metadata only. You see the breach name, date, the types of data involved and a description — never passwords, hashes or any leaked content.
- Git history is marked "unverified — may not be yours". Git does not check the author address of a commit, so anyone can create commits with your address. A match means your address appears in public history, which matters for spam, but not that you wrote those commits.
If a source does not answer, the result says so and notes that missing results are not "clean" results.
Privacy is the feature
- Your address is held in the server's memory only for the verification and the 30-minute session.
- It is never written to logs or analytics, never put in a URL and never stored with the results.
- Clear results deletes the session immediately; leaving the page also tries to end it, and otherwise it expires after 30 minutes.
- Exports (copy, JSON, CSV, print) show the address masked. Details copied from public sources — such as a PGP key's user ID — can still contain it, and the export says so.
Why NetTools built this instead of a "people search"
We had planned a People Search. We dropped it: the big platforms offer no lawful way to search people through their APIs, the alternatives mean scraping or data brokers, and a search for someone else's traces is a stalking tool. Turning the idea around — what can others find about me? — keeps the useful part and removes the harm. Its sibling for organisations is the Network & Abuse Contact Finder, which finds the contacts networks and websites publish for abuse and security reports.
Try it
Open the Digital Footprint Self-Check with an address you use, and keep the recommendations list as a small privacy to-do. The guide describes every source, limit and score component.