Bot traffic: cambridgetower.net

all sites · all domains · last 15 days

All sites · All Domains · Visit cambridgetower.net

Who is really visiting cambridgetower.net?

Between Oct 23 and Nov 6, cambridgetower.net received 56,074 requests. About 99.5% came from automated software and about 0.1% look like real people.

That works out to about 42 human visitors, roughly 3 a day, who opened 70 pages between them. 23 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.5%of requests from bots
42human visitors (estimate)
70pages opened by people
56,074total requests, 15 days

Where the requests came from

People 0.1%Named bots 4.7%Disguised bots 6.3%Scanners 88%Unclear 0.4%

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.

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

The breakdown

SourceRequestsΣ 56,074ShareData sentBlockedby the serverWhat this means
Break-in scanners42,62976%70 MB26,205Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers6,97812%36 MB82Other requests from an address also caught probing for weak spots.
Disguised scrapers2,3914.3%18 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.
Scripts and tools1,1332.0%3 MB9Programs such as curl or Python, or anything with an unrecognizable name.
Search engines1,0361.8%4 MB3Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
AI crawlers7681.4%1 MB39AI companies gathering pages or answering a user's question, and saying so.
Other named bots7061.3%4 MB12Any other software that identifies itself as a bot.
Unclear2260.4%<1 MB0Browser name, but fetched only an image or data file and no page. Could be either.
SEO and marketing tools1230.2%<1 MB56Commercial tools that sell data about websites.
Possibly people530.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.
Likely people260.0%<1 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
No name given50.0%<1 MB0Requests that give no software name at all.

Named bots

Botas it names itselfTypeRequests
PetalBotSearch engines383
ClaudeBotAI crawlers347
GooglebotSearch engines271
bingbotSearch engines133
OAI-SearchBotAI crawlers132
ApplebotSearch engines91
GPTBotAI crawlers60
SemrushBotSEO and marketing tools48
leakix.netOther named bots48
Amzn-SearchBotSearch engines46
SeznamBotSearch engines40
ibou-searchOther named bots37
SERankingBacklinksBotSEO and marketing tools34
BarkrowlerSEO and marketing tools33
sunrisetranscription.comOther named bots32

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/26
/rss-api2

How people arrived

Referring siteHuman visitors
m.baidu.com21
mylibertyusaes.blogspot.com9
www.google.com4

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
152.53.0.0/161433
192.42.0.0/1612922
66.249.0.0/16752
102.129.0.0/16691
158.69.0.0/16562
185.220.0.0/164210
152.163.0.0/16352
170.106.0.0/163219

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 23231242465,151235,54799.5%
Oct 24241211804,411174,73499.5%
Oct 2510121481214,25794,54999.5%
Oct 2624922441,69492,04399.4%
Oct 27471552092,34372,72299.4%
Oct 28221411314,268294,57199.3%
Oct 29241152172,484172,83799.3%
Oct 30242831744,41774,88699.8%
Oct 31241281752,707133,02799.4%
Nov 1363291,0203,075284,45999.2%
Nov 2342772075,728136,23099.7%
Nov 3461311513,376123,67799.5%
Nov 4232121451,33981,70799.4%
Nov 5342541932,741233,21699.1%
Nov 6231231161,616111,86999.3%

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.