Bot traffic: childrenstory.net

all sites · all domains · last 15 days

All sites · All Domains · Visit childrenstory.net

Who is really visiting childrenstory.net?

Between Oct 23 and Nov 6, childrenstory.net received 34,267 requests. About 98% came from automated software and about 0.8% look like real people.

That works out to about 75 human visitors, roughly 5 a day, who opened 101 pages between them. 26 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
75human visitors (estimate)
101pages opened by people
34,267total requests, 15 days

Where the requests came from

People 0.8%Named bots 13%Disguised bots 14%Scanners 71%Unclear 0.7%

Requests per day

PeopleNamed botsDisguised botsScannersUnclear
01,2502,5003,7505,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.

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

The breakdown

SourceRequestsΣ 34,267ShareData sentBlockedby the serverWhat this means
Break-in scanners20,09659%1 MB14,280Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers4,12712%3 MB29Other requests from an address also caught probing for weak spots.
Disguised scrapers3,54610%12 MB1Claims 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.
Search engines1,9265.6%8 MB0Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
Other named bots1,4944.4%3 MB4Any other software that identifies itself as a bot.
Scripts and tools1,3413.9%<1 MB14Programs such as curl or Python, or anything with an unrecognizable name.
AI crawlers7752.3%<1 MB24AI companies gathering pages or answering a user's question, and saying so.
SEO and marketing tools4311.3%<1 MB114Commercial tools that sell data about websites.
Unclear2370.7%5 MB0Browser name, but fetched only an image or data file and no page. Could be either.
Likely people2320.7%1 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
Possibly people580.2%<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
PetalBotSearch engines1,005
QlyzeBotOther named bots535
ClaudeBotAI crawlers423
bingbotSearch engines272
ElevenlabsCrawlerOther named bots265
Amzn-SearchBotSearch engines229
SERankingBacklinksBotSEO and marketing tools216
GooglebotSearch engines161
meta-webindexerOther named bots122
SemrushBotSEO and marketing tools116
BarkrowlerSEO and marketing tools95
OAI-SearchBotAI crawlers90
GPTBotAI crawlers85
ibou-searchOther named bots85
ApplebotSearch engines58

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/40
/tales/index.html3
/rhymes/indexnew.html2
/stories/index.html2
/tales/lgb/2
/tales/sounds/p-ptest.ram2
/tales/ft2.html2

How people arrived

Referring siteHuman visitors
m.baidu.com21
www.google.com14
duckduckgo.com2
claudefieldguide.com1
www.google.com.hk1

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
66.249.0.0/164893
192.42.0.0/1629937
164.68.0.0/161521
45.138.0.0/161514
152.53.0.0/161171
104.164.0.0/161043
37.60.0.0/16951
183.207.0.0/16754

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 23561421931,320131,69198%
Oct 24241842581,36071,81399.4%
Oct 25662011421,483131,87597%
Oct 26693962564,31944,98499.7%
Oct 271215575501835121,93999%
Oct 28893751661,328191,94096%
Oct 294628847640541,18099.1%
Oct 3055133219944181,32298%
Oct 31461671564,306564,69799%
Nov 19121,1751,2232,316414,80198%
Nov 2551852732,250112,73999%
Nov 3462421871,828142,28199%
Nov 4451452084011077198%
Nov 5243284031,08191,84798%
Nov 6239023047638795%

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.