Research guidance

Frequently Asked Questions

Practical answers about using SpiderFoot.tools for authorized OSINT research, interpreting public-source signals, and understanding our service boundaries.

Last updated: October 31, 2026

SpiderFoot.tools is for lawful, authorized research. Search results and AI-assisted output are investigative leads, not proof of identity, ownership, intent, or wrongdoing. Do not use them as the sole basis for a high-impact decision about a person or organization.

01 // What Is SpiderFoot.tools?

SpiderFoot.tools is an independent third-party, browser-based OSINT web service. It helps researchers organize public-information checks for usernames, email addresses, and IP addresses without requiring a local installation.

It is not affiliated with, endorsed by, or operated by the SpiderFoot open-source project or its maintainers. Our service, policies, research guidance, and website content are maintained independently. Learn more about who operates this website and how we evaluate tools on the About page.

02 // How Our OSINT Scanner Works

01 / INPUT

Choose a supported research type and submit a valid username, email address, or IP address.

02 / CHECK

The relevant workflow requests available public-source and service-provider checks for that input type.

03 / ORGANIZE

Results are presented as structured signals, source links, and progress information where available.

04 / VERIFY

You review original sources and independently corroborate any material finding before relying on it.

Feature availability, source coverage, and output can change as external providers change their services. AI-assisted suggestions, where enabled, help organize or extend research but do not replace source review or human judgment.

03 // How long does a full scan take?

A full username scan usually takes about 120 seconds (2 minutes), while a full email scan takes about 60 seconds (1 minute). These are estimates; scans may take longer during busy periods as more people scan at the same time.

The username workflow covers more than 2,500 sites across 15+ categories, so checking this volume takes time. Read our methodology to learn how scans run and how coverage is handled. We are continuing to optimize scan performance and increase server capacity to shorten wait times.

04 // What Data Sources Are Checked?

Coverage depends on the selected input type, enabled features, source availability, and applicable provider policies. A scan may surface signals from public websites, indexed web pages, public profile services, and network-context providers.

Not every source is queried for every scan, and a result should not be interpreted as a complete inventory of someone’s online presence. Third-party services control their own data, availability, rate limits, and ranking logic. See our methodology for how we explain source limitations and verification.

05 // Username OSINT

Username OSINT looks for publicly accessible references and possible account matches associated with a username. It can help an authorized researcher identify leads, compare public profile context, or conduct a self-audit of an organization’s public footprint.

A matching handle is not identity verification. Usernames are reused, impersonated, abandoned, and copied across platforms. Confirm the original profile, review dates and supporting context, and look for independent corroboration before making an attribution.

06 // Email OSINT

Email OSINT can surface publicly indexed references, associated domains, and other available context for an address. It is useful for approved security assessments, an organization’s exposure review, or investigating an identifier you are authorized to examine.

Do not submit credentials, private mailbox contents, financial details, health information, or other highly sensitive data. A discovered reference is not confirmation that an address is active, controlled by a particular person, or connected to any behavior. Use the service only as permitted by our Terms of Service.

07 // IP Address OSINT

IP address research provides network context, such as the apparent network operator, routing or location indicators, and other information returned by available providers. It can support incident triage, asset inventory, and authorized infrastructure analysis.

IP-derived location is usually an approximation, not a precise physical address. Addresses can be dynamic, shared, proxied, routed through cloud infrastructure, or associated with a VPN. Do not treat network context alone as proof that a specific person used, owns, or controlled an IP address.

08 // How to Read and Verify Results

  1. 01.Open the original public source rather than relying on a result title or summary.
  2. 02.Check provenance, dates, account history, and whether the source is still available.
  3. 03.Compare independent sources and record contradictions as well as confirmations.
  4. 04.Label observation and inference separately; stop when the evidence does not support a stronger conclusion.

Our methodology and editorial policy describe the standards we use when testing tools and publishing OSINT guidance.

09 // Accuracy and False Positives

Public data changes constantly. A source can be unavailable, outdated, incomplete, duplicated, or wrong; search engines and third-party providers may also rank or label the same information differently. Those conditions can produce false positives and false negatives.

Why can this hosted scanner miss an account or show a 403?

SpiderFoot.tools is a hosted preview. Some target sites rate-limit or block shared public-server IPs, return anti-bot challenges, or change their response format. A 403, 429, redirect, timeout, Error, or Unknown result leaves that check unresolved; an empty result is not proof that the account does not exist.

For broader authorized username or email coverage, consider running kaifcodec/user-scanner locally by following its README and command-line instructions. Your local network environment may avoid some restrictions placed on hosted infrastructure, but no scanner can guarantee complete or permanently accurate results. The complete usage guide explains why this is our preferred local option for focused username and email checks.

Use the smallest conclusion supported by the evidence. If you find a material error in a website result or article, send the page URL, a concise explanation, and safe-to-share supporting evidence through Contact or follow the correction process.

10 // Privacy and Data Retention

We may process search inputs, timestamps, and limited technical data to operate the requested workflow, protect the service, and provide available research-history features. External providers involved in a search may process requests under their own policies.

How do I permanently delete one saved scan?

Open the user sidebar, choose Username or Email under Search History, and select Delete from the scan’s list card or detail page. Review the warning and choose Delete Permanently to remove that scan record and all of its saved results from the database.

Warning: This action cannot be undone, and the deleted scan data cannot be recovered.

How do I permanently delete my account and all scan history?

Open the user sidebar and select Delete Account at the bottom of Site Menu. Review the confirmation warning, then choose Delete Account Permanently. This physically deletes the current user record, profile details, and every username and email scan-history record associated with that user ID. The current browser identifier is also cleared.

Warning: Account deletion is permanent and cannot be reversed. Logging out is different: it only clears the browser identifier and does not delete database records.

Only submit data you are authorized to investigate. For categories of data collected, use, sharing, retention, and available choices, read the Privacy Policy. Our Terms of Service explain the acceptable-use requirements.

11 // SpiderFoot.tools vs SpiderFoot Open Source

SpiderFoot.tools is an independent third-party OSINT web service. It is not affiliated with, endorsed by, or operated by the SpiderFoot open-source project or its maintainers. SpiderFoot and related project names belong to their respective owners.

This website provides its own browser workflows, public guidance, editorial standards, privacy notices, and support channels. For a clear explanation of the distinction, see About SpiderFoot.tools.

12 // Example OSINT Investigation

An appropriate example is an organization reviewing its own public exposure. A security team can define an authorized company username or email address, run the relevant workflow, review returned public references, and verify notable findings against the original pages. Confirmed issues can then be documented, assigned to an owner, and remediated.

The team should use only the modules and scope needed for that question, avoid unnecessary personal data, preserve enough source context for review, and stop when the approved task is complete. This is general information, not legal advice; local law, organizational policy, and permissions still apply.

13 // Latest OSINT Research

Visit the SpiderFoot research blog for current guides on responsible OSINT workflows, verification, privacy, and browser-based web tools. Articles are written and reviewed according to our editorial policy.

Still need help?

For a tool issue, correction, or support question, include the relevant page URL and safe-to-share context.

CONTACT_SUPPORT