Website check
wix.com
In plain English
Wix.com scores B (81/100) on this passive check. The findings are mostly hardening gaps rather than active problems, and nothing here shows the site is currently compromised. The most important fix is adding a Content Security Policy, since it limits which scripts can run and makes code-injection attacks harder. Visitors do not need to panic, but the site owner should work through the list, starting with the medium item and the cookie settings.
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: _wixAB3, ssr-caching
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: _wixAB3, ssr-caching
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.
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.
static.parastorage.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 security.txt file
security.txt tells researchers how to report a security problem to you. Without it, reports may go unsent or to the wrong place.
How to fix: Publish /.well-known/security.txt with at least a Contact: line and an Expires: date (see securitytxt.org).
No CAA record
CAA records limit which certificate authorities may issue certificates for wix.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 (13 steps)
- 01Picked up a daily rating check
- 02Looking up wix.com and connecting over HTTPS
- 03Connected over HTTPS: www.wix.com answered 200 after 1 redirect
- 04Certificate from Let's Encrypt, valid 70 more days (TLSv1.3)
- 05Read the security headers: HSTS, nosniff, Referrer-Policy set; missing CSP, X-Frame-Options
- 06Checked 6 cookies for Secure, HttpOnly and SameSite
- 07No PHP version given away
- 08Found 2 script sources from other sites
- 09Plain http:// redirects to HTTPS
- 10Old TLS 1.0/1.1: refused
- 11No security.txt
- 12Email spoofing protection: SPF set, DMARC set
- 13Scored 81/100, grade B. Writing it up in plain English
Technical details (28)
- ip
- 34.149.87.45
- caa
- tls cipher
- TLS_AES_256_GCM_SHA384
- tls issuer
- Let's Encrypt
- tls subject
- *.wix.com
- tls validTo
- 2026-12-31T11:33:52.000Z
- tls daysLeft
- 70
- tls protocol
- TLSv1.3
- tls authorized
- true
- email spf
- v=spf1 include:wix.com._nspf.vali.email include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all
- email apex
- wix.com
- email dmarc
- v=DMARC1; p=quarantine; rua=mailto:dmarc_agg@vali.email,mailto:postmaster@wix.com
- status
- 200
- cookies
- _wixAB3, sec-fetch-unsupported, ssr-caching, XSRF-TOKEN, _wixCIDX, _wixUIDX
- headers server
- Pepyaka
- headers referrer-policy
- no-referrer-when-downgrade
- headers x-content-type-options
- nosniff
- headers strict-transport-security
- max-age=31536000
- finalUrl
- https://www.wix.com/
- requests
- 4
- timingMs
- 645
- reachable
- true
- oldTlsProbe
- rejected
- securityTxt
- false
- httpRedirect
- redirects to https
- bodyTruncated
- true
- thirdPartyScripts
- 2
- thirdPartyScriptHosts
- static.parastorage.com, accounts.google.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.