Bot traffic: tribalsurvival.com

all sites · all domains · last 15 days

All sites · All Domains · Visit tribalsurvival.com

Who is really visiting tribalsurvival.com?

Between Oct 23 and Nov 6, tribalsurvival.com received 42,946 requests. About 99% came from automated software and about 0.8% look like real people.

That works out to about 98 human visitors, roughly 7 a day, who opened 223 pages between them. 55 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.

99%of requests from bots
98human visitors (estimate)
223pages opened by people
42,946total requests, 15 days

Where the requests came from

People 0.8%Named bots 9.4%Disguised bots 7.7%Scanners 82%Unclear 0.3%

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.

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

The breakdown

SourceRequestsΣ 42,946ShareData sentBlockedby the serverWhat this means
Break-in scanners29,48569%27 MB16,614Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers5,61413%21 MB30Other requests from an address also caught probing for weak spots.
Disguised scrapers2,2275.2%13 MB5Claims 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.
AI crawlers1,4263.3%2 MB85AI companies gathering pages or answering a user's question, and saying so.
Search engines1,3533.2%4 MB12Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
Scripts and tools1,0802.5%2 MB10Programs such as curl or Python, or anything with an unrecognizable name.
Other named bots1,0212.4%3 MB27Any other software that identifies itself as a bot.
Likely people3000.7%1 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
SEO and marketing tools2320.5%<1 MB58Commercial tools that sell data about websites.
Unclear1500.3%<1 MB0Browser name, but fetched only an image or data file and no page. Could be either.
Possibly people370.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.
Automated browsers140.0%<1 MB0Loads images like a browser, but too fast for a person or with a faked browser name.
No name given50.0%<1 MB0Requests that give no software name at all.
Calendar and feed apps10.0%<1 MB0Software fetching a feed for someone who subscribed.
App link sweepers10.0%<1 MB0Touches only login, app or embed links and no actual content.

Named bots

Botas it names itselfTypeRequests
PetalBotSearch engines594
ClaudeBotAI crawlers416
GooglebotSearch engines315
OAI-SearchBotAI crawlers181
bingbotSearch engines127
GPTBotAI crawlers87
ApplebotSearch engines85
BytespiderAI crawlers79
KimiBotOther named bots71
YouBotAI crawlers67
OAI-AdsBotSearch engines67
ElevenlabsCrawlerOther named bots65
CCBotAI crawlers62
SeznamBotSearch engines60
QwenbotOther named bots59

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/39
/rss-api9
/kit-guide/8
/about/8
/news/8
/sources/6
/faq/6
/resources/6
/videos/5
/social/2
/about.html2

How people arrived

Referring siteHuman visitors
m.baidu.com18
www.google.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
43.166.0.0/1611256
192.42.0.0/1611031
158.69.0.0/161102
66.249.0.0/16975
45.138.0.0/16803
45.156.0.0/166748
43.130.0.0/165230
102.129.0.0/16521

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 23121421342,88973,17499.7%
Oct 247211291572,104132,42599%
Oct 25113881303,93394,46299.8%
Oct 268161401145,01695,30199.4%
Oct 275162132901,112111,64598%
Oct 28442841331,66042,08899.5%
Oct 29241251931,18651,51399.4%
Oct 30715132167702131,03896%
Oct 31122531311,10181,49599.3%
Nov 124373271,0852,700124,18398%
Nov 217394591772,75563,47098%
Nov 37123981891,658152,27799%
Nov 413207031375,658156,54599.3%
Nov 58242481591,64862,09698%
Nov 681092131977171,23497%

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.