Bot traffic: girlhoop.com

all sites · all domains · last 15 days

All sites · All Domains · Visit girlhoop.com

Who is really visiting girlhoop.com?

Between Oct 23 and Nov 6, girlhoop.com received 32,011 requests. About 97% came from automated software and about 2.1% look like real people.

That works out to about 219 human visitors, roughly 15 a day, who opened 275 pages between them. 54 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.

97%of requests from bots
219human visitors (estimate)
275pages opened by people
32,011total requests, 15 days

Where the requests came from

People 2.1%Named bots 22%Disguised bots 27%Scanners 48%Unclear 1.0%

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.

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

The breakdown

SourceRequestsΣ 32,011ShareData sentBlockedby the serverWhat this means
Break-in scanners11,15635%2 MB25Probing for WordPress logins, password files and other common weak spots.
Disguised scrapers5,77718%30 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.
Scanners posing as browsers4,25313%9 MB17Other requests from an address also caught probing for weak spots.
Scripts and tools2,8558.9%3 MB2Programs such as curl or Python, or anything with an unrecognizable name.
Other named bots2,3337.3%11 MB10Any other software that identifies itself as a bot.
Search engines2,2927.2%11 MB1Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
AI crawlers1,7645.5%11 MB12AI companies gathering pages or answering a user's question, and saying so.
Likely people6171.9%3 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
SEO and marketing tools5761.8%1 MB214Commercial tools that sell data about websites.
Unclear3281.0%<1 MB0Browser name, but fetched only an image or data file and no page. Could be either.
Possibly people520.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.
No name given80.0%<1 MB0Requests that give no software name at all.

Named bots

Botas it names itselfTypeRequests
PetalBotSearch engines1,016
QlyzeBotOther named bots814
OAI-SearchBotAI crawlers789
ClaudeBotAI crawlers388
SERankingBacklinksBotSEO and marketing tools254
bingbotSearch engines252
GooglebotSearch engines213
ChatGPT-UserAI crawlers209
SemrushBotSEO and marketing tools188
DuckDuckBotSearch engines186
Amzn-SearchBotSearch engines169
meta-webindexerOther named bots165
ApplebotSearch engines153
PerplexityBotAI crawlers137
ibou-searchOther named bots131

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/64
/dunkers/62
/global/12
/teams/8
/college/6
/college/2026-27-preview/5
/college/texas/houston-christian/4
/questions/3
/ncaaw/3
/pipeline/3
/olympics/3
/college/texas/abilene-christian/3

How people arrived

Referring siteHuman visitors
duckduckgo.com20
www.bing.com19
www.google.com18
m.baidu.com16
search.yahoo.com7
com.reddit.frontpage1
www.yahoo.com1
ca.search.yahoo.com1
www.reddit.com1
www.baidu.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/164973
192.42.0.0/1618434
87.81.0.0/16141132
5.102.0.0/161033
64.16.0.0/168115
93.123.0.0/16812
43.157.0.0/167826
43.130.0.0/166933

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 23810293353482161,16996%
Oct 24913246168544171,00296%
Oct 2517214464523,718184,68798%
Oct 2615176054213,431174,51999%
Oct 271825557423938171,99196%
Oct 2817208532,8571,201234,98099%
Oct 291926341381696241,51594%
Oct 301313441510349261,36096%
Oct 311319298273697361,35494%
Nov 11518404724739181,92797%
Nov 21824789390287191,54195%
Nov 31820394398585161,43796%
Nov 41517522484439241,50096%
Nov 51416542426435251,47895%
Nov 61316234380868321,55196%

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.