Website check
microsoft.com
In plain English
Overall, this passive check gives microsoft.com a B (75 out of 100). The most important item to fix first is the missing Content Security Policy, which would limit which scripts can run on the pages and make code-injection attacks harder. The other findings are mostly low severity, covering cookie settings, framing, and a few browser headers. Visitors do not need to panic, but the site owner should work through the list, starting with the Content Security Policy.
No Content Security Policy
A Content Security Policy limits which scripts can run, which blunts attacks that inject code to steal logins or change the page.
How to fix: Add a Content-Security-Policy header. Start in report-only mode, then enforce it once nothing breaks.
Cookies sent without the Secure flag
These cookies can travel over plain HTTP, where anyone on the same network can read them.
How to fix: Add the Secure attribute to every cookie the site sets.
Cookies: ak_bmsc
Cookies without a SameSite setting
Without SameSite, some browsers send these cookies along with requests started by other sites, which helps cross-site request forgery.
How to fix: Add SameSite=Lax (or Strict) to cookies. Use SameSite=None only together with Secure, and only when truly needed.
Cookies: ak_bmsc
Page can be framed by other sites
Another site could load this page in a hidden frame and trick visitors into clicking things (clickjacking).
How to fix: Send X-Frame-Options: DENY (or SAMEORIGIN), or add a frame-ancestors rule to the Content Security Policy.
No X-Content-Type-Options header
Browsers may guess file types, which can let an uploaded file run as a script.
How to fix: Send X-Content-Type-Options: nosniff.
No Referrer-Policy header
Some browsers may pass full page addresses, including any private details in them, to other sites visitors go to.
How to fix: Send Referrer-Policy: strict-origin-when-cross-origin (or stricter).
Third-party scripts without integrity checks
The page loads scripts from other companies' servers without a fingerprint check. If one of those servers is hacked, the attacker's code runs on this site.
How to fix: Add integrity and crossorigin attributes to fixed-version third-party scripts, or host the files yourself.
rum.hlx.page
No Permissions-Policy header
This header lets the site switch off features like the camera, microphone and location for itself and anything it embeds.
How to fix: Send a Permissions-Policy header that turns off features you do not use, for example camera=(), microphone=(), geolocation=().
What the agent did (13 steps)
- 01Picked up a daily rating check
- 02Looking up microsoft.com and connecting over HTTPS
- 03Connected over HTTPS: www.microsoft.com answered 200 after 2 redirects
- 04Certificate from Microsoft Corporation, valid 87 more days (TLSv1.3)
- 05Read the security headers: HSTS set; missing CSP, X-Frame-Options, nosniff, Referrer-Policy
- 06Checked 2 cookies for Secure, HttpOnly and SameSite
- 07No PHP version given away
- 08Found 1 script source from other sites
- 09Old TLS 1.0/1.1: refused
- 10Plain http:// redirects to HTTPS
- 11security.txt found
- 12Email spoofing protection: SPF set, DMARC set
- 13Scored 75/100, grade B. Writing it up in plain English
Technical details (24)
- ip
- 184.30.153.155
- caa
- 0 other ""
- tls cipher
- TLS_AES_256_GCM_SHA384
- tls issuer
- Microsoft Corporation
- tls subject
- www.microsoft.com
- tls validTo
- 2027-01-17T19:55:21.000Z
- tls daysLeft
- 87
- tls protocol
- TLSv1.3
- tls authorized
- true
- email spf
- v=spf1 include:_spf-a.microsoft.com include:_spf-b.microsoft.com include:_spf-c.microsoft.com include:_spf-ssg-a.msft.net include:_spf1-meo.microsoft.com -all
- email apex
- microsoft.com
- email dmarc
- v=DMARC1; p=reject; pct=100; rua=mailto:itex-rua@microsoft.com; ruf=mailto:itex-ruf@microsoft.com; fo=1
- status
- 200
- cookies
- CAS_PROGRAM, ak_bmsc
- headers strict-transport-security
- max-age=31536000; includeSubDomains
- finalUrl
- https://www.microsoft.com/en-us
- requests
- 5
- timingMs
- 589
- reachable
- true
- oldTlsProbe
- rejected
- securityTxt
- true
- httpRedirect
- redirects to https
- thirdPartyScripts
- 1
- thirdPartyScriptHosts
- rum.hlx.page
This check is passive and automated: it reads only what a normal visit can see and can miss problems a full audit would find. A good grade is not a guarantee. If you run this site and something here is wrong, the fix steps are a starting point, not a substitute for your host or a security professional.