Skip to content
Osint Daily
Osint Daily cover for uncover, under Internet scanning, published 16 Oct 2026. The right side crops the listing capture. Look up exposed ports for a public host.

01 · Product name

uncover

Look up exposed ports for a public host.

Published by ProjectDiscovery.

FreeTerminalInternet scanning

In short

uncover is the ProjectDiscovery client for internet search engines. On 19 Oct 2026 the SPDX field on projectdiscovery/uncover was MIT. The latest GitHub release was v1.2.1, published 2026-05-20. The binary run here printed Current Version: v1.2.1. The README says the install wants go1.21, and that shodan-idb needs no API key and is the default engine when the input is an IP. A query for 1.1.1.1 returned twelve host:port lines. A query for 8.8.8.8 returned port 53 and port 443. Both used only shodan-idb.

Product pricing strategy

02

Free

The repository's SPDX field on 19 Oct 2026 was MIT, and the README did not print a price for uncover itself. The binary ran the shodan-idb engine with no key and no checkout. Shodan, Censys, FOFA, and the other named engines are separate services. The README says they need their own API keys. This listing did not open those accounts and does not copy a Shodan or Censys plan price onto uncover. MIT covers the client. It does not cover a third-party search engine's quota. If a key-backed engine later bills a query, cite that engine's pricing page. The twelve lines for 1.1.1.1 and the two lines for 8.8.8.8 are result counts from one morning. They are not a fee.

Utility and features

03

uncover, from projectdiscovery/uncover, is a Go client that asks internet search engines for hosts. The README says it requires go1.21 to install, and that the engine flag accepts shodan, shodan-idb, fofa, censys, and others, with shodan as the flag's default. The same README says shodan-idb does not require an API key and is the engine used by default when the input is an IP or a CIDR. The other engines need keys. They were not configured and were not queried. The latest GitHub release on 19 Oct 2026 was v1.2.1, published 2026-05-20T11:54:31Z. The binary's own line was Current Version: v1.2.1. The SPDX field is MIT.

  • Client v1.2.1. The GitHub release v1.2.1 was published 2026-05-20. The binary printed Current Version: v1.2.1. The SPDX field is MIT.
  • 1.1.1.1 returned twelve ports. shodan-idb listed 53, 80, 443, 2052, 2053, 2082, 2083, 2086, 2087, 2096, 8080, and 8443.
  • 8.8.8.8 returned two. The same engine and the same morning returned 8.8.8.8:53 and 8.8.8.8:443.

Two lookups were run that morning, both against public resolvers, both with -e shodan-idb. echo 1.1.1.1 produced 1.1.1.1:53, :80, :443, :2052, :2053, :2082, :2083, :2086, :2087, :2096, :8080, and :8443. echo 8.8.8.8 produced 8.8.8.8:53 and 8.8.8.8:443. Those lines are what Shodan InternetDB returned through uncover. They are not a full port scan by this machine, and they are not a statement that every other port is closed. The README's CIDR examples were not used. A hit is a port the engine has associated with that address. Confirm anything you intend to rely on in the engine's own record.

  1. 1

    Pass -e shodan-idb when you want the keyless engine, and name that engine next to the output.

  2. 2

    Query an address you are willing to record, and keep the host:port lines with the date.

  3. 3

    Open the upstream engine before you treat a port as currently open.

Caveats

04

The README says go1.21. The release and the binary agree on v1.2.1. Do not invent a newer client version from the Go toolchain that happened to compile it. The engine default in the flag help is shodan. The README also says shodan-idb is the default when the input is an IP. The commands here passed -e shodan-idb so the sentence does not depend on that default.

A line such as 1.1.1.1:443 means the engine returned that pair. It does not mean this machine connected to the port, and it does not mean the other engine's web UI would show the same set today. 8.8.8.8 returned only 53 and 443 in this run. That shorter list is not a claim that 1.1.1.1's extra ports were a mistake. No key-backed engine was queried. Do not present these two resolvers as a scan of someone else's network. The README's sample CIDR was not the command that was run.

Screenshots

05

uncover lookup of 1.1.1.1. uncover v1.2.1, command echo 1.1.1.1 piped to uncover -e shodan-idb, on 19 Oct 2026. The binary printed 1.1.1.1:53, :80, :443, :2052, :2053, :2082, :2083, :2086, :2087, :2096, :8080, and :8443. Captured 2026-10-19. Source
uncover lookup of 8.8.8.8. uncover v1.2.1, command echo 8.8.8.8 piped to uncover -e shodan-idb, on 19 Oct 2026. The binary printed 8.8.8.8:53 and 8.8.8.8:443. No other engine was queried. Captured 2026-10-19. Source

Potential use cases

06

  • You want the ports a public resolver presents to an internet search engine. On 19 Oct 2026 uncover v1.2.1 with -e shodan-idb printed twelve host:port lines for 1.1.1.1, including 53, 80, 443, 8080, and 8443, and two lines for 8.8.8.8, ports 53 and 443. The README says shodan-idb needs no key. The SPDX field is MIT. Name the engine next to the lines.
  • A note is about to call this a scan of a network. The commands were echo of a single address piped to uncover. This machine did not connect to those ports, and the README's CIDR examples were not the commands that ran. A host:port line is the engine's association. Confirm it in Shodan's own record before you brief it as currently open.
  • Another engine is about to be described as included. The flag help lists Shodan, Censys, FOFA, and others. Those need keys, and none of them was configured. The flag default in the help text is shodan, while the README says shodan-idb is the default for an IP. The commands passed -e shodan-idb so the sentence does not rest on the default.

Hard cases

The case where the first result is easy to over-read.

The short answer hides the engine

Twelve ports for 1.1.1.1 and two for 8.8.8.8 are meaningless without the engine and the client version. Both runs were uncover v1.2.1 and shodan-idb on 19 Oct 2026. A later key-backed engine can disagree. Do not copy a Shodan plan price onto the MIT client, and do not drop ports to make the two resolvers match.

Practitioners using it

Posts on X from people describing a concrete use. The quote is the post. Likes and reposts are the counts saved with it, not a live total. A label marks a creator, a maintainer, a vendor, a partner, a data partner, or an investor.

Vendor

Questions

Is uncover free?

The SPDX field is MIT, and shodan-idb answered without a key on 19 Oct 2026. Other engines in the README need their own API keys and their own pricing.

What did 1.1.1.1 return?

uncover v1.2.1 with -e shodan-idb printed twelve host:port lines, from 1.1.1.1:53 through 1.1.1.1:8443. 8.8.8.8 printed only port 53 and port 443.

Citations

07

Titled sources. These public pages are what the quotes on this listing come from.

When this listing changes, the letter says so.

Developments in OSINT. Confirm from your inbox before the first issue.

Only for this letter. Privacy

Related tools