What's better about this vs. Mozilla Observatory. https://developer.mozilla.org/en-US/observatory https://developer.mozilla.org/en-US/observatory (formerly htt

What's better about this vs. Mozilla Observatory. https://developer.mozilla.org/en-US/observatory https://developer.mozilla.org/en-US/observatory (formerly https://observatory.mozilla.org/ https://observatory.mozilla.org/) Or Security Headers? https://securityheaders.com/ https://securityheaders.com/ Or VENOM? https://github.com/oshp/oshp-validator https://github.com/oshp/oshp-validator Applaud the effort, these are things that more devs should be aware of when building websites... Hey some specific feedback on this tool... On mobile, it has a lot of "view port wobble" and the input fields aren't keyed right, it's just using a straight text input field so you don't get any ".com" buttons as you type. The forms use light gray text on a dark gray background -- that isn't at all aligned with WCAG standards. https://i.imgur.com/BNCC5Dx.png https://i.imgur.com/BNCC5Dx.png And it really needs to work on what it thinks is a valid URL. https://i.imgur.com/N1ctafd.png https://i.imgur.com/N1ctafd.png Small UX stuff like that annoy me more than if a page has a privacy policy setup correctly. (= Lastly, Permissions Policy... good concept, but still in "DRAFT" so not quite something you can ding users for not adopting just yet. https://www.w3.org/TR/permissions-policy/ https://www.w3.org/TR/permissions-policy/ https://caniuse.com/permissions-policy https://caniuse.com/permissions-policy If you want to play around with it, here's a good tool to generate examples. https://www.permissionspolicy.com/ https://www.permissionspolicy.com/ Oh lastly lastly, there are some really easy tools out there for helping to create a Content Security Policy, these really speed up the process. (Just make sure you disable your ad-blockers before running.) https://csper.io/generator https://csper.io/generator https://github.com/april/laboratory https://github.com/april/laboratory