MyRecon OSINTMyRecon public footprint search features
MyRecon combines public username lookup with email, breach, password, domain, DNS and IP checks. This guide explains what each feature examines, where its data comes from, and how to interpret uncertain results. Use the live tool and current plan details to confirm access and scope.
Product details
- MyRecon supports a public username lookup workflow for checks available through its current platform catalogue; individual sites can be unavailable or change their behavior.
- A result is a candidate for manual verification, not proof that a named person controls an account or that no account exists when no result appears.
Username lookup across public profiles
Search a username you own or are authorized to review. MyRecon checks supported public profile pages and reports candidates for manual verification. Guest scans show an initial set of results; sign in when you need the full report or want saved scans. Coverage changes by platform, and a blocked request or ambiguous page stays unconfirmed rather than being counted as a match.
Email and breach exposure
Email checks can examine provider and deliverability signals, disposable-address indicators, and available breach exposure from public breach data sources. A breach result describes data in a source record; it does not prove that an account is currently compromised. Review the affected fields and follow the remediation guidance for the account you control.
Password exposure checks
The password exposure checker hashes the password in your browser and uses the first five characters of that hash for a k-anonymity lookup. The password itself is not sent to MyRecon. Use a password you control, and change it anywhere it is reused if the check reports exposure.
Domain registration and DNS
Domain lookups use RDAP, the modern registration-data protocol that succeeds WHOIS for many registries, to show available registrar, registration, and nameserver details. DNS lookups resolve records such as A, AAAA, MX, NS, TXT, CNAME, SOA, and CAA using DNS-over-HTTPS. Public registration records can be redacted, and DNS answers describe current configuration rather than who controls a service.
IP address context
IP checks can show approximate geolocation, network or ASN ownership, hosting indicators, and reverse DNS when those public sources return data. Geolocation is approximate and usually identifies a network endpoint, not a person's home or precise location. A proxy or hosting flag is one signal, not a judgment about intent.
Review, export, and privacy
Open candidate links at their original sources before relying on a result. Browser history and saved guest items stay in the browser; signed-in scan reports can be saved to the account and deleted there. Where available, results can be exported for a self-audit. Read the privacy policy for the current retention and account details.
Use MyRecon within its limits
MyRecon works with public sources and cannot open private accounts or restricted material. A matching username is a lead, not proof of identity, and an empty result is not proof that an account does not exist. Use the tools for your own footprint or an authorized review, and keep the original source and uncertainty with any notes you retain.
Check a public username
Use accounts and identifiers you own or are authorized to review. A matching username is a lead, not proof of identity.
Frequently asked questions
What can I check with MyRecon?
MyRecon includes public username, email and breach, password exposure, domain registration, DNS, and IP checks. Coverage and access can vary by tool, so use the live interface and current plan page to confirm what is available.
Does a missing username result prove no account exists?
No. A site may block, rate-limit, rename, or restrict a profile, and some services may not be supported. Treat an unavailable or missing result as inconclusive unless the source provides a verifiable reason.
Can MyRecon confirm that a profile belongs to a person?
No. A matching username is only a lead. Confirm important conclusions with independent public evidence and keep uncertain links unconfirmed. MyRecon does not access private accounts or restricted content.
Is the password exposure check private?
The browser hashes the password and sends only the first five characters of the hash for the k-anonymity check. The password itself is not sent to MyRecon. See the privacy policy for details about data handling.