Currently, testssl prints a big red warning when a server has no server preferred cipher order.

Mozilla recently relaxed their recommendations regarding cipher order. If only strong cipher suites are supported anyway, why not deciding according to the client's preferences. Maybe it's a phone that wants to optimize for performance on low hardware. Additionally, often browsers are better maintain

I'm using this project and want to add mobx for state management.

I'm happy to PR documentation/example with some guidance!

Thoughts? @tirthbodawala

Instead of just doing it in the CLI. Currently, non-CLI uses of pshtt are forced to remember to call the function themselves in order to get the same level of sanitization.

https://hstspreload.org/static/css/style.css has this font stack:
font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, "Helvetica Neue", Helvetica, Arial, sans-serif;

I propose to change it to this:
font-family: system-ui, "-apple-system", "Segoe UI", Roboto, "Helvetica Neue", Helvetica, Arial, sans-serif;

Because system-ui is the standard version of prefixed `

As hinted in aidantwoods/SecureHeaders#67 (comment), the public API could do with some better coverage.

On the front page we say: "test your website" and just below we ask "Your domain name". We should consider to use the same term.

I set the nuxt.config.js file with the following settings:

modules: [
    '@nuxtjs/axios',
    '@nuxtjs/pwa',
    [
      '@dansmaculotte/nuxt-security',
      {
        dev: false,
        csp: {
          directives: {
            defaultSrc: ["'self'"],
            scriptSrc: ["'self'"],
            connectSrc: ["'self'"],
            imgSrc: ["'self'"],
            sty