Website check
ebay.com
In plain English
Overall, ebay.com scored a B (81 out of 100) on this passive check. The biggest gap is the missing Content Security Policy, which limits which scripts a page can run, so fixing that first would do the most good. Visitors do not need to panic, because the remaining items are mostly low or informational and the check found no direct sign of an active break-in or stolen data.
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 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: bm_s, bm_so
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).
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).
What the agent did (13 steps)
- 01Picked up a daily rating check
- 02Looking up ebay.com and connecting over HTTPS
- 03Connected over HTTPS: www.ebay.com answered 403 after 1 redirect
- 04Certificate from Sectigo Limited, valid 97 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 0 script sources from other sites
- 09Old TLS 1.0/1.1: refused
- 10Plain http:// redirects to HTTPS
- 11No security.txt
- 12Email spoofing protection: SPF set, DMARC set
- 13Scored 81/100, grade B. Writing it up in plain English
Technical details (25)
- ip
- 23.46.228.173
- caa
- 0 issue "symantec.com", 0 iodef "mailto:dl-ebay-caa@ebay.com", 0 issue "digicert.com", 0 issue "sectigo.com"
- tls cipher
- TLS_AES_128_GCM_SHA256
- tls issuer
- Sectigo Limited
- tls subject
- www.ebay.com
- tls validTo
- 2027-01-27T23:59:59.000Z
- tls daysLeft
- 97
- tls protocol
- TLSv1.3
- tls authorized
- true
- email spf
- v=spf1 include:c._spf.ebay.com include:p._spf.ebay.com include:p2._spf.ebay.com ~all
- email apex
- ebay.com
- email dmarc
- v=DMARC1; p=reject; rua=mailto:ebay@rua.agari.com; ruf=mailto:ebay@ruf.agari.com; fo=1; rf=afrf; pct=100
- status
- 403
- cookies
- bm_s, bm_so
- headers server
- AkamaiGHost
- headers strict-transport-security
- max-age=31536000
- finalUrl
- https://www.ebay.com/
- requests
- 5
- timingMs
- 680
- reachable
- true
- oldTlsProbe
- rejected
- securityTxt
- false
- httpRedirect
- redirects to https
- thirdPartyScripts
- 0
- thirdPartyScriptHosts
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.