Your work address is on a few public profiles, in the history of a repository you contributed to years ago, maybe on a keyserver, and almost certainly in at least one breach notification you half-remember. Before changing passwords or cleaning up profiles, it helps to see in one place where the address is actually visible and which of those places carries real risk.
The Digital Footprint Self-Check answers that for your own address. It first proves that you can read the mailbox, then asks a fixed set of public sources about the address and turns the answers into findings with a source, a confidence label and concrete steps under "What you can do". It is a privacy self-audit, not a people search.
What is a digital footprint self-check?
In simple terms
Your digital footprint is the trail of data linked to you online. This tool looks at one slice of it: places where your email address is published or known. That means data breaches the address was part of, a public Gravatar profile or avatar, OpenPGP keys published for the address, GitHub profiles and Git commits that show it, and the mail setup of the domain the address belongs to. You get a dashboard of what was found, what was not, and which sources could not be asked.
Technical background
Each source exposes the address through a different mechanism:
| Source | What it holds | How it is looked up |
|---|---|---|
| Have I Been Pwned (HIBP) | Breaches and pastes that contained the address, with breach metadata and data classes | HIBP API v3 breachedaccount and pasteaccount, which require an API key |
| Gravatar | A public profile and/or avatar image tied to the address | Gravatar identifies profiles by a hash of the normalized address; the tool computes the SHA-256 hash and asks the profile API and the avatar URL |
| keys.openpgp.org | Published OpenPGP keys whose user ID contains the address (this keyserver only publishes addresses whose owners confirmed them by email) | HKP index query (op=index&options=mr), the machine-readable listing format of the HTTP Keyserver Protocol |
| GitHub | Accounts that show the address as public profile email, and commits whose author email is the address | GitHub search API: user search with in:email and commit search with author-email: |
| Your mail domain | MX records, the DMARC policy and whether the address itself is published in DMARC rua/ruf or in security.txt | DNS queries for MX and _dmarc TXT, and a request for /.well-known/security.txt |
Two background facts explain several findings. Git stores whatever user.email the committer configured, without any verification. And DMARC (RFC 7489) is what lets receiving servers reject mail that spoofs your domain; without an enforcing policy (p=quarantine or p=reject) someone else can more easily send mail that appears to come from your address.
Why use the self-check?
- Prioritize password changes: see which breaches included passwords and when they happened.
- Find forgotten public profiles: a Gravatar profile shows details on every site that displays Gravatar images.
- Clean up developer exposure: a public profile email or commit author email is harvested by spammers and recruiters.
- Review old keys: an expired or forgotten OpenPGP key can confuse people who want to write to you.
- Check your domain's anti-spoofing: a missing or
p=noneDMARC policy makes phishing in your name easier. - Spot an address published in DNS: a personal address in DMARC reporting tags or security.txt attracts spam.
Who should use it?
Anyone who wants to audit their own address: developers who commit under a work or personal address, administrators who published their own mailbox as a DMARC report or security contact, people preparing a privacy cleanup or a password-manager migration, and security teams that want staff to self-assess. Each person checks their own address; the verification step means one person cannot audit a colleague's mailbox.
How the digital footprint self-check works
All steps run through the NetTools.tech API; the address is sent only in request bodies, never in a URL.
1. Info. When the page loads, it asks the server which sources are available and what each one receives. Have I Been Pwned is marked "not configured — skipped" when no API key is set. If the server cannot send email, the page says the self-check is unavailable and disables the start button. Verification is never bypassed.
2. Start. You enter your address and tick the consent box ("This is my own email address…"). The server validates the address, applies rate limits and emails a 6-digit code. The code is stored only as a hash, together with the address, in memory.
3. Verify. You enter the code. A wrong code reports how many attempts remain; after five wrong attempts the code is discarded and you must request a new one. A correct code is consumed and replaced by a verified session.
4. Run. The session runs all sources in parallel, each with a 12-second timeout (15 seconds for the mail domain checks). For large mailbox providers such as gmail.com, outlook.com or proton.me the DNS checks are skipped, because the provider manages that domain; you get a context note instead. Results are combined into findings, a score and source statuses, and only the masked address (for example a***@example.com) is returned with them.
Limits (from the server configuration):
| Limit | Value |
|---|---|
| Code validity | 15 minutes |
| Wrong code attempts | 5 |
| Verified session | 30 minutes |
| Runs per session | 5 |
| Code requests per connection | 3 per 10 minutes, 10 per day |
| Code requests per address | 3 per hour |
| Code requests for the whole service | 300 per day |
Every footprint operation is flagged as sensitive, so the server writes no input value into its request log for these calls. Challenges and sessions are deleted when they expire, when you press Clear results, and (on a best-effort basis) when you leave the page.
How to use the NetTools.tech Digital Footprint Self-Check
- Open the Digital Footprint Self-Check.
- Read What will be checked — and who receives your address. It lists each source and what it receives.
- Enter Your email address, tick the consent checkbox and press Send verification code. The address field is cleared once the code is sent.
- Open the email "Your NetTools.tech verification code" and enter the code under Verification code. A countdown shows how long the code is valid. Use Use a different address to start over.
- Press Verify and run the check. A progress list shows each source being checked.
- Read the dashboard (see below), open findings to see details and What you can do.
- Press Run again after fixing something, within the 30-minute session. Export with CSV, JSON, Copy all or Print. Exports show the address in masked form.
- Press Clear results when you are done. This deletes the session on the server and resets the page.
Understanding the results
Dashboard
| Result | Meaning | What to look for |
|---|---|---|
| Header line | Masked address, check time and "X of Y sources answered" | Fewer answering sources means missing data, not a clean result |
| NetTools Privacy Exposure Score | 0–100 with a band: No public exposure found, Low, Moderate, Elevated, High | Open How it was calculated to see every contribution |
| KPIs | Sources checked, sources with public presence, breaches (with how many included passwords), public profiles, cryptographic identity (published keys), developer references | "not checked" under Breaches means HIBP is not configured |
| Exposure by category | Cards for Breaches, Public profiles, Developer / code activity, Cryptographic identity, Public email infrastructure, Other public references, each with "N exposures", "context only" or "nothing found" | Click a card to jump to its findings |
| Breach timeline | Breaches per year of the breach; darker bars include leaked passwords | Recent bars with passwords come first in your cleanup |
| Public vs. private exposure | Public: anyone can see it (profiles, keys, Git history, published listings). Private: known from breaches, held by breached services and attackers | Public items you can often remove; private ones you can only contain |
| Source coverage | A bar and table with each source's result: Found, Not found, Rate limited, Not configured, Source unavailable, and the retrieval time | Rerun later if a source was unavailable or rate limited |
| Findings | Expandable cards grouped by category with title, source, confidence, details, "Why it matters", check time, source link, metadata and "What you can do" | Breaches with passwords open automatically |
Confidence labels
| Label | Meaning | Used for |
|---|---|---|
| Confirmed by source | The source states the match directly | Verified HIBP breaches, Gravatar, OpenPGP keys, GitHub profile emails, DMARC/security.txt listings |
| Matched, not verified | Matched by address but the source has not verified it | HIBP breaches flagged as unverified |
| Unverified — may not be yours | The data cannot prove ownership | GitHub commit author matches |
| Context | Information, not exposure | Mail domain MX/DMARC summary, large mailbox provider note |
The score formula
The score adds points per finding that counts as exposure and is capped at 100:
| Finding | Points |
|---|---|
| Breach | 8, +4 if passwords were leaked, +4 if HIBP marks it sensitive; all breaches together at most 60 |
| Paste | 3 |
| Public Gravatar profile | 10 (avatar only: 4) |
| Developer reference | 8 (unverified commit match: 4) |
| Published OpenPGP key | 5 |
Other public listing (DMARC rua/ruf, security.txt) | 3 |
Bands: 0 none, 1–24 low, 25–49 moderate, 50–74 elevated, 75–100 high. Context findings and sources that did not answer add nothing. The page labels it "informational, not an industry-standard security rating". It is a summary of this tool's findings, not a measure of how safe you are.
Example: an illustrative self-check
The following is illustrative: the address, breach names and numbers are invented to show how the dashboard reads, and do not describe any real person or service.
Suppose [email protected] is verified and the sources return two breaches ("ExampleShop", 2019, with passwords among the data classes; "Example Forum", 2016, without passwords), a Gravatar avatar without profile details, one published OpenPGP key, and 12 public commits with this author address. The header would read a***@example.com · checked … · 5 of 5 sources answered, and How it was calculated would list:
ExampleShop breach (2019): +12
Example Forum breach (2016): +8
Public Gravatar avatar: +4
Public OpenPGP key 0123456789ABCDEF: +5
Address in public Git history (12 commits): +4That gives 33 / 100, Moderate exposure. The mail domain finding (MX servers and DMARC policy for example.com) appears under Public email infrastructure as context and adds no points.
Reading it: the 2019 breach card opens automatically because passwords were involved, and its What you can do list says to change that password and any reuse, use a password manager and enable multi-factor authentication. The commit finding is "Unverified — may not be yours", so check whether those repositories are yours before acting; for future commits, switch to the GitHub noreply address. The key finding tells you whether the key has expired and how to remove an identity you no longer use.
Common use cases
- Annual privacy review: run the check, fix public items, rerun within the session to confirm.
- After a breach notification: see which other breaches include the same address and which leaked passwords.
- Before publishing open-source work: confirm your commits use a noreply address.
- Domain owner check: see whether your domain's DMARC is enforcing and whether your personal mailbox is published in DNS.
Troubleshooting
The start button is disabled and the page says the check is unavailable
The server cannot send verification emails (mail is not configured), or the NetTools service is not reachable. Nothing is checked in either case; try again later.
No code arrives
Check the spam folder and the spelling of the address. If the mail server refused the message you see "The verification email could not be sent". You can request at most three codes per address per hour and three per connection in ten minutes; after that you get a "Too many verification…" message.
"The code is not correct" or "Too many wrong codes"
Enter the six digits from the newest email; the page only uses the code of its latest request. After five wrong attempts, or after 15 minutes, request a new code.
"This verified session has expired"
Sessions last 30 minutes and allow five runs. Verify the address again.
Have I Been Pwned shows "Not configured"
The server has no HIBP API key, so breaches were not checked. This is not the same as zero breaches. If HIBP reports a rejected key, the source is shown as unavailable with a message for the administrator.
A source is "Rate limited" or "Source unavailable"
The source did not answer in time or is throttling requests; GitHub search in particular has tight limits. A note says results from these sources are missing, not clean. Use Run again later.
Common mistakes
- Reading "Not configured" or "unavailable" as clean. Only "Not found" means the source answered without a match.
- Treating commit matches as proof. Anyone can author commits with your address.
- Treating the score as a security grade. It weighs findings by a fixed NetTools formula; one reused breached password can matter more than the number suggests.
- Expecting history to disappear. Changing your Git email affects new commits only; old ones stay unless repositories are rewritten.
- Checking only one address. Aliases and old addresses have their own footprint; verify and check each.
Limitations
- Fixed sources only. The tool does not search social networks, forums, people-search sites, data brokers or leaked databases, so a "low" result covers only these sources.
- Breach data depends on HIBP and its API key on the server; breaches HIBP does not know about are not shown.
- Search coverage varies. GitHub search only finds public data it has indexed, and the tool takes at most five profiles and five sample commits per search (the commit count is GitHub's total); the key lookup covers keys.openpgp.org only, not other keyservers.
- DNS checks are skipped for large mailbox providers and only list the address in DMARC or security.txt when it matches exactly.
- Point-in-time results. Nothing is saved; a later check may differ.
Security & privacy
Verification by emailed code is mandatory, so only the mailbox owner can run the check. The address stays in server memory for the code and the verified session, is not written to the request log, is never put in a URL and is deleted on Clear results, when you leave the page (best effort) or when the session expires. The results are not stored. Have I Been Pwned, keys.openpgp.org and GitHub receive the address; Gravatar receives only a SHA-256 hash; DNS resolvers see only your domain. No account is changed anywhere and no password, hash or leaked content is shown. Exports label the address in masked form; note that details copied from public sources, such as OpenPGP user IDs, can themselves contain your address. Never enter a password into this tool, as none is needed. See the privacy policy.
Related tools
- Password Strength Checker – test a replacement password locally; guide.
- Password Generator – create unique passwords for breached accounts; guide.
- Email Health Check – SPF, DKIM and DMARC for your own domain; guide.
- DMARC Lookup – read your domain's DMARC policy in detail; guide.
- Network & Abuse Contact Finder – find who to report abuse from a network or domain to; guide.
- My Info & Identity tools overview.
Summary
The Digital Footprint Self-Check shows where one address you have proven to own appears in breaches, on Gravatar, on keys.openpgp.org, on GitHub and in your mail domain's published records, with a source and confidence for every finding. The Privacy Exposure Score summarizes the findings but is informational only. Fix the public items you control, change any breached passwords, and treat sources that did not answer as unchecked rather than clean.
Frequently asked questions
Why do I have to verify my email address first?
The results describe a person, so the tool only runs for someone who can read the mailbox. A 6-digit code is emailed to the address, and the check starts only after that code is entered, which keeps the tool a self-audit rather than a way to investigate other people.
Is this a people search?
No. It checks one address you have proven to own against a fixed list of sources: Have I Been Pwned, Gravatar, keys.openpgp.org, GitHub and the DNS and security.txt of your mail domain. It does not search or scrape social networks, query leaked databases or look up names, phone numbers or other people.
Does the tool show my leaked passwords?
No. Breach findings contain the breach name, dates, the number of affected accounts and the types of data involved, such as email addresses or passwords. Passwords, hashes and leaked content are never shown, and paste findings do not include the paste text.
Which services receive my email address?
Have I Been Pwned, keys.openpgp.org and GitHub receive the address for their lookups. Gravatar only receives a SHA-256 hash of it, public DNS resolvers only see the domain part, and the request for your domain's security.txt contains nothing personal; the page lists all of this before you start.
Does NetTools store my address or the results?
No. The address is held in server memory for the 15-minute code and the 30-minute verified session only, and the operations are marked sensitive so the address is never written to the request log. Clear results deletes it from the server immediately, and the results are not saved.
Why does the breach check say "Not configured"?
Have I Been Pwned requires an API key, which the NetTools administrator has to set on the server. Without it, breaches and pastes are not checked and the dashboard says so instead of reporting zero breaches; you can still check the address directly at haveibeenpwned.com.
Why are my GitHub commits marked as unverified?
Git does not check the author address of a commit, so anyone can create commits that carry your address. A commit match shows that the address appears in public history, not that you made those commits, so it is labelled "Unverified — may not be yours" and scores lower than a profile match.
What does the Privacy Exposure Score mean?
It is a NetTools summary from 0 to 100 that adds fixed points per exposure finding, with the formula and every contribution shown on the page. It is informational and not an industry-standard security rating, so use the individual findings to decide what to fix.
What happens if the server cannot send email?
The tool is unavailable. Verification is never skipped: without a working mail configuration the Send verification code button is disabled and nothing is checked.