Bot traffic: afterstages.com

all sites · all domains · last 15 days

All sites · All Domains · Visit afterstages.com

Who is really visiting afterstages.com?

Between Oct 23 and Nov 6, afterstages.com received 39,025 requests. About 99.2% came from automated software and about 0.5% look like real people.

That works out to about 140 human visitors, roughly 9 a day, who opened 166 pages between them. 24 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.2%of requests from bots
140human visitors (estimate)
166pages opened by people
39,025total requests, 15 days

Where the requests came from

People 0.5%Named bots 6.0%Disguised bots 8.1%Scanners 85%Unclear 0.3%

Requests per day

PeopleNamed botsDisguised botsScannersUnclear
01,5003,0004,5006,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Σ 39,025ShareData sentBlockedby the serverWhat this means
Break-in scanners25,35765%36 MB11,564Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers7,90120%41 MB127Other requests from an address also caught probing for weak spots.
Disguised scrapers2,0225.2%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,1222.9%2 MB9Programs such as curl or Python, or anything with an unrecognizable name.
Other named bots8552.2%5 MB9Any other software that identifies itself as a bot.
Search engines8192.1%5 MB1Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
AI crawlers5311.4%<1 MB20AI companies gathering pages or answering a user's question, and saying so.
Possibly people1500.4%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.
SEO and marketing tools1190.3%<1 MB67Commercial tools that sell data about websites.
Unclear1100.3%<1 MB0Browser name, but fetched only an image or data file and no page. Could be either.
Likely people340.1%<1 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
No name given40.0%<1 MB0Requests that give no software name at all.
App link sweepers10.0%<1 MB0Touches only login, app or embed links and no actual content.

Named bots

Botas it names itselfTypeRequests
GooglebotSearch engines331
PetalBotSearch engines255
ClaudeBotAI crawlers173
RiverBotOther named bots132
OAI-SearchBotAI crawlers118
bingbotSearch engines108
pathscanOther named bots92
GPTBotAI crawlers59
meta-webindexerOther named bots52
SemrushBotSEO and marketing tools50
leakix.netOther named bots48
Amzn-SearchBotSearch engines47
facebook.comOther named bots42
ElevenlabsCrawlerOther named bots32
ExaSearchBotOther named bots28

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/124
/videos/2

How people arrived

Referring siteHuman visitors
videoretreat.com99
m.baidu.com18
www.google.com6
schemikalelike.blogspot.com4
www.baidu.com2
www.google.com.hk1

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/1618341
45.138.0.0/161314
66.249.0.0/16683
102.129.0.0/16661
185.220.0.0/164113
170.106.0.0/162918
104.164.0.0/16284
103.4.0.0/16273

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 2312110126665991299%
Oct 2424251462622,79963,23999.0%
Oct 2599158983,18363,45499.6%
Oct 2612152412523,77964,29399.5%
Oct 2714161171994,71195,05299.5%
Oct 2820201741291,59051,91899%
Oct 29222459202362565395%
Oct 30563221334,45064,91899.7%
Oct 311419102108555279796%
Nov 19122381,0042,47173,73499.4%
Nov 2111561672,96283,29499.7%
Nov 3572201312,719113,08999.4%
Nov 445128100928101,17199%
Nov 5238216079991,05499%
Nov 61271781,285111,44799.1%

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.