[Issue] The `rl,rls` options are not supported

[Bundy01]

Describe the bug
I noticed that these options weren't working when testing with the sitedossier source, for example. I suspected that it was blocking my VPN's IP.
I thought it was coming from him, but now I suspect the number of requests/min is too high.

On an old branch, I saw a commit including the limits/min c3d8a02.
This is more sensible, for example with the subdomaincenter source and its 2 requests/min.

Subfinder version
Current Version: v2.6.7

Complete command you used to reproduce this
subfinder -s sitedossier -dL FILE -rl NUMBER
subfinder -s sitedossier -rls sitedossier=2/m -dL FILE

Screenshots
an extract from FILE

surreal.vision
askfacebook.net
instagramboomerang.com
instagramboomerang.net
boomerangfrominstagram.com
advertiseonfacebook.net
webinstagramsecurity.com
oculusacademy.net
oculusacademy.org
connect-facebook-mobile.net
connect-facebook-cell.net
friendfeed-inc.com
instagram.bet
instagram.bayern
instagramboomerang.org
instagram.scot
instagram.brussels
instagram-together.org
instagram.shop
instagram.tj
instagram.doctor
instagram.loan

[dogancanbakir]

Hi @Bundy01 ! Thanks for your recent feedbacks—we really appreciate it. As a thank-you, grab some PD stickers here: http://nux.gg/stickers!

Btw, I'll look into this.

[dogancanbakir]

/bounty $75

[algora-pbc]

💎 $75 bounty • ProjectDiscovery Bounty Available

How to Participate:

• Claim attempt: Comment /attempt #1434 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/subfinder and include /claim #1434 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/subfinder 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:05 AM	WIP
🟢 @falcolnic	Feb 03, 2026, 08:45:40 AM	#1728	Reward
🟢 @thecafetron-ctrl	Feb 08, 2026, 11:59:50 AM	#1744	Reward
🟢 @buildingvibes	Feb 09, 2026, 07:44:09 PM	#1737	Reward
🟢 @Rhan2020	Feb 11, 2026, 04:06:48 PM	#1738	Reward
🟢 @nenadilic84	Feb 13, 2026, 06:40:45 AM	#1740	Reward
🟢 @jpirstin	Feb 16, 2026, 06:10:03 PM	#1742	Reward
🟢 @285729101	Feb 17, 2026, 09:35:32 AM	#1745	Reward

[Simplereally]

/attempt #1434

I'll fix the rate limit duration handling. The -rl/-rls options currently ignore the duration unit (e.g., /m for per-minute).

Root cause: In pkg/runner/runner.go, only sourceRateLimit.MaxCount is used — Duration is ignored.

Plan:

1. Modify rate limit setup to respect Duration field
2. Add test for per-minute rate limiting
3. Submit PR with full test coverage

[falcolnic]

/attempt #1434

[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!