Frequently Asked Questions
SeekOSINT automatically detects and normalises:
1.1.1.12606:4700:4700::1111http://, trailing slashes strippedAS15169 or plain 15169Up to 15, depending on query type. All sources are queried in parallel — the page renders results as each source responds rather than waiting for all to finish.
No. SeekOSINT is entirely passive. It only queries existing public databases and APIs. No packets are sent to the target host.
SeekOSINT stores only anonymous recent-search query strings (not IPs) for the homepage recent-searches widget. No user identity is tracked. Upstream APIs may log queries on their end per their own privacy policies.
A source may be unavailable for several reasons:
500 requests per hour per IP on a rolling window. If you hit the limit you'll receive a 429 response. Self-hosting with your own API keys removes this constraint.
Private ranges (10.x, 172.16–31.x, 192.168.x) are rejected at validation. They have no meaningful public intelligence data.
Yes. The source is available on GitHub under the project license. Contributions, bug reports, and source suggestions are welcome.
SeekOSINT only queries public data sources — there is no active probing. However, you are responsible for complying with the terms of service of each underlying source and the laws of your jurisdiction. Only investigate hosts you own or have explicit authorisation to investigate.
Each source has its own data freshness — from live DNS resolution to 12-hour certificate caches to 24-hour BGP snapshots. Results are KV-cached at the edge for performance; hit the refresh button to bypass the cache and fetch live data.
The worker exposes a JSON API at /api/lookup?q=<target>. Self-host your own instance for higher throughput and direct API access without rate limits.
.env.example → .env and fill in your API keysnpm install then npm run dev for local devnpm run deploy (Cloudflare Pages via OpenNext)