Bot traffic: atemcooler.com

all sites · all domains · last 15 days

All sites · All Domains · Visit atemcooler.com

Who is really visiting atemcooler.com?

Between Oct 23 and Nov 6, atemcooler.com received 39,920 requests. About 99% came from automated software and about 0.8% look like real people.

That works out to about 167 human visitors, roughly 11 a day, who opened 251 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 1, with 6,959 requests, of which 39 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.

99%of requests from bots
167human visitors (estimate)
251pages opened by people
39,920total requests, 15 days

Where the requests came from

People 0.8%Named bots 11%Disguised bots 9.4%Scanners 78%Unclear 0.6%

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.

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

The breakdown

SourceRequestsΣ 39,920ShareData sentBlockedby the serverWhat this means
Break-in scanners24,98763%30 MB11,050Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers6,05315%26 MB67Other requests from an address also caught probing for weak spots.
Disguised scrapers2,5056.3%22 MB4Claims 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.
AI crawlers1,9855.0%3 MB91AI companies gathering pages or answering a user's question, and saying so.
Other named bots1,2463.1%5 MB35Any other software that identifies itself as a bot.
Search engines1,1662.9%5 MB12Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
Scripts and tools1,1522.9%3 MB9Programs such as curl or Python, or anything with an unrecognizable name.
Unclear2380.6%<1 MB0Browser name, but fetched only an image or data file and no page. Could be either.
Likely people1670.4%1 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
SEO and marketing tools1660.4%<1 MB82Commercial tools that sell data about websites.
Possibly people1520.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.
No name given1030.3%<1 MB5Requests that give no software name at all.

Named bots

Botas it names itselfTypeRequests
GPTBotAI crawlers683
GooglebotSearch engines368
PetalBotSearch engines330
OAI-SearchBotAI crawlers194
ClaudeBotAI crawlers194
bingbotSearch engines156
ChatGPT-UserAI crawlers102
RiverBotOther named bots88
HunyuanOther named bots86
BytespiderAI crawlers80
DuckAssistBotOther named bots77
Claude-SearchBotAI crawlers76
BaiduspiderSearch engines73
AmazonbotAI crawlers72
claudebotAI crawlers70

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/96
/atem-mini-cooling/17
/mini-pcs/9
/switchers-explained/9
/live-production-setup/8
/thermal-management/7
/gear-guide/5
/faq/4
/about/3
/about.html3
/sources/3
/guide/2

How people arrived

Referring siteHuman visitors
www.google.com51
far-uvclight.com51
m.baidu.com19
www.bing.com2
duckduckgo.com2
www.wholetech.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/1614429
66.249.0.0/161203
102.129.0.0/16872
158.69.0.0/16682
185.220.0.0/164614
178.20.0.0/16441
84.54.0.0/16403
45.152.0.0/16401

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 235713626693561,35299%
Oct 241217160217574797897%
Oct 25444041362,55363,10399.7%
Oct 2624344562963,97094,77599%
Oct 27151921717593091,35398%
Oct 2820212211411,98982,39198%
Oct 2922361432153,45283,85699%
Oct 3010115081641,939832,70696%
Oct 311014133159760241,09696%
Nov 119293211,1365,430336,95999%
Nov 2791861792,278122,66699.1%
Nov 3362792062,298122,80199.4%
Nov 415276331901,42272,28998%
Nov 5686591561,66452,49599.4%
Nov 67910712484691,10098%

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.