Bot traffic: cargotown.com

all sites · all domains · last 15 days

All sites · All Domains · Visit cargotown.com

Who is really visiting cargotown.com?

Between Oct 23 and Nov 6, cargotown.com received 69,936 requests. About 99.1% came from automated software and about 0.4% look like real people.

That works out to about 96 human visitors, roughly 6 a day, who opened 192 pages between them. 52 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 28,431 requests, of which 18 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.

99.1%of requests from bots
96human visitors (estimate)
192pages opened by people
69,936total requests, 15 days

Where the requests came from

People 0.4%Named bots 7.9%Disguised bots 4.1%Scanners 87%Unclear 0.5%

Requests per day

PeopleNamed botsDisguised botsScannersUnclear
07,50015,00022,50030,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.

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

The breakdown

SourceRequestsΣ 69,936ShareData sentBlockedby the serverWhat this means
Break-in scanners35,04150%44 MB16,568Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers25,84937%69 MB225Other requests from an address also caught probing for weak spots.
Disguised scrapers2,3163.3%18 MB3Claims 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.
Search engines2,1983.1%11 MB11Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
AI crawlers1,7232.5%3 MB116AI companies gathering pages or answering a user's question, and saying so.
Other named bots1,4352.1%6 MB16Any other software that identifies itself as a bot.
Scripts and tools5490.8%3 MB2Programs such as curl or Python, or anything with an unrecognizable name.
Unclear3790.5%<1 MB0Browser name, but fetched only an image or data file and no page. Could be either.
Likely people2220.3%1 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
SEO and marketing tools1700.2%<1 MB66Commercial tools that sell data about websites.
Possibly people490.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 given50.0%<1 MB0Requests that give no software name at all.

Named bots

Botas it names itselfTypeRequests
sogou.comSearch engines702
PetalBotSearch engines513
GooglebotSearch engines437
ClaudeBotAI crawlers406
bingbotSearch engines225
OAI-SearchBotAI crawlers205
BytespiderAI crawlers113
QlyzeBotOther named bots110
GPTBotAI crawlers108
ChatGPT-UserAI crawlers96
ApplebotSearch engines90
KimiBotOther named bots85
PerplexityBotAI crawlers81
crawlerOther named bots78
DuckAssistBotOther named bots77

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/48
/videos/9
/container-basics/9
/rss-api6
/designs/5
/costs/5
/faq/4
/news/4
/about/4
/resources/3
/building-codes/3
/social/3

How people arrived

Referring siteHuman visitors
m.baidu.com18
www.google.com6
scriblihelp.com1
www.bing.com1
www.google.com.hk1
duckduckgo.com1
www.yahoo.com1
www.facebook.com1
search.brave.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
192.42.0.0/1616331
66.249.0.0/161173
93.123.0.0/161161
158.69.0.0/16651
43.157.0.0/163923
43.130.0.0/163218
43.166.0.0/162717
49.51.0.0/162516

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 23354152272,918283,59599.0%
Oct 248221981932,099122,52799%
Oct 25003581334,456104,95799.8%
Oct 26111429021427,8941528,43199.9%
Oct 27511230342953271,56498%
Oct 28342931521,493361,98098%
Oct 29717219186967401,43596%
Oct 301321441171904311,58096%
Oct 318104002062,074382,73498%
Nov 110144872474,483345,27399%
Nov 29259172185,767146,94999.3%
Nov 311161891802,138192,55398%
Nov 410177081231,664392,56197%
Nov 56102331831,763212,21398%
Nov 646148951,317151,58498%

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:43 UTC from 15 log files.