Bot traffic: hoopwomen.com

all sites · all domains · last 15 days

All sites · All Domains · Visit hoopwomen.com

Who is really visiting hoopwomen.com?

Between Oct 23 and Nov 6, hoopwomen.com received 17,651 requests. About 94% came from automated software and about 3.7% look like real people.

That works out to about 166 human visitors, roughly 11 a day, who opened 385 pages between them. 37 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 Oct 26, with 3,951 requests, of which 33 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.

94%of requests from bots
166human visitors (estimate)
385pages opened by people
17,651total requests, 15 days

Where the requests came from

People 3.7%Named bots 38%Disguised bots 18%Scanners 39%Unclear 1.8%

Requests per day

PeopleNamed botsDisguised botsScannersUnclear
01,0002,0003,0004,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.

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

The breakdown

SourceRequestsΣ 17,651ShareData sentBlockedby the serverWhat this means
Break-in scanners4,88428%1 MB4Probing for WordPress logins, password files and other common weak spots.
Search engines3,49820%17 MB0Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
Disguised scrapers2,53614%25 MB2Claims 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 bots2,00611%12 MB7Any other software that identifies itself as a bot.
Scanners posing as browsers1,95011%8 MB9Other requests from an address also caught probing for weak spots.
AI crawlers8474.8%6 MB12AI companies gathering pages or answering a user's question, and saying so.
Scripts and tools6593.7%5 MB2Programs such as curl or Python, or anything with an unrecognizable name.
Likely people6223.5%9 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
Unclear3151.8%2 MB0Browser name, but fetched only an image or data file and no page. Could be either.
SEO and marketing tools3001.7%<1 MB244Commercial tools that sell data about websites.
Possibly people320.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.
Calendar and feed apps10.0%<1 MB0Software fetching a feed for someone who subscribed.
No name given10.0%<1 MB0Requests that give no software name at all.

Named bots

Botas it names itselfTypeRequests
bingbotSearch engines1,945
PetalBotSearch engines711
QlyzeBotOther named bots606
ClaudeBotAI crawlers286
SemrushBotSEO and marketing tools228
OAI-SearchBotAI crawlers219
ElevenlabsCrawlerOther named bots197
ExaSearchBotOther named bots195
ChatGPT-UserAI crawlers183
DuckDuckBotSearch engines175
ApplebotSearch engines162
meta-webindexerOther named bots162
GooglebotSearch engines137
Amzn-SearchBotSearch engines135
SeznamBotSearch engines127

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/100
/playoffs/45
/wnba/27
/overseas/26
/watch/25
/standings/25
/scores/24
/draft/24
/tickets/24
/guide/5
/videos/5
/news/4

How people arrived

Referring siteHuman visitors
duckduckgo.com19
m.baidu.com17
www.google.com9
search.yahoo.com4
www.bing.com4
www.qwant.com1
www.baidu.com1
www.quora.com1
www.reddit.com1
www.facebook.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/16732
117.132.0.0/16691
87.81.0.0/166563
43.173.0.0/166057
43.157.0.0/165830
64.16.0.0/165511
45.138.0.0/16483
5.102.0.0/16442

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 2388476188330151,03097%
Oct 2455466250114785497%
Oct 253436128715867798%
Oct 2615155151483,236193,95199%
Oct 2767433244671377496%
Oct 281433633156742094092%
Oct 291333386205781673691%
Oct 30295645134874411,02985%
Oct 311736460351240171,13593%
Nov 11019473332695511,58495%
Nov 2937396142399491,03591%
Nov 3134231220488291,46795%
Nov 4782901311791964293%
Nov 5115648412516770289%
Nov 682651685435241,09595%

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.