Security Report Summary
C
Site: https://login.microsoftonline.com/e0793d39-0939-496d-b129-198edd916feb/saml2?samlrequest=fzfnb8iwdib/spv72lcg0igwsu3tkjigooywc0qzqas1thcn+/j3k3ri7mlrdqzn8zvz/lupg09lurviycbkjfagzbugkio74pfoytyfowjqli+8o8bgfxifluj2apl5kbfvgrubgjmirif3km8xzyseh4y31jgjtu2c5ung9quajmlayne6ge+kkovuptjo2eqxivi5ecmiddjykiqjxi9e8clriejvetajcf2lxyyyha5zwcz8noqsfspb+g92p6e/4zzz2t9c/lqua7p+2rykwcaq6zrovqh0jbjbzt+1vlvnkimh51rkuvtwpgqflaqctyqupomo5gd7477x1oqfiar9zvzsbk/cum0klnss32b9tvqacf0namtfacco0acnfvapeqlqlhvstqu7uldadusz6eoo76v/x5r/ag==
IP Address: 40.126.0.68
Report Time: 24 Jan 2021 06:37:07 UTC
Headers:
  • Strict-Transport-Security
  • X-Content-Type-Options
  • Referrer-Policy
  • Content-Security-Policy
  • X-Frame-Options
  • Permissions-Policy
Supported By
Probely
Not bad… Maybe you should perform a deeper security analysis of your website and APIs:
Raw Headers
HTTP/1.1400 Bad Request
Cache-Controlno-store, no-cache
Pragmano-cache
Content-Length150326
Content-Typetext/html; charset=utf-8
Expires-1
Strict-Transport-Securitymax-age=31536000; includeSubDomains
X-Content-Type-Optionsnosniff
Link<https://aadcdn.msauth.net>; rel=preconnect; crossorigin
Link<https://aadcdn.msauth.net>; rel=dns-prefetch
Link<https://aadcdn.msftauth.net>; rel=dns-prefetch
X-DNS-Prefetch-Controlon
P3PCP="DSP CUR OTPi IND OTRi ONL FIN"
x-ms-request-iddc8e407d-3224-4d57-8914-43c538b02900
x-ms-ests-server2.1.11419.13 - SAN ProdSlices
Set-Cookiefpc=Apnu2dm1-HRJm0wcTInpG2o; expires=Tue, 23-Feb-2021 06:37:07 GMT; path=/; secure; HttpOnly; SameSite=None
Set-Cookieesctx=AQABAAAAAABeStGSRwwnTq2vHplZ9KL4x8Ja3HkMDU-3QTm7dHHEp7hn4zxsvMCxtP5lTF5NqOJ128Hi6eGAqg-sRA7zY8otaOKir6fUaBzFPbCa3Firt_YQNVfQpBw_49fnmGfSJ9ZdrVhDKL5pJUhWjpmxJoR5ROLyQ0bxaAuBtuNAuh4-VJimzsQQE_KryZOZCJyyl5sgAA; domain=.login.microsoftonline.com; path=/; secure; HttpOnly; SameSite=None
Set-Cookiex-ms-gateway-slice=prod; path=/; secure; samesite=none; httponly
Set-Cookiestsservicecookie=ests; path=/; secure; samesite=none; httponly
Referrer-Policystrict-origin-when-cross-origin
DateSun, 24 Jan 2021 06:37:06 GMT
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.
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. Recommended value "X-Frame-Options: SAMEORIGIN".
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
Expect-CTExpect-CT allows a site to determine if they are ready for the upcoming Chrome requirements and/or enforce their CT policy.
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
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.
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".
Set-CookieThere is no Cookie Prefix on this cookie. This is not a SameSite Cookie.
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.