Roadmap 2026

[bwbroersma]

This is a continuously updated issue of our roadmap. Last update by Sasha on 2025-02-05, all instances running v1.10.7.

Planned releases:

• v1.9 - will include the RPKI scoring.
• v1.10 - includes a non-scoring CAA test, resolver cleanup
• v1.11 - all new TLS
  • based on new (currently not yet released) NCSC-NL TLS guidelines 2025
  • Proposal to change 'phase out' TLS web configurations from warning to failed #1154 / Fix #714 - Switch to (mainly) sslyze for TLS testing #1218
  • will include all? labeled tls
  • will include tls-update to SSLyze
  • TLS update is a multi stage process:
    1. first implement existing behaviour,
    2. then run comparison to find unknown old bugs fixed and potential new bugs,
    3. then modify for new guidelines: Update sslyze branch to NCSC 2025 #1800
• v1.x - webdesign - in progress, Website redesign #1252, see https://dev3.internet.nl
  • See labels webdesign, some smaller things (<details><summary> and JS) can be done before the design, ideally at least all HTML changes are done before the front-end work is done.
  • Will also have plenty of content changes.

Larger priority items:

• Improvements to the database and data structure. Initially thought as a big restructure, likely possible in a less dramatic and more gradual way. Thoughts so far: (1) Decide on consistent terminology for test targets #1531; (2) rename a lot of parts of our DB (the schema isn't that bad itself, it just has terrible naming all around); (3) look to improve our pickle-in-text storage; (4) address chaos in the translation between test output and database and the gazillion untyped manually copied dicts.
• Optional DNS checks to add #1288
• Add "test" for hosting location / dependencies / sovereignty #1926

Other improvements we may want to prioritise:

• (Re)move news content & optimize repo #1611
• Fixes #1246 and #1756 - Removed Hall of Fame task #1754 (fix for single test)
• Fix and test report generation locking for results views, fixes #1749 #1776 (fix for batch)
• Should we start checking for PQC ? #1640 PQC testing in TLS

Ongoing things:

• fix bugs
• Improvements in deployment
• keep dependencies up to date
• make sure other instances (e.g. DK and other translations) have a workable fork

This is the roadmap for Internet.nl and the Internet.nl API. For the dashboard, which supports creating internet.nl metrics in bulk refer to the dashboard roadmap, here.