Bot traffic: campaignpromise.com

all sites · all domains · last 15 days

All sites · All Domains · Visit campaignpromise.com

Who is really visiting campaignpromise.com?

Between Oct 23 and Nov 6, campaignpromise.com received 66,339 requests. About 99% came from automated software and about 0.6% look like real people.

That works out to about 147 human visitors, roughly 10 a day, who opened 259 pages between them. 45 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
147human visitors (estimate)
259pages opened by people
66,339total requests, 15 days

Where the requests came from

People 0.6%Named bots 6.3%Disguised bots 6.1%Scanners 87%Unclear 0.4%

Requests per day

PeopleNamed botsDisguised botsScannersUnclear
02,5005,0007,50010,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.

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

The breakdown

SourceRequestsΣ 66,339ShareData sentBlockedby the serverWhat this means
Break-in scanners48,57073%74 MB28,513Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers8,94613%45 MB56Other requests from an address also caught probing for weak spots.
Disguised scrapers2,8254.3%24 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.
AI crawlers1,5152.3%3 MB101AI companies gathering pages or answering a user's question, and saying so.
Search engines1,3232.0%6 MB13Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
Scripts and tools1,1951.8%3 MB12Programs such as curl or Python, or anything with an unrecognizable name.
Other named bots1,1571.7%5 MB33Any other software that identifies itself as a bot.
Likely people3340.5%3 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
Unclear2400.4%<1 MB0Browser name, but fetched only an image or data file and no page. Could be either.
SEO and marketing tools1660.3%<1 MB62Commercial tools that sell data about websites.
Possibly people580.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 given100.0%<1 MB0Requests that give no software name at all.

Named bots

Botas it names itselfTypeRequests
PetalBotSearch engines404
GooglebotSearch engines346
ClaudeBotAI crawlers249
bingbotSearch engines226
OAI-SearchBotAI crawlers207
ChatGPT-UserAI crawlers120
GPTBotAI crawlers108
PerplexityBotAI crawlers93
BytespiderAI crawlers89
DuckAssistBotOther named bots79
DuckDuckBotSearch engines77
Meta-ExternalAgentAI crawlers74
claudebotAI crawlers70
MoonshotBotOther named bots68
DeepSeekBotAI crawlers67

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/127
/about/11
/resources/7
/news/6
/rss-api6
/videos/5
/history/5
/faq/4
/sources/4
/social/3
/act/2

How people arrived

Referring siteHuman visitors
www.bing.com31
duckduckgo.com26
m.baidu.com20
www.google.com14
search.brave.com6
search.yahoo.com5
www.ecosia.org2
www.wholetech.com1
noai.duckduckgo.com1
www.qwant.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/1620131
37.19.0.0/161681
185.220.0.0/1613123
102.129.0.0/161211
66.249.0.0/161153
45.152.0.0/16601
45.156.0.0/165639
103.196.0.0/16483

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 238121401315,80176,10799.4%
Oct 2418341252093,666114,05999%
Oct 25353171415,299115,77699.7%
Oct 2612163121984,298174,84999.2%
Oct 27462644652,78873,53299.6%
Oct 288142071473,897204,29199.1%
Oct 298141481852,718123,08399%
Oct 309211282405,679136,08699.4%
Oct 31671452033,38663,75199.5%
Nov 110196121,1153,468365,25999%
Nov 2459102347,20988,37099.8%
Nov 31922872073,462203,81698%
Nov 420364052402,128212,85097%
Nov 511291481671,652352,04096%
Nov 613192131482,065162,47098%

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.