How the reach of OutfitTor grows
This page is calculated once a day at 23:58 on the administration server from the access logs — no counting cookies, no tracking script, no personal data. It shows who visits OutfitTor: search engines, AI platforms, people.
As of October 20, 2026, 23:58 — daily balance · online since September 5, 2026
The numbers at a glance
outfits online
freely visible, no sign-up
page views by people
129 visits in total
people on 10/20
1 page views on that day
votes
clicks in the duel in total
search engines
have fetched OutfitTor (confirmed)
AI platforms
have read OutfitTor
websites link here
to OutfitTor
messenger previews
services unpacked links
Search engines that read OutfitTor
These programs actually fetched pages of OutfitTor. The log shows the fetch — whether a page then lands in the search index is up to the operator and appears in no log file. "Fetched" is not the same as "indexed".
| operator | identifier | first seen | last seen | outfits read | verified |
|---|---|---|---|---|---|
Googlebot | 9/6 | 10/20 | 6 | ✔ confirmed | |
| Apple | Applebot | 9/6 | 10/20 | 6 | ✔ confirmed |
| Microsoft Bing | bingbot | 9/6 | 10/20 | 6 | ✔ confirmed |
| Yandex | YandexBot | 9/6 | 10/7 | 1 | ✔ confirmed |
| DuckDuckGo | DuckDuckBot | 9/23 | 9/23 | 1 | identifier only |
| Seznam | SeznamBot | 10/7 | 10/19 | 0 | identifier only |
AI platforms that know OutfitTor
The robots.txt of OutfitTor is deliberately open: AI systems may read along here. A site whose images were themselves created with artificial intelligence should not be locked away from artificial intelligence.
| operator | identifier | first seen | last seen | outfits read | verified |
|---|---|---|---|---|---|
| Anthropic Claude | ClaudeBot | 9/6 | 10/20 | 6 | identifier only |
| OpenAI | GPTBot | 9/6 | 10/20 | 5 | identifier only |
| Amazon Alexa | Amazonbot | 9/8 | 10/20 | 5 | identifier only |
| ByteDance | Bytespider | 9/6 | 10/20 | 3 | identifier only |
| Common Crawl | CCBot | 9/7 | 10/14 | 3 | identifier only |
| Meta AI | meta-externalagent | 9/9 | 10/16 | 1 | identifier only |
| Perplexity | PerplexityBot | 9/7 | 9/11 | 1 | identifier only |
| OpenAI ChatGPT Search | OAI-SearchBot | 9/6 | 10/20 | 0 | identifier only |
How many platforms — and how much do they read?
Left axis: how many platforms know OutfitTor. Right axis: how many outfits the individual platform had fetched by then.
Other programs
SEO tools and additional crawlers of large providers. They belong neither to a search engine nor to an AI service, but fetch the pages just the same.
| operator | identifier | first seen | last seen | outfits read | verified |
|---|---|---|---|---|---|
| Semrush | SemrushBot | 9/16 | 10/20 | 6 | identifier only |
| Google (weitere Dienste) | GoogleOther | 9/6 | 10/20 | 6 | ✔ confirmed |
| Majestic | MJ12bot | 9/7 | 10/7 | 5 | identifier only |
| Moz | DotBot | 9/24 | 10/20 | 3 | identifier only |
| Ahrefs | AhrefsBot | 9/8 | 10/20 | 2 | identifier only |
Shared and linked
| website | kind | since | clicks |
|---|---|---|---|
| google.com | suche | 9/9 | 1 |
| webdig.asia | sonstige | 9/27 | 1 |
Messenger previews
| service | first seen | last seen | previews |
|---|---|---|---|
| 9/15 | 10/17 | 8 |
How links and previews develop
How the visits develop
Bars: page views by people on that day. Line (right axis): all page views since the start, added up.
Votes in the duel
How often per day somebody clicked an outfit in the duel. Counted are requests to the voting endpoint — not who clicked.
Machine traffic
For comparison: what crawlers and scanners fetched on the same day. These requests never count as a visit.
Most viewed outfits
Not enough data yet — as soon as people look at individual outfits, the ranking appears here.
Most visited views
| # | page | views by people |
|---|---|---|
| 1 | duel (home page) | 169 |
| 2 | Filter — configurator | 37 |
| 3 | Tips — recommendations | 14 |
| 4 | Top — personal ranking | 12 |
| 5 | Last — own votes | 8 |
| 6 | all outfits | 4 |
How these numbers come about
The only source is the Apache access log of this server; a background program on the administration server fetches it once a day, calculates the daily balance there at 23:58 and only stores the finished sums here as a small file. This server calculates nothing for it — it only delivers. Human or machine is distinguished by three signs: the identifier must look like a real browser, the page must have been delivered successfully, and the same sender must have fetched the stylesheet, the JavaScript or an image within two minutes — a browser loads those automatically, a crawler usually does not. Search engines are cross-checked: for Google, Bing, Apple and Yandex the sender is resolved via reverse DNS; only if the name really points to the operator does it say "confirmed" here. Not counted are attack and scanner requests (the hunt for wp-login, .env and the like), accesses from our own administration server, redirects and error pages, as well as programs with a browser identifier that load no files. Privacy: "visitors per day" is counted from the access log of this server; a person cannot be traced from it. The counting happens on the administration server; the file this server delivers contains sums only. There are no counting cookies, no tracking script and no sharing with third parties. And the most important limitation: "fetched" does not mean "indexed" — the log only sees the fetch, not what a search engine or an AI model makes of it.
Questions and answers
Why are the human numbers so much smaller than the bot numbers?
Because that is normal. A young site is discovered by crawlers first; people only come once the content shows up in search results and AI answers. This page makes exactly that path visible.
Why are the numbers updated only once a day?
Because the machine that delivers this page is small and should spend its power on delivering. The evaluation therefore runs at night on another machine, and only the finished result arrives here. For a growth curve one value per day is the right resolution anyway.
Can I trust these numbers?
They are as honest as a log file allows: no extrapolation, no estimate, no smoothed curves. Where a heuristic is involved, it is stated in the box above — and where nothing has happened yet, there is a zero instead of a pretty placeholder.