Bot traffic: whensthegame.com

all sites · all domains · last 15 days

All sites · All Domains · Visit whensthegame.com

Who is really visiting whensthegame.com?

Between Oct 23 and Nov 6, whensthegame.com received 37,626 requests. About 99.1% came from automated software and about 0.4% look like real people.

That works out to about 70 human visitors, roughly 5 a day, who opened 112 pages between them. 38 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.

99.1%of requests from bots
70human visitors (estimate)
112pages opened by people
37,626total requests, 15 days

Where the requests came from

People 0.4%Named bots 15%Disguised bots 9.8%Scanners 74%Unclear 0.5%

Requests per day

PeopleNamed botsDisguised botsScannersUnclear
01,5003,0004,5006,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Σ 37,626ShareData sentBlockedby the serverWhat this means
Break-in scanners23,07061%30 MB12,503Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers4,77013%22 MB52Other requests from an address also caught probing for weak spots.
Disguised scrapers2,4956.6%30 MB3Claims 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 engines2,4406.5%17 MB8Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
Other named bots1,5054.0%10 MB32Any other software that identifies itself as a bot.
AI crawlers1,3013.5%2 MB117AI companies gathering pages or answering a user's question, and saying so.
Scripts and tools1,1773.1%4 MB4Programs such as curl or Python, or anything with an unrecognizable name.
SEO and marketing tools5231.4%4 MB61Commercial tools that sell data about websites.
Unclear1840.5%<1 MB0Browser name, but fetched only an image or data file and no page. Could be either.
Possibly people930.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.
Likely people560.1%<1 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
No name given110.0%<1 MB0Requests that give no software name at all.
Calendar and feed apps10.0%<1 MB0Software fetching a feed for someone who subscribed.

Named bots

Botas it names itselfTypeRequests
PetalBotSearch engines994
bingbotSearch engines776
ClaudeBotAI crawlers230
GooglebotSearch engines228
RiverBotOther named bots183
OAI-SearchBotAI crawlers152
DataForSeoBotSEO and marketing tools148
QlyzeBotOther named bots142
serpstatbotSEO and marketing tools136
Amzn-SearchBotSearch engines117
BytespiderAI crawlers115
BarkrowlerSEO and marketing tools108
ibou-searchOther named bots92
ElevenlabsCrawlerOther named bots91
PerplexityBotAI crawlers84

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/42
/tickets/nba/2
/social.html2

How people arrived

Referring siteHuman visitors
www.google.com25
m.baidu.com18
search.yahoo.com11
duckduckgo.com3
www.bing.com2
us.search.yahoo.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/161681
66.249.0.0/161583
102.129.0.0/16871
45.138.0.0/16663
192.42.0.0/166517
192.210.0.0/16601
158.173.0.0/16502
43.166.0.0/163517

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 23464021441,268161,83699%
Oct 24362102781,18491,68799.1%
Oct 2545197159762161,14098%
Oct 2611212911684,21294,72699%
Oct 276103692641,330101,98499%
Oct 2811192216683111,10399%
Oct 2957213158200758598%
Oct 30697072151,601132,54699.1%
Oct 31691801491,568121,91899%
Nov 18138501,1152,148294,15799%
Nov 2247191802,41163,32099.7%
Nov 3572491302,618103,01599.4%
Nov 4332371981,453231,91499%
Nov 5465892234,933115,76899.6%
Nov 635365861,46921,92799.6%

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:43 UTC from 15 log files.