v0.7.0

Release Note
v0.7.0 expands resolver scanning and DNSTT testing beyond the previous UDP-only flow. This release adds selectable DNS scan transports (UDP, TCP, BOTH), adds embedded DNSTT transport support (UDP, TCP, DOT, DOH) with optional resolver endpoint templating, persists the new settings in config.

Changelog

• Added scan protocol selection in the UI: UDP, TCP, or BOTH.
• Added DNSTT transport selection in the UI: UDP, TCP, DOT, or DOH.
• Added optional DNSTT Resolver Endpoint override, including {ip} and {port} placeholder support.
• Persisted scanConfig.protocol, dnsttConfig.transport, and dnsttConfig.resolverURL in saved config.
• Updated config loading to normalize and restore the new protocol/transport fields.
• Extended the embedded DNSTT runtime to support https://, tls://, and tcp:// resolver transports.
• Added validation for invalid DNSTT transport and resolver endpoint combinations, including DOH requirements.
• Extended scanner probing to support TCP and combined UDP/TCP scans.
• Improved resolver scoring tests, including dual-protocol behavior and NS answers from the authority section.

v0.6.1

Full Changelog: v0.1.6...v0.6.1

v0.1.6

This release candidate brings the DNS scanner and DNSTT workflow much closer to SlipNet, replaces the old external DNSTT client process with an embedded runtime, and stabilizes the TUI for smaller terminals and stage transitions.

Highlights

• SlipNet-style DNS compatibility scanning with 6 tunnel probes and score-based qualification
• Embedded DNSTT runtime inside range-scout with no external dnstt-client binary required
• HTTP-over-SOCKS5 DNSTT verification aligned with SlipNet’s real-traffic check
• New Test Nearby IPs option for /24 follow-up testing after successful DNSTT results
• Major TUI layout fixes for compact screens, sidebar stability, and command-pane rendering
• Improved export behavior for both scan and DNSTT stages, including paired failure exports
• Updated config handling and README examples to match current UI behavior

Scanner

• Reworked DNS scanning to use SlipNet-style tunnel compatibility scoring instead of the older recursive/stable-only model
• Added the 6 resolver checks used for tunnel qualification:
  • NS -> A
  • TXT
  • random subdomain
  • tunnel realism
  • EDNS0
  • NXDOMAIN
• Sorted scan results by score and latency for more useful prioritization
• Preserved scan result metadata for later DNSTT and export decisions
• Fixed a scanner progress-emitter timing issue that could cause CI flakiness

DNSTT

• Added Sock optional username & password support
• Replaced the old external dnstt-client process model with an embedded in-process DNSTT runtime
• Switched end-to-end verification from the old raw SOCKS connect behavior to real HTTP-over-SOCKS5 traffic validation
• Added E2E URL support with http://www.gstatic.com/generate_204 as the default probe
• Added Test Nearby IPs as a Yes / No dropdown on the DNSTT screen
• Added strict single-hop /24 expansion rules:
  • only original successful resolvers seed nearby expansion
  • nearby-discovered IPs do not expand again
  • each /24 expands at most once
  • IPs already covered by original scan ranges are skipped
• Removed leftover obsolete dnstt-client discovery and legacy helper code from the runtime path

TUI / UX

• Reworked the layout for smaller laptop screens so config fields remain visible
• Fixed command-pane row jumps when actions unlock after scan or DNSTT completion
• Fixed sidebar/button rendering issues where controls were hard to see or click
• Removed unnecessary DNSTT stage/tunnel labels to flatten the form
• Moved DNSTT Pubkey directly under DNSTT Domain
• Simplified the DNSTT command pane to focus on labeled fields and actions only
• Bumped the in-app version to v0.1.6-rc1 during the release-candidate cycle

Export / Results

• Restored scan-stage export visibility after DNSTT runs
• Scan export continues to produce paired success and failure outputs
• DNSTT Export Passed now also writes a paired failures file
• Nearby DNSTT discoveries are excluded from normal scan exports so scan semantics stay clean
• Added DNSTT candidate tracking so totals and failure exports stay correct after nearby expansion

Config / Docs

• Updated config.json handling to reflect current UI fields
• Added support for testNearbyIPs
• Documented the current config shape in the README
• Updated the README and release examples for the current release-candidate flow

v0.1.6-rc3

Full Changelog: v0.1.6-rc2...v0.1.6-rc3

v0.1.6-rc2

v0.1.6-rc2

