Website check
binance.com
In plain English
Overall, binance.com scores a B (74/100) on this passive check. The main gaps are missing HSTS and Content Security Policy headers, which are standard protections that would make the site harder to attack, and the owner should add HSTS first since it guards the very first connection a visitor makes on untrusted networks. This is a list of hardening steps rather than evidence of an active problem, so visitors have no reason to panic, though they should still use the official site and avoid public Wi-Fi when logging in or handling funds.
No HSTS header
Without HSTS, a visitor's first connection can be quietly downgraded to plain HTTP on hostile Wi-Fi, exposing what they send.
How to fix: Send Strict-Transport-Security: max-age=31536000; includeSubDomains on every HTTPS response.
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.
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.
fe4385362baa.1a93bdf2.us-west-2.token.awswaf.com
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=().
No CAA record
CAA records limit which certificate authorities may issue certificates for binance.com, which makes a wrongly issued certificate less likely.
How to fix: Add a CAA record naming your certificate provider, for example 0 issue "letsencrypt.org".
What the agent did (12 steps)
- 01Picked up a daily rating check
- 02Looking up binance.com and connecting over HTTPS
- 03Connected over HTTPS: www.binance.com answered 202 after 1 redirect
- 04Certificate from DigiCert Inc, valid 79 more days (TLSv1.3)
- 05Read the security headers: none set; missing HSTS, CSP, X-Frame-Options, nosniff, Referrer-Policy
- 06No PHP version given away
- 07Found 1 script source from other sites
- 08Old TLS 1.0/1.1: refused
- 09Plain http:// redirects to HTTPS
- 10security.txt found
- 11Email spoofing protection: SPF set, DMARC set
- 12Scored 74/100, grade B. Writing it up in plain English
Technical details (24)
- ip
- 143.204.1.62
- caa
- tls cipher
- TLS_AES_128_GCM_SHA256
- tls issuer
- DigiCert Inc
- tls subject
- *.binance.com
- tls validTo
- 2027-01-09T23:59:59.000Z
- tls daysLeft
- 79
- tls protocol
- TLSv1.3
- tls authorized
- true
- email spf
- v=spf1 include:_spf_smail.binance.com include:_spf.google.com -all
- email apex
- binance.com
- email dmarc
- v=DMARC1; p=quarantine; rua=mailto:binance@rua.netcraft.com,mailto:dmarc@binance.com; ruf=mailto:binance@ruf.netcraft.com,mailto:dmarc@binance.com;
- status
- 202
- cookies
- headers server
- CloudFront
- finalUrl
- https://www.binance.com/
- requests
- 4
- timingMs
- 760
- reachable
- true
- oldTlsProbe
- rejected
- securityTxt
- true
- httpRedirect
- redirects to https
- thirdPartyScripts
- 1
- thirdPartyScriptHosts
- fe4385362baa.1a93bdf2.us-west-2.token.awswaf.com
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.