-
Notifications
You must be signed in to change notification settings - Fork 58
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
Update DNS report #2413
Update DNS report #2413
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. Just a side note: I thought we generally capitalize H1, H2, and H3 headings, but I'm not sure.
I dont see a CAA record in that table, But I do see that it somehow has that security measure, this seems illogical? I'd also like to see the various DNS related findings listed. Eg, no ipv6 on the nameservers, or not enough nameservers. |
After reviewing the report it would be nice to change the following things.
|
CAA are actually shown, but mispo.es doesn't have them. In the QA I did see it for one of the domains I tested. |
Small additions are fixed. Ready for merge. |
…minvws/nl-kat-coordination into feature/add-dns-generate-report
Restarting the bits solved the missing CAA Record. It was a problem on my end. |
Changes
This PR updates the DNS report in the Generate Report flow to match the new design.
The new design can be seen here:
https://www.figma.com/file/QRL8085Z827bNdO0bIDdFL/KAT-%7C-Design-%7C-For-review?type=design&node-id=2305-3142&mode=design
Changes:
Extra info
The "Security measures" chapter hasn't been deleted as in the design. This chapter should stay and was forgotten about in the new design.
For now, only the DNS report has been modified for the Generate Report flow. The Figma design shows the Aggregate Report flow, which doesn't exist yet (should be build firts).
Issue link
Closes #2406
Demo
Code Checklist
Communication
.env
changes files if required and changed the.env-dist
accordingly.Checklist for code reviewers:
Copy-paste the checklist from the docs/source/templates folder into your comment.
Checklist for QA:
Copy-paste the checklist from the docs/source/templates folder into your comment.