Security Report Summary
C
Site: https://flex.okta.com/oauth2/ausseglz71syrobqo2p6/v1/authorize?client_id=0oa1swfs86idnqfvu2p7&redirect_uri=http://aquiresnc.flex.com/login&response_type=code&scope=profile%20email%20openid&state=avxurl
IP Address: 18.219.144.33
Report Time: 23 May 2022 05:03:46 UTC
Headers:
  • X-Frame-Options
  • X-Content-Type-Options
  • Strict-Transport-Security
  • Content-Security-Policy
  • Referrer-Policy
  • Permissions-Policy
Supported By
Probely
Not bad… Maybe you should perform a deeper security analysis of your website and APIs:
Raw Headers
HTTP/2400
dateMon, 23 May 2022 05:03:46 GMT
content-typetext/html;charset=utf-8
content-length1627
servernginx
public-key-pins-report-onlypin-sha256="r5EfzZxQVvQpKo3AgYRaT7X2bDO/kj3ACwmxfdT2zt8="; pin-sha256="MaqlcUgk2mvY/RFSGeSwBRkI+rZ6/dxe/DuQfBT/vnQ="; pin-sha256="72G5IEvDEWn+EThf3qjR7/bQSWaS2ZSLqolhnO6iyJI="; pin-sha256="rrV6CLCCvqnk89gWibYT0JO6fNQ8cCit7GGoiVTjCOg="; max-age=60; report-uri="https://okta.report-uri.com/r/default/hpkp/reportOnly"
x-okta-request-idYosVslhMzOlRHCX8rlyfjAAADYk
x-xss-protection0
p3pCP="HONK"
expect-ctreport-uri="https://oktaexpectct.report-uri.com/r/t/ct/reportOnly", max-age=0
cache-controlno-cache, no-store
pragmano-cache
expires0
x-frame-optionsSAMEORIGIN
x-content-type-optionsnosniff
content-languageen
strict-transport-securitymax-age=315360000; includeSubDomains
set-cookiesid=""; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/
set-cookieautolaunch_triggered=""; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/
set-cookieJSESSIONID=FC2453A98811B10DFF177968A67D2E76; Path=/; Secure; HttpOnly
set-cookiet=default; Path=/
set-cookieDT=DI0cFCZN24jRfy3b9Kfp93c_g;Version=1;Path=/;Max-Age=63072000;Secure;Expires=Wed, 22 May 2024 05:03:46 GMT;SameSite=None
Missing Headers
Content-Security-PolicyContent Security Policy is an effective measure to protect your site from XSS attacks. By whitelisting sources of approved content, you can prevent the browser from loading malicious assets.
Referrer-PolicyReferrer Policy is a new header that allows a site to control how much information the browser includes with navigations away from a document and should be set by all sites.
Permissions-PolicyPermissions Policy is a new header that allows a site to control which features and APIs can be used in the browser.
Upcoming Headers
Cross-Origin-Embedder-PolicyCross-Origin Embedder Policy allows a site to prevent assets being loaded that do not grant permission to load them via CORS or CORP.
Cross-Origin-Opener-PolicyCross-Origin Opener Policy allows a site to opt-in to Cross-Origin Isolation in the browser.
Cross-Origin-Resource-PolicyCross-Origin Resource Policy allows a resource owner to specify who can load the resource.
Additional Information
serverThis Server header seems to advertise the software being run on the server but you can remove or change this value.
public-key-pins-report-onlyHTTP Public Key Pinning Report Only allows a host to test the effects of a HPKP policy before making it live. The browser will report on actions that would have been taken if the policy were live so a host can see what effect it would have. Analyse this policy in more detail.
x-xss-protectionX-XSS-Protection sets the configuration for the XSS Auditor built into older browsers. The recommended value was "X-XSS-Protection: 1; mode=block" but you should now look at Content Security Policy instead.
expect-ctExpect-CT allows a site to determine if they are ready for the upcoming Chrome requirements and/or enforce their CT policy.
x-frame-optionsX-Frame-Options tells the browser whether you want to allow your site to be framed or not. By preventing a browser from framing your site you can defend against attacks like clickjacking.
x-content-type-optionsX-Content-Type-Options stops a browser from trying to MIME-sniff the content type and forces it to stick with the declared content-type. The only valid value for this header is "X-Content-Type-Options: nosniff".
strict-transport-securityHTTP Strict Transport Security is an excellent feature to support on your site and strengthens your implementation of TLS by getting the User Agent to enforce the use of HTTPS.
set-cookieThere is no Cookie Prefix on this cookie. This is not a SameSite Cookie.