Bot traffic: repeater.org

all sites · all domains · last 15 days

All sites · All Domains · Visit repeater.org

Who is really visiting repeater.org?

Between Oct 23 and Nov 6, repeater.org received 50,538 requests. About 99% came from automated software and about 0.5% look like real people.

That works out to about 99 human visitors, roughly 7 a day, who opened 219 pages between them. 42 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
99human visitors (estimate)
219pages opened by people
50,538total requests, 15 days

Where the requests came from

People 0.5%Named bots 8.3%Disguised bots 8.6%Scanners 82%Unclear 0.9%

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.

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

The breakdown

SourceRequestsΣ 50,538ShareData sentBlockedby the serverWhat this means
Break-in scanners35,31070%32 MB20,085Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers6,02612%26 MB6Other requests from an address also caught probing for weak spots.
Disguised scrapers3,4986.9%22 MB4Claims 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,3742.7%2 MB95AI companies gathering pages or answering a user's question, and saying so.
Search engines1,3712.7%5 MB15Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
Other named bots1,1582.3%4 MB28Any other software that identifies itself as a bot.
Scripts and tools8331.6%7 MB3Programs such as curl or Python, or anything with an unrecognizable name.
Unclear4440.9%<1 MB0Browser name, but fetched only an image or data file and no page. Could be either.
SEO and marketing tools2700.5%<1 MB99Commercial tools that sell data about websites.
Likely people1440.3%1 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
Possibly people1060.2%<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 given40.0%<1 MB0Requests that give no software name at all.

Named bots

Botas it names itselfTypeRequests
ClaudeBotAI crawlers446
GooglebotSearch engines445
PetalBotSearch engines275
bingbotSearch engines228
OAI-SearchBotAI crawlers178
sogou.comSearch engines113
SemrushBotSEO and marketing tools96
PerplexityBotAI crawlers94
GPTBotAI crawlers92
BytespiderAI crawlers90
Amzn-SearchBotSearch engines88
RiverBotOther named bots84
SERankingBacklinksBotSEO and marketing tools81
ibou-searchOther named bots76
ElevenlabsCrawlerOther named bots72

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/52
/resources.html12
/frequencies/7
/social.html7
/news.html6
/expanse/6
/faq/5
/history/4
/resources/4
/sources/4
/videos/4
/social/4

How people arrived

Referring siteHuman visitors
www.google.com50
m.baidu.com21
duckduckgo.com4
noai.duckduckgo.com2
www.facebook.com1
www.bing.com1
www.google.com.ua1

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/161351
192.42.0.0/1613333
66.249.0.0/161193
117.132.0.0/16661
102.129.0.0/16541
45.156.0.0/164638
207.241.0.0/16402
43.166.0.0/163922

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 239231873583,948294,54899%
Oct 246102092531,761242,25798%
Oct 25591782854,955335,46599.1%
Oct 2610272273565,770476,43299%
Oct 2719211803171,165141,69798%
Oct 28991963142,707173,24499.2%
Oct 29827220288556261,12195%
Oct 308103152871,708282,35298%
Oct 316112102231,695232,16798%
Nov 18315123342,198243,10098%
Nov 2332223382,200232,78899%
Nov 3465362596,136516,98899.2%
Nov 47224422982,040252,82898%
Nov 5234252342,772393,47399%
Nov 6571141911,725412,07898%

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.