Resend
Resend is wiring itself into every agent runtime it can reach, and now adding the controls to stop a send.
Comparison · Infra & APIs
DNSControl vs Greenbone Vulnerability Manager
A side-by-side editorial comparison of DNSControl and Greenbone Vulnerability Manager — release velocity, themes, recent moves, and the top alternatives to consider.
DNSControl vs Greenbone Vulnerability Manager: at a glance
| Feature | DNSControl | Greenbone Vulnerability Manager |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 5.0 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | dns, infrastructure-as-code, devtools, release-candidate | vulnerability management, web application scanning, gmp protocol, report modeling |
| Last editorial update | 2h ago | 10d ago |
| Website | Visit → | Visit → |
What is DNSControl?
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
DNSControl has locked v5.0.0 to bugfixes only with a stated ship date of 25 August 2026. rc9 carries no new capability: punycode decoding before IDNA validation in ALIDNS, a SVCB fix in POWERDNS, NAPTR and trailing-dot fixes in DYNU, a dnssort edge case, and internal refactors replacing pkg/diff and standardising on models.Records. The release notes read as a call for provider testing more than an announcement.
What is Greenbone Vulnerability Manager?
Greenbone's scanner daemon is growing a web-application scanning class beside its network roots.
gvmd releases every week or two, and the changelog splits cleanly in three: a sustained build-out of web application scanning, a rewrite of how reports are modeled and exported, and a long tail of memory-management fixes in the C core. Recent versions added web application scanner preferences, scanner verification, and a Web Application VT subtype with a database migration. The report work moved from ad-hoc XML toward a structured report model addressable through new GMP commands.
DNSControl vs Greenbone Vulnerability Manager: editorial side-by-side
DNSControl
5.0INFRA · APIS
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
◆ Current state
DNSControl has locked v5.0.0 to bugfixes only with a stated ship date of 25 August 2026. rc9 carries no new capability: punycode decoding before IDNA validation in ALIDNS, a SVCB fix in POWERDNS, NAPTR and trailing-dot fixes in DYNU, a dnssort edge case, and internal refactors replacing pkg/diff and standardising on models.Records. The release notes read as a call for provider testing more than an announcement.
◆ Where it's heading
The v5 arc has run its course in public: rc1 laid out the dnsv2.RDATA refactor, rc3 finished converting every provider to it, rc4 completed the move to the Codeberg-hosted miekg/dns, and rc8 declared feature completeness. What is left is per-provider correctness on record types that only a handful of users exercise, which is why the maintainer is publishing a list of which providers most need testing rather than shipping.
◆ Prediction
Expect one or two more release candidates of provider fixes before the 25 August date, with the risk concentrated in providers nobody volunteers to test - the notes already flag PACKETFRAME as unmaintained and EXOSCALE as not supporting PTR.
Greenbone Vulnerability Manager
6.3INFRA · APIS
Greenbone's scanner daemon is growing a web-application scanning class beside its network roots.
◆ Current state
gvmd releases every week or two, and the changelog splits cleanly in three: a sustained build-out of web application scanning, a rewrite of how reports are modeled and exported, and a long tail of memory-management fixes in the C core. Recent versions added web application scanner preferences, scanner verification, and a Web Application VT subtype with a database migration. The report work moved from ad-hoc XML toward a structured report model addressable through new GMP commands.
◆ Where it's heading
Greenbone is widening what gvmd can orchestrate. Network and container scanning were the existing surface; web application scanning is being brought to parity, with its own VT class, preferences, validation, and verification path. In parallel the GMP protocol is gaining first-class report retrieval commands, which makes report data consumable by tooling rather than only renderable. The bug-fix stream is dominated by frees and cleanup in long-lived report paths, the signature of a codebase under memory pressure at scale.
◆ Prediction
Web Application VTs now have a subtype, a migration, and scanner verification, but the audit and scan report commands were added separately; expect the report model work to fold web application results into the same structured retrieval path rather than leaving a parallel one.
Alternatives to DNSControl and Greenbone Vulnerability Manager
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either DNSControl or Greenbone Vulnerability Manager.
Casdoor
Casdoor is spending its release cadence moving auth checks from the client to the server
ESPHome
ESPHome ships on a calendar, and the August beta train is now five builds deep
Strimzi
Strimzi's 1.2.0 candidate closes with a logging fix and nothing else
Prowler
Prowler's assistant decides what to do with findings; the patches keep the scanner honest
NetBox
NetBox adds a cooling data model — the first new infrastructure domain since power
See all DNSControl alternatives → · See all Greenbone Vulnerability Manager alternatives →
Recent activity from DNSControl and Greenbone Vulnerability Manager
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 12h agoDNSControlDNSControl v5 rc9 sets a 25 August ship date, bugfixes only
- 6d agoDNSControlDNSControl v5 rc8 declared feature complete
- 16d agoDNSControlDNSControl v5 rc4 completes the move to Codeberg-hosted miekg/dns
- 16d agoGreenbone Vulnerability Manageropenvasd library bumped to 23.9
- 16d agoGreenbone Vulnerability ManagerGMP gains a get_audit_report_hosts command
- 17d agoDNSControlDNSControl v5 rc3 finishes converting every provider
- 21d agoGreenbone Vulnerability ManagerWeb Application VTs become a first-class scan type ⚡
- 27d agoDNSControlDNSControl v5 rc2 continues the internal rewrite
- 28d agoGreenbone Vulnerability ManagerStructured report model and the get_scan_report command
- 29d agoDNSControlDNSControl v5 rc1 lays out the dnsv2.RDATA refactor
- 29d agoGreenbone Vulnerability ManagerPer-object asset permissions and report-script trust checks
- 1mo agoGreenbone Vulnerability ManagerAggregate grouping and family-name fixes
Frequently asked questions
What is the difference between DNSControl and Greenbone Vulnerability Manager?
They serve adjacent needs but don't currently overlap on shipped themes. Greenbone Vulnerability Manager is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is DNSControl better than Greenbone Vulnerability Manager?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Greenbone Vulnerability Manager is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to DNSControl?
Top DNSControl alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "DNSControl alternatives" section above for the current picks, or visit /alternatives/dnscontrol for the full list with editorial commentary on each.
What are the best alternatives to Greenbone Vulnerability Manager?
Top Greenbone Vulnerability Manager alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Greenbone Vulnerability Manager alternatives" section above for the current picks, or visit /alternatives/greenbone-gvmd for the full list with editorial commentary on each.