Bot traffic: proaudiobroker.com

all sites · all domains · last 15 days

All sites · All Domains · Visit proaudiobroker.com

Who is really visiting proaudiobroker.com?

Between Oct 23 and Nov 6, proaudiobroker.com received 21,339 requests. About 97% came from automated software and about 2.4% look like real people.

That works out to about 84 human visitors, roughly 6 a day, who opened 132 pages between them. 47 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 6,555 requests, of which 41 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.

97%of requests from bots
84human visitors (estimate)
132pages opened by people
21,339total requests, 15 days

Where the requests came from

People 2.4%Named bots 32%Disguised bots 16%Scanners 49%Unclear 0.7%

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.

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

The breakdown

SourceRequestsΣ 21,339ShareData sentBlockedby the serverWhat this means
Break-in scanners8,23639%3 MB1,439Probing for WordPress logins, password files and other common weak spots.
Search engines3,40916%23 MB336Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
Scanners posing as browsers2,18410%5 MB52Other requests from an address also caught probing for weak spots.
Other named bots1,9639.2%11 MB262Any other software that identifies itself as a bot.
Disguised scrapers1,8348.6%18 MB197Claims 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,6697.8%2 MB12Programs such as curl or Python, or anything with an unrecognizable name.
AI crawlers1,1525.4%6 MB19AI companies gathering pages or answering a user's question, and saying so.
Likely people4592.2%18 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
SEO and marketing tools2461.2%<1 MB209Commercial tools that sell data about websites.
Unclear1390.7%<1 MB0Browser name, but fetched only an image or data file and no page. Could be either.
Possibly people430.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.
App link sweepers40.0%<1 MB0Touches only login, app or embed links and no actual content.
No name given10.0%<1 MB0Requests that give no software name at all.

Named bots

Botas it names itselfTypeRequests
PetalBotSearch engines1,727
ElevenlabsCrawlerOther named bots858
ClaudeBotAI crawlers727
bingbotSearch engines709
QlyzeBotOther named bots579
Amzn-SearchBotSearch engines552
SERankingBacklinksBotSEO and marketing tools199
GooglebotSearch engines146
OAI-SearchBotAI crawlers102
ChatGPT-UserAI crawlers96
SeznamBotSearch engines75
ApplebotSearch engines56
Baiduspider-renderSearch engines51
leakix.netOther named bots48
BaiduspiderSearch engines40

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/57
/liquidation/6
/contact.html3

How people arrived

Referring siteHuman visitors
www.google.com37
m.baidu.com19
learn.microsoft.com1
www.bing.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
141.94.0.0/1615212
192.42.0.0/1612627
123.6.0.0/16453
57.129.0.0/16408
185.220.0.0/16349
213.32.0.0/16335
5.102.0.0/16312
43.157.0.0/162914

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 2323376511401121,30499%
Oct 24172453210861061,38490%
Oct 25223929951181,01399%
Oct 26791,1838074,510146,55599.2%
Oct 2735916846917122,69699.4%
Oct 2810176219462683593%
Oct 294757117117877997%
Oct 3010133751154141999591%
Oct 312424493408675599%
Nov 13527911380691,21299%
Nov 211275158386783199%
Nov 31219239132860101,29495%
Nov 4233268374849498%
Nov 5713293108432687695%
Nov 6671487012831673%

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.