For discussion: show any existing test results by default?

[mdavids]

Should we mimic DNSviz behavior and show any existing test results first, instead of immediately initiating a new one (and leave that up to the user)?

There is functionality in place that we could perhaps be used for this: https://internet.nl/site/example.nl/results

But there are questions too:

• Doing this would of course have serious impact on the main KPI, the number of scans.
• Should a user be redirected to a more than 1 year old result?
• Should this also be capped on 'the last version' of the scoring code? (e.g. changes in scoring like adding RPKI or fixing parser bugs, have impact on the result) Especially the case for users who check their own site on internet.nl and see 100%, it should be very clear the 'full compliance' might no longer be the case. In my mind the answer here is: yes it should.
• Should there be a 're-scan' scheduled automatically if the age is > Y? In my opinion: no.
• The 'scanning now' feels nice, the result is 'fresh', you 'trigger' something. So we should maintain the 'scan now' button.
• In terms of data analysis: probably it would be wise to first check how often sites are repeatedly scanned in combination with the change of subtest results.
• Is this idea worth the effort?

[bwbroersma]

There is a bug related to using /results if the site was never tested and takes less than a minute to test:

• #1511