Bot traffic: carolekatchen.com

all sites · all domains · last 15 days

All sites · All Domains · Visit carolekatchen.com

Who is really visiting carolekatchen.com?

Between Oct 23 and Nov 6, carolekatchen.com received 30,761 requests. About 93% came from automated software and about 3.8% look like real people.

That works out to about 286 human visitors, roughly 19 a day, who opened 403 pages between them. 53 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.

The busiest day was Nov 2, with 6,072 requests, of which 45 came from people.

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.

93%of requests from bots
286human visitors (estimate)
403pages opened by people
30,761total requests, 15 days

Where the requests came from

People 3.8%Named bots 14%Disguised bots 12%Scanners 68%Unclear 2.8%

Requests per day

PeopleNamed botsDisguised botsScannersUnclear
02,0004,0006,0008,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.

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

The breakdown

SourceRequestsΣ 30,761ShareData sentBlockedby the serverWhat this means
Break-in scanners13,93845%26 MB4,835Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers7,01023%31 MB49Other requests from an address also caught probing for weak spots.
Disguised scrapers2,6238.5%87 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.
Other named bots1,6175.3%54 MB21Any other software that identifies itself as a bot.
Search engines1,2254.0%37 MB4Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
Likely people9203.0%497 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
AI crawlers9012.9%2 MB53AI companies gathering pages or answering a user's question, and saying so.
Unclear8552.8%87 MB0Browser name, but fetched only an image or data file and no page. Could be either.
Scripts and tools8322.7%306 MB2Programs such as curl or Python, or anything with an unrecognizable name.
SEO and marketing tools4811.6%<1 MB329Commercial tools that sell data about websites.
Possibly people2430.8%3 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.
No name given1160.4%<1 MB0Requests that give no software name at all.

Named bots

Botas it names itselfTypeRequests
PetalBotSearch engines493
ClaudeBotAI crawlers417
GooglebotSearch engines331
MJ12botSEO and marketing tools311
pathscanOther named bots155
bingbotSearch engines150
OAI-SearchBotAI crawlers149
google.comOther named bots142
ImageMetaBotOther named bots115
GPTBotAI crawlers69
RiverBotOther named bots69
YouBotAI crawlers66
sogou.comSearch engines65
ibou-searchOther named bots60
SemrushBotSEO and marketing tools60

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/241
/rss-api12
/news/11
/social/10
/about/9
/faq/8
/sitemap.html7
/resources/6
/research/4
/videos/4
/stuff/2

How people arrived

Referring siteHuman visitors
beckieleone.blogspot.com188
m.baidu.com19
www.google.com10
medaiprotect.com3
litiongod.ru1
scriblihelp.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
192.42.0.0/1622230
66.249.0.0/161405
102.129.0.0/161021
185.220.0.0/167711
5.102.0.0/16661
43.166.0.0/165125
104.164.0.0/16482
104.28.0.0/16453

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 237578318196743781,41789%
Oct 248398233210557431,20483%
Oct 2547492662301,054721,68692%
Oct 2669200259733391,30691%
Oct 271130255302358281,10383%
Oct 28454163402,044472,85598%
Oct 29911223235566541,09094%
Oct 301729326283773681,59687%
Oct 31462742361,219491,78497%
Nov 19263322861,453832,29690%
Nov 27162662465,3921236,07297%
Nov 38124821581,567442,35394%
Nov 4232391631,591392,03598%
Nov 517291772821,299561,96989%
Nov 6122171451,599321,99598%

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.