Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better integration with other services #200

Open
mattias-p opened this issue Apr 23, 2021 · 1 comment
Open

Better integration with other services #200

mattias-p opened this issue Apr 23, 2021 · 1 comment
Milestone

Comments

@mattias-p
Copy link
Member

mattias-p commented Apr 23, 2021

I learned today that Hardenize links to three other tools from one of its result pages. Among those tools is zonemaster.net 🎉

All three tools provide different levels of integration:

  • Zonemaster.net - It's just a link to an empty domain name field. You have to enter the domain name you ran Hardenize on and press enter or click the start button.
  • DNSSEC Analyser - It's a link to a pre-filled domain name field. You have to focus the field and press enter. (Weirdly enough they don't seem to have a start button.)
  • DNSViz - If there is an older test result you're immediately redirected to the result. If there is no test result you're presented with a pre-filled domain name field and an analyze button.

We should make it possible to create links with the domain name pre-filled, and perhaps even automatically start the test when the domain name is pre-filled. We should also make this feature discoverable by vendors. Perhaps by adding a "Integration" documentation topic that can be easily found by someone looking for it.

Some care should be taken when designing the URL schema for this feature. In particular the schema should allow for extension with other options.

E.g. I believe it would make sense to extend this feature to also allow the inclusion of fake delegation details in the link. The idea here is to give DNS providers an easy way to let their end-users test their NS-record and DS-record updates before making the jump and hoping for the best.

@matsduf matsduf added this to the v2021.2 milestone Apr 23, 2021
@matsduf
Copy link
Contributor

matsduf commented Apr 23, 2021

This is a good idea. The first step is the design and specification of the URL schema. It should be documented as an API to make sure that we do not change anything without an explicit decision.

@matsduf matsduf modified the milestones: v2021.2, v2022.1 Dec 1, 2021
@matsduf matsduf modified the milestones: v2022.1, v2022.2 May 22, 2022
@matsduf matsduf modified the milestones: v2022.2, v2023.1 Dec 20, 2022
@matsduf matsduf modified the milestones: v2023.1, v2023.2 Jun 26, 2023
@matsduf matsduf modified the milestones: v2023.2, v2024.1 Mar 19, 2024
@matsduf matsduf modified the milestones: v2024.1, v2024.2 Jul 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants