Website report · 03 Nov 2026

sexbot.services

“Sexbot”

Template-written 9 evidence items Code reader analysed 8 scripts
What this means for you

Sexbot only talked to its own servers while we watched.E1

  • We saw no known analytics or advertising services load on the first visit.E1

Tech check

What the site says about itself, next to what its public page actually loads. Facts only, no verdict: you decide.

The page doesn't make tech claims we check for (AI, on-chain, wallets, trading, own chain, staking, live data, an app).

Calls its own backend /content.jsonE6
Wallet code none seen
Contract calls in its code none seen
Talks to AI services none seen
Live connections none seen

What it is

  • The Internet Archive first saved this site on 2025-01-25 (648 days ago).E9
  • The site describes itself as: “Sex is solved. Explore Sexbot.”E2
  • It has sections such as /kidding.E8
  • While loading, it called 1 endpoint on its own servers, such as /content.json.E6

Where your data goes

On a first visit the page only talked to its own servers (sexbot.services).

How key features work

Loading its content

Its content loads from its own API while you browse (/content.json).E6

/content.json

Saving data on your device

It saves data in your browser (sessionStorage), so some things persist between visits.E5

sessionStorage

Cookies and storage

Names only. We never store the values.

sessionStorageE5: sexbot-attribution

Pages and API calls

Pages it links to

//kidding

Endpoints

Called while loading (seen) or named in the code (code).

sexbot.services/content.jsonseenE6
/content.jsoncodeE7

Evidence

Every sentence above points to one of these. Code references show the file, line:column and the short identifier that matched, never the site's code itself.

E1
Page title: Sexbot
page title · https://sexbot.services/
E2
Page description: Sex is solved. Explore Sexbot.
page description · https://sexbot.services/
E3
Site name: Sexbot
page site_name · https://sexbot.services/
E4
27 request(s) to sexbot.services
types: 9 image, 8 script, 3 font
GET https://sexbot.services/ · image · 27 requests · network recording
E5
sessionStorage: 1 key(s) saved in your browser
sessionStorage keys: sexbot-attribution · values not stored
E6
The page called /content.json on sexbot.services (GET)
GET https://sexbot.services/content.json · fetch · network recording
E7
Code reader found the endpoint /content.json
how: call:fetch
sexbot.services/app.js @ 16:38 · “/content.json” · the code reader
E8
2 links to pages on the same site
page links · https://sexbot.services/ · /, /kidding
E9
The Internet Archive first saved sexbot.services on 2025-01-25 and has snapshots from 5 different days
page web archive · https://web.archive.org/web/20250125075519/sexbot.services

Limits

  • We only see what your browser sees: code and requests on a first visit, without logging in or accepting cookie banners. What the servers do with data is invisible from outside.
  • Site code is usually minified (compressed), so names are partly lost and some code may be only partly analysed.
  • Some trackers only load after you accept cookies or log in, so the real list can be longer.
  • We visited from a server in the United States. Sites load different trackers and cookie banners in different countries (visitors in the EU usually get a consent banner first).
  • This text was written from fixed templates because no AI writer was available. It uses exactly the same evidence.

Facts, not judgements: this page describes what the code and traffic show, not anyone's intent. Not financial advice. Case id 3iKIWaAL.