Bot traffic: offgridder.com

all sites · all domains · last 15 days

All sites · All Domains · Visit offgridder.com

Who is really visiting offgridder.com?

Between Oct 23 and Nov 6, offgridder.com received 45,268 requests. About 98% came from automated software and about 0.9% look like real people.

That works out to about 187 human visitors, roughly 12 a day, who opened 283 pages between them. 50 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.

98%of requests from bots
187human visitors (estimate)
283pages opened by people
45,268total requests, 15 days

Where the requests came from

People 0.9%Named bots 13%Disguised bots 13%Scanners 73%Unclear 0.8%

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.

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

The breakdown

SourceRequestsΣ 45,268ShareData sentBlockedby the serverWhat this means
Break-in scanners27,62561%2 MB17,293Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers5,41412%11 MB28Other requests from an address also caught probing for weak spots.
Disguised scrapers3,7458.3%37 MB1Claims 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 engines1,9844.4%8 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,9684.3%14 MB3Programs such as curl or Python, or anything with an unrecognizable name.
Other named bots1,7593.9%8 MB32Any other software that identifies itself as a bot.
AI crawlers1,6573.7%2 MB105AI companies gathering pages or answering a user's question, and saying so.
SEO and marketing tools3600.8%2 MB87Commercial tools that sell data about websites.
Unclear3580.8%<1 MB0Browser name, but fetched only an image or data file and no page. Could be either.
Likely people2600.6%2 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
Possibly people1310.3%<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 given70.0%<1 MB0Requests that give no software name at all.

Named bots

Botas it names itselfTypeRequests
PetalBotSearch engines933
GooglebotSearch engines380
ClaudeBotAI crawlers362
bingbotSearch engines174
QlyzeBotOther named bots173
OAI-SearchBotAI crawlers168
GPTBotAI crawlers167
ElevenlabsCrawlerOther named bots131
SeekportBotSEO and marketing tools119
SERankingBacklinksBotSEO and marketing tools116
Amzn-SearchBotSearch engines98
meta-webindexerOther named bots93
claudebotAI crawlers91
BaiduspiderSearch engines85
SemrushBotSEO and marketing tools84

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/100
/about/13
/resources/11
/social/9
/sitemap/8
/faq/7
/videos.html6
/how-to-go-off-grid/5
/news/2026-05-14-three-tiny-home-designs-off-grid-inspiration.html5
/research/4
/news/3
/about.html2

How people arrived

Referring siteHuman visitors
www.google.com56
m.baidu.com21
aquachifit.com17
austintweet.com10
duckduckgo.com3
www.baidu.com2

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/1618445
66.249.0.0/161683
158.69.0.0/161451
104.164.0.0/161209
47.82.0.0/168885
183.207.0.0/16758
5.102.0.0/16713
62.93.0.0/16711

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 23462152993,414363,97399%
Oct 249182364712,018152,76399%
Oct 25365193453,686174,57899.4%
Oct 2613182033101,024161,58297%
Oct 2720292695651,772252,66698%
Oct 2818245772233,152254,00899%
Oct 2914164432521,753152,48798%
Oct 301418193302722421,28894%
Oct 31714199294875231,40997%
Nov 111164431,4462,469294,41399%
Nov 24114963072,036232,87899%
Nov 38114762225,753196,48799.4%
Nov 438525473371,467462,46595%
Nov 521366152331,889152,79798%
Nov 6683291141,009121,47499%

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.