Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

"Honest benchmark": reproducible comparison against puredns, shuffledns, dnsx and gobuster using lab zones

Open
#127 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
go

Research direction

Start by reading the existing -simulate-zone lab mode and its scenario-directive implementation, then inspect the CLI and README/landing-page documentation entry points. The issue proposes adding bench/ scenarios and a make bench-compare script, but does not identify existing test files or benchmark infrastructure. Done means the command reproduces the published comparison table on a fresh machine and the results page is linked from the README and landing page.

Written by the indexing model from the issue text.

Description

documentation marketing priority: medium

Value / who it's for

The strongest launch asset for #74. Users choosing a tool want evidence. subenum's differentiators (real rate limiting, per-query accounting, wildcard filtering, a confidence verdict) only show up in a benchmark that measures recall under adverse resolvers and queries actually sent vs the configured rate, not raw speed.

Rationale

Lab mode (-simulate-zone) with $REFUSE-ABOVE/$DELAY-style scenario directives makes a fully local, legal and reproducible benchmark possible. Competitors can be pointed at the same local server with their resolver flags.

Suggested approach

  • bench/ with scenario zones: clean, wildcard, rotating-pool wildcard, rate-limited resolver, flaky resolver, plus a script (make bench-compare) that runs each tool against the local server and records recall, false positives, wall time and wire queries (counted at the server).
  • A docs page with the results table, versions, and how to reproduce. Include where subenum loses; honesty is the brand.

Done when

make bench-compare reproduces the published table on a fresh machine, and the page is linked from the README and landing page.

Dominant language
Go
Stars
1
Forks
1
Avg merge
5d 2h
Merged PRs (30d)
3

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from TMHSDigital/subenum

All issues in TMHSDigital/subenum

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.