Bot traffic: steamlearn.com

all sites · all domains · last 15 days

All sites · All Domains · Visit steamlearn.com

Who is really visiting steamlearn.com?

Between Oct 23 and Nov 6, steamlearn.com received 31,364 requests. About 98% came from automated software and about 1.1% look like real people.

That works out to about 120 human visitors, roughly 8 a day, who opened 233 pages between them. 49 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)
233pages opened by people
31,364total requests, 15 days

Where the requests came from

People 1.1%Named bots 8.7%Disguised bots 11%Scanners 79%Unclear 0.6%

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.

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

The breakdown

SourceRequestsΣ 31,364ShareData sentBlockedby the serverWhat this means
Break-in scanners19,17661%25 MB12,199Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers5,50718%22 MB33Other requests from an address also caught probing for weak spots.
Disguised scrapers2,3087.4%16 MB6Claims 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.
Scripts and tools1,1173.6%2 MB5Programs such as curl or Python, or anything with an unrecognizable name.
Search engines8612.7%3 MB4Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
Other named bots8522.7%4 MB13Any other software that identifies itself as a bot.
AI crawlers8302.6%1 MB66AI companies gathering pages or answering a user's question, and saying so.
Likely people3061.0%2 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
SEO and marketing tools1830.6%<1 MB71Commercial tools that sell data about websites.
Unclear1800.6%<1 MB0Browser name, but fetched only an image or data file and no page. Could be either.
Possibly people410.1%<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 given30.0%<1 MB0Requests that give no software name at all.

Named bots

Botas it names itselfTypeRequests
PetalBotSearch engines312
ClaudeBotAI crawlers212
GooglebotSearch engines184
bingbotSearch engines115
OAI-SearchBotAI crawlers98
GPTBotAI crawlers78
QlyzeBotOther named bots70
BytespiderAI crawlers62
SemrushBotSEO and marketing tools61
Amzn-SearchBotSearch engines55
ApplebotSearch engines50
leakix.netOther named bots48
ibou-searchOther named bots47
SERankingBacklinksBotSEO and marketing tools46
ElevenlabsCrawlerOther named bots43

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/76
/videos/10
/resources/10
/social/9
/social.html9
/news/8
/rss-api8
/faq/8
/faq.html7
/resources.html6
/sources/4
/about/4

How people arrived

Referring siteHuman visitors
m.baidu.com19
www.google.com3
www.bing.com3
chatgpt.com1
duckduckgo.com1
roozzy.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/1614533
66.249.0.0/1612810
93.123.0.0/16941
45.138.0.0/16824
183.207.0.0/16503
5.102.0.0/16462
158.69.0.0/16411
173.46.0.0/16342

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 238271701721,489111,87798%
Oct 2481091215926111,25798%
Oct 25553081471,826122,30399.0%
Oct 269232702031,80652,31598%
Oct 276997290897121,30998%
Oct 2818191142052,334222,71298%
Oct 291530152233434586595%
Oct 304819617174771,13498%
Oct 3147108117938111,18898%
Nov 125472691,1062,631244,10098%
Nov 2451511562,55082,87499.4%
Nov 3792151254,628124,99399.5%
Nov 412273091321,072231,57296%
Nov 534149881,23241,47999.3%
Nov 623127681,173131,38699%

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.