-l -list option does not understand multiple prefixes, comma-separated in a single line

[hubrandesk789]

tlsx version:

Version: v1.2.0
Operative System: linux
Architecture: amd64
Go Version: go1.24.4

Current Behavior:

Serving targets as prefixes with the option -u work.
./tlsx -u 192.168.1.0/24,192.168.2.0/24,192.168.3.0/24

Using the option -l / -list filename.txt where the filename.txt contain a one line, comma-separated prefixes does not.
[WRN] Could not connect input 192.168.1.0/24,192.168.2.0/24,192.168.3.0/24:443 [auto,ztls:RUNTIME] failed to setup connection <- [:RUNTIME] cause="no address found for host" <- could not dial address <- could not connect to host

Expected Behavior:

Same behavior using -u or -l filename.txt

Steps To Reproduce:

Pick some prefixes of your chose who are reachable, save them inside filename.txt as prefix1,prefix2,prefix3
./tlsx -l filename.txt -v

[dogancanbakir]

/bounty $75

[algora-pbc]

💎 $75 bounty • ProjectDiscovery Bounty Available

How to Participate:

• Claim attempt: Comment /attempt #859 on this issue. Multiple participants can attempt, but only the first to submit a complete, mergeable solution will receive the reward.
• Work on the issue: Follow the Contribution Guidelines and ensure your solution fully addresses the issue requirements.
• Submit your PR: Open a pull request to projectdiscovery/tlsx and include /claim #859 in the PR body.
• Receive payment: Upon successful merge, you will receive 100% of the bounty through Algora within 2-5 days.

Thank you for contributing to projectdiscovery/tlsx and helping us democratize security!

---

PR Requirements

Your PR must include the following. PRs that don't meet these requirements may not be reviewed and could be closed.

Proposed Changes

Describe the overall picture of your modifications to help maintainers understand the pull request.

Proof

Demonstrate your changes work. Include before/after examples, screenshots, or terminal output showing the fix/feature in action.

Checklist

• PR created against the correct branch (usually dev)
• All checks passed (lint, unit/integration/regression tests)
• Tests added that prove the fix is effective or feature works
• Documentation added (if appropriate)

---

Add a bounty • Share on socials

Attempt	Started (UTC)	Solution	Actions
🟢 @Simplereally	Feb 03, 2026, 03:09:11 AM	WIP
🟢 @sangokp	Feb 05, 2026, 08:03:59 AM	#892	Reward
🟢 @thecafetron-ctrl	Feb 08, 2026, 11:59:51 AM	#897	Reward
🟢 @ohmygod20260203	Feb 09, 2026, 02:00:16 AM	#895	Reward
🟢 @buildingvibes	Feb 09, 2026, 07:41:23 PM	#898	Reward
🟢 @nenadilic84	Feb 14, 2026, 12:07:41 PM	WIP
🟢 @fayanwubian-hue	Feb 15, 2026, 02:21:53 AM	#904	Reward
🟢 @285729101	Feb 17, 2026, 09:32:33 AM	#910	Reward
🟢 @artylobos	Feb 24, 2026, 06:40:40 AM	#921	Reward
🟢 @Bushi-gg	Feb 24, 2026, 10:47:09 AM	#922	Reward

[Simplereally]

/attempt #859

I'll fix the comma-separated entries handling in -l/-list file input.

Problem: When using -l with a file containing comma-separated entries on a single line, they're treated as one target instead of being split.

Plan:

1. Add comma-splitting when reading targets from input files (matching -u behavior)
2. Add test for comma-separated file input
3. Submit PR with full test coverage

[samuel-asleep]

@dogancanbakir can you assign me ?

[dogancanbakir]

Hey contributors! Please make sure your PR follows the PR template and includes proof that your changes work (before/after examples, screenshots, or terminal output). Reviewer time is limited! Incomplete PRs may be closed without review. Thanks!

[dogancanbakir]

Hey @Simplereally — just a heads up, you've got multiple bounty issues claimed. We ask contributors to work on one at a time. Pick the one you'd like to focus on and we'll go from there.