Bot traffic: 186echopoint.com

all sites · all domains · last 15 days

All sites · All Domains · Visit 186echopoint.com

Who is really visiting 186echopoint.com?

Between Oct 23 and Nov 6, 186echopoint.com received 13,025 requests. About 91% came from automated software and about 6.2% look like real people.

That works out to about 134 human visitors, roughly 9 a day, who opened 171 pages between them. 32 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 Nov 1, with 2,509 requests, of which 59 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.

91%of requests from bots
134human visitors (estimate)
171pages opened by people
13,025total requests, 15 days

Where the requests came from

People 6.2%Named bots 24%Disguised bots 26%Scanners 41%Unclear 2.9%

Requests per day

PeopleNamed botsDisguised botsScannersUnclear
07501,5002,2503,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.

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

The breakdown

SourceRequestsΣ 13,025ShareData sentBlockedby the serverWhat this means
Break-in scanners3,71028%<1 MB0Probing for WordPress logins, password files and other common weak spots.
Disguised scrapers2,49919%69 MB7Claims 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 browsers1,60212%2 MB3Other requests from an address also caught probing for weak spots.
AI crawlers1,2089.3%82 MB32AI companies gathering pages or answering a user's question, and saying so.
Other named bots1,1729.0%47 MB132Any other software that identifies itself as a bot.
Scripts and tools9487.3%10 MB15Programs such as curl or Python, or anything with an unrecognizable name.
Likely people7245.6%162 MB4Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
Search engines6154.7%19 MB108Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
Unclear3762.9%81 MB0Browser name, but fetched only an image or data file and no page. Could be either.
SEO and marketing tools880.7%<1 MB48Commercial tools that sell data about websites.
Possibly people810.6%<1 MB7Read 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 given20.0%<1 MB0Requests that give no software name at all.

Named bots

Botas it names itselfTypeRequests
ClaudeBotAI crawlers759
GPTBotAI crawlers368
PetalBotSearch engines337
RiverBotOther named bots236
facebook.comOther named bots112
bingbotSearch engines106
LohiSoftBotOther named bots105
leakix.netOther named bots96
GooglebotSearch engines93
OAI-SearchBotAI crawlers75
ElevenlabsCrawlerOther named bots62
HubSpot CrawlerOther named bots58
QlyzeBotOther named bots54
ibou-searchOther named bots47
SemrushBotSEO and marketing tools42

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/98
/gallery/6
/act/3
/flyers/4-shop-electric/3
/photos-mls/2
/comps/2
/1304mariposa206/2
/flyers/5-shop-electric-water/2
/flyers/6-shop-electric-water-fiber/2
/flyers/2-home-only/2

How people arrived

Referring siteHuman visitors
bnbhot.com37
www.google.com27
m.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/164322
192.42.0.0/1622856
5.102.0.0/161053
185.220.0.0/167323
43.157.0.0/163519
170.106.0.0/163422
104.164.0.0/16336
43.130.0.0/163022

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 233450116971128991%
Oct 2410129613992436989%
Oct 2546215248151055986%
Oct 2699503437139331,14894%
Oct 272222575275119791,13386%
Oct 282325289201499341,10190%
Oct 29671681751561660383%
Oct 30331141054364170893%
Oct 3111861013542456895%
Nov 1683181,198896382,50996%
Nov 278230971,058181,44896%
Nov 336122871,128191,36498%
Nov 415171331071022548171%
Nov 5121995115212945293%
Nov 61624894891529350%

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.