Bot traffic: aiwayback.com

all sites · all domains · last 15 days

All sites · All Domains · Visit aiwayback.com

Who is really visiting aiwayback.com?

Between Oct 23 and Nov 6, aiwayback.com received 19,467 requests. About 98% came from automated software and about 1.2% look like real people.

That works out to about 120 human visitors, roughly 8 a day, who opened 159 pages between them. 33 of them read more than one page.

The biggest source is scanners hunting for security holes. They try the same list of common weak spots on every site they find.

Bottom line: the hit counts on the All Domains worksheet are almost entirely bots. Use the human visitor figure here to judge this site's real audience.

98%of requests from bots
120human visitors (estimate)
159pages opened by people
19,467total requests, 15 days

Where the requests came from

People 1.2%Named bots 28%Disguised bots 34%Scanners 36%Unclear 1.2%

Requests per day

PeopleNamed botsDisguised botsScannersUnclear
01,0002,0003,0004,000Oct 23Oct 25Oct 27Oct 29Oct 31Nov 2Nov 4Nov 6

Human visitors per day

Same days, people only, on their own scale so they are visible.

0481216Oct 23Oct 25Oct 27Oct 29Oct 31Nov 2Nov 4Nov 6

The breakdown

SourceRequestsΣ 19,467ShareData sentBlockedby the serverWhat this means
Disguised scrapers4,89025%59 MB0Claims to be a normal browser but only downloads pages, never the images or icons a real browser fetches, reads many pages without ever clicking a link, or runs from a cloud provider.
Break-in scanners4,22722%8 MB1,267Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers2,85215%22 MB31Other requests from an address also caught probing for weak spots.
Other named bots2,27112%18 MB20Any other software that identifies itself as a bot.
Search engines2,05711%14 MB43Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
Scripts and tools1,6628.5%14 MB4Programs such as curl or Python, or anything with an unrecognizable name.
AI crawlers6883.5%3 MB32AI companies gathering pages or answering a user's question, and saying so.
SEO and marketing tools3581.8%2 MB56Commercial tools that sell data about websites.
Unclear2291.2%<1 MB0Browser name, but fetched only an image or data file and no page. Could be either.
Likely people1560.8%2 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
Possibly people730.4%<1 MB0Read 1 to 3 pages, arrived from a search engine or social link, no icons fetched. Referrers can be faked, so treat these as maybe.
App link sweepers30.0%<1 MB0Touches only login, app or embed links and no actual content.
No name given10.0%<1 MB0Requests that give no software name at all.

Named bots

Botas it names itselfTypeRequests
RiverBotOther named bots943
PetalBotSearch engines847
bingbotSearch engines447
QlyzeBotOther named bots407
Amzn-SearchBotSearch engines375
ClaudeBotAI crawlers329
SERankingBacklinksBotSEO and marketing tools223
ElevenlabsCrawlerOther named bots214
OAI-SearchBotAI crawlers189
GooglebotSearch engines185
meta-webindexerOther named bots100
SeznamBotSearch engines81
BarkrowlerSEO and marketing tools78
ibou-searchOther named bots74
GPTBotAI crawlers69

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/82
/live/13
/guide.html11
/faq/2
/about/2

How people arrived

Referring siteHuman visitors
www.google.com27
m.baidu.com19
memsist.com19
duckduckgo.com3
www.bing.com1
fableguide.com1
www.reddit.com1

Where disguised bots operate from

Address blocks, not individual addresses. A heavily used block with many addresses suggests one operator rotating through them.

Address blockRequestsAddresses used
158.69.0.0/162922
192.42.0.0/1627855
47.82.0.0/16197188
66.249.0.0/1617217
45.138.0.0/16699
142.147.0.0/164949
141.94.0.0/164613
170.106.0.0/164525

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 236122483562621890096%
Oct 24710223359378898398%
Oct 2544195273301351697%
Oct 261214333387731482596%
Oct 271516430512265161,24197%
Oct 2866291410476161,20298%
Oct 2981323143291577597%
Oct 30352582523301886597%
Oct 31101521332162291,18697%
Nov 114189141,499688243,15998%
Nov 29115412861,497162,35999%
Nov 379211216749181,20797%
Nov 467350403870221,65598%
Nov 51013191499666151,39098%
Nov 64674535182171,20498%

How this was measured

Every request in the server log was sorted by what it did, not only what it claimed to be. Bots that name themselves are counted as named. Anything claiming to be a browser had to act like one: open a page, fetch its images or icons, move at human speed, and come from outside the big cloud providers. These are estimates. A careful bot can pass the test, and a person with images blocked or a cached icon can fail it, so read the human figures as a good approximation, not an exact count. One person using two devices counts as two visitors. Google Analytics-style tools would show different numbers because most bots never run their script. Logs are kept for 15 days.

Built 2026-11-06 22:42 UTC from 15 log files.