This release candidate brings the DNS scanner and DNSTT workflow much closer to SlipNet, replaces the old external DNSTT client process with an embedded runtime, and stabilizes the TUI for smaller terminals and stage transitions.

Highlights

• SlipNet-style DNS compatibility scanning with 6 tunnel probes and score-based qualification
• Embedded DNSTT runtime inside range-scout with no external dnstt-client binary required
• HTTP-over-SOCKS5 DNSTT verification aligned with SlipNet’s real-traffic check
• New Test Nearby IPs option for /24 follow-up testing after successful DNSTT results
• Major TUI layout fixes for compact screens, sidebar stability, and command-pane rendering
• Improved export behavior for both scan and DNSTT stages, including paired failure exports
• Updated config handling and README examples to match current UI behavior

Scanner

• Reworked DNS scanning to use SlipNet-style tunnel compatibility scoring instead of the older recursive/stable-only model
• Added the 6 resolver checks used for tunnel qualification:
  • NS -> A
  • TXT
  • random subdomain
  • tunnel realism
  • EDNS0
  • NXDOMAIN
• Sorted scan results by score and latency for more useful prioritization
• Preserved scan result metadata for later DNSTT and export decisions
• Fixed a scanner progress-emitter timing issue that could cause CI flakiness

DNSTT

• Replaced the old external dnstt-client process model with an embedded in-process DNSTT runtime
• Switched end-to-end verification from the old raw SOCKS connect behavior to real HTTP-over-SOCKS5 traffic validation
• Added E2E URL support with http://www.gstatic.com/generate_204 as the default probe
• Added Test Nearby IPs as a Yes / No dropdown on the DNSTT screen
• Added strict single-hop /24 expansion rules:
  • only original successful resolvers seed nearby expansion
  • nearby-discovered IPs do not expand again
  • each /24 expands at most once
  • IPs already covered by original scan ranges are skipped
• Removed leftover obsolete dnstt-client discovery and legacy helper code from the runtime path

TUI / UX

• Reworked the layout for smaller laptop screens so config fields remain visible
• Fixed command-pane row jumps when actions unlock after scan or DNSTT completion
• Fixed sidebar/button rendering issues where controls were hard to see or click
• Removed unnecessary DNSTT stage/tunnel labels to flatten the form
• Moved DNSTT Pubkey directly under DNSTT Domain
• Simplified the DNSTT command pane to focus on labeled fields and actions only
• Bumped the in-app version to v0.1.6-rc1 during the release-candidate cycle

Export / Results

• Restored scan-stage export visibility after DNSTT runs
• Scan export continues to produce paired success and failure outputs
• DNSTT Export Passed now also writes a paired failures file
• Nearby DNSTT discoveries are excluded from normal scan exports so scan semantics stay clean
• Added DNSTT candidate tracking so totals and failure exports stay correct after nearby expansion

Config / Docs

• Updated config.json handling to reflect current UI fields
• Added support for testNearbyIPs
• Documented the current config shape in the README
• Updated the README and release examples for the current release-candidate flow

v0.1.5

This release improves Windows usability and adds shareable app configuration.

Highlights
Fixed duplicated typing issues in Windows input fields.
Restored mouse clicking for Windows builds.
Added config.json support for startup defaults, with Save Config from the UI.
Added visible app version in the header to make bug reports easier.
Improved clipboard paste behavior across editable fields.
Config
You can now place a config.json next to the app or project and share stage-based defaults for:

importConfig
scanConfig
dnsttConfig

v0.1.4

What's New in v0.1.4
This release adds a dedicated DNSTT validation stage, improves scan targeting, and fixes several important workflow and export issues.

Highlights
Added a post-scan DNSTT stage that runs only on healthy recursive resolvers
Added support for both tunnel-only and full E2E DNSTT validation
Added Export Passed and Copy Passed for DNSTT-passed resolvers
Made the recursion check host configurable
Derived scan scope directly from Pick Targets, removing the need for a manual host limit
Improved manual target workflows with Import TXT and Paste Targets
Improved dnstt-client detection and missing-client handling for E2E runs
Fixed an export bug where failed DNSTT results could be exported as successful in some cases
Updated the release workflow so

v0.1.4-rc2

Full Changelog: v0.1.4-rc1...v0.1.4-rc2

v0.1.4-rc1

Full Changelog: v0.1.3...v0.1.4-rc1

v0.1.3

Full Changelog: v0.1.2...v0.1.3