In Sublist3r, which flag scans found subdomains against specific TCP ports?

In Sublist3r, which flag scans found subdomains against specific TCP ports?

• A. --help (-h)
• B. --verbose (-v)
• C. --ports (-p)
• D. --sockets (-s)

Answer: (C)

The thing being tested is how to run a targeted port check on each discovered subdomain. The flag for scanning against specific TCP ports is the ports option. When you provide a list after this flag (for example, -p 80,443,22), Sublist3r will not only find subdomains but also attempt to connect to those subdomains on the specified ports. This reveals which ports are open and, by extension, which services might be exposed on each subdomain, giving you a clearer view of the attack surface. The other options don’t trigger port checks: one shows help/usage instructions, another only adjusts how much detail the output prints, and the remaining flag isn’t about selecting ports to scan.

The thing being tested is how to run a targeted port check on each discovered subdomain. The flag for scanning against specific TCP ports is the ports option. When you provide a list after this flag (for example, -p 80,443,22), Sublist3r will not only find subdomains but also attempt to connect to those subdomains on the specified ports. This reveals which ports are open and, by extension, which services might be exposed on each subdomain, giving you a clearer view of the attack surface.

The other options don’t trigger port checks: one shows help/usage instructions, another only adjusts how much detail the output prints, and the remaining flag isn’t about selecting ports to scan.