Bot traffic: tvreviewer.com

all sites · all domains · last 15 days

All sites · All Domains · Visit tvreviewer.com

Who is really visiting tvreviewer.com?

Between Oct 23 and Nov 6, tvreviewer.com received 80,631 requests. About 98% came from automated software and about 0.6% look like real people.

That works out to about 246 human visitors, roughly 16 a day, who opened 294 pages between them. 48 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
246human visitors (estimate)
294pages opened by people
80,631total requests, 15 days

Where the requests came from

People 0.6%Named bots 39%Disguised bots 16%Scanners 44%Unclear 1.2%

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.

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

The breakdown

SourceRequestsΣ 80,631ShareData sentBlockedby the serverWhat this means
Break-in scanners26,25133%44 MB14,737Probing for WordPress logins, password files and other common weak spots.
Disguised scrapers9,95312%61 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.
Other named bots9,89612%109 MB40Any other software that identifies itself as a bot.
Search engines9,45612%44 MB7Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
Scanners posing as browsers9,12511%46 MB28Other requests from an address also caught probing for weak spots.
SEO and marketing tools7,2759.0%42 MB386Commercial tools that sell data about websites.
AI crawlers4,4335.5%25 MB144AI companies gathering pages or answering a user's question, and saying so.
Scripts and tools2,7683.4%39 MB1Programs such as curl or Python, or anything with an unrecognizable name.
Unclear9511.2%54 MB0Browser name, but fetched only an image or data file and no page. Could be either.
Likely people3540.4%6 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
Possibly people1660.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.
App link sweepers30.0%<1 MB0Touches only login, app or embed links and no actual content.

Named bots

Botas it names itselfTypeRequests
QlyzeBotOther named bots4,042
serpstatbotSEO and marketing tools3,693
PetalBotSearch engines3,069
Amzn-SearchBotSearch engines2,121
BaiduspiderSearch engines1,700
ClaudeBotAI crawlers1,374
ElevenlabsCrawlerOther named bots1,086
BarkrowlerSEO and marketing tools1,045
fresh-domain-watchOther named bots1,000
DataForSeoBotSEO and marketing tools906
bingbotSearch engines840
SERankingBacklinksBotSEO and marketing tools794
RiverBotOther named bots725
YouBotAI crawlers631
PerplexityBotAI crawlers561

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/71
/live/39
/showrunner/8
/films/one-battle-after-another.html7
/fnl/3
/stars/3
/streaming/3
/friday-night-lights/crew/kerry-ehrin.html3
/reviews/the-white-lotus/2
/friday-night-lights/cast/scott-porter.html2
/friday-night-lights/cast/adrianne-palicki.html2
/watch/2

How people arrived

Referring siteHuman visitors
www.google.com59
tvnight.com29
m.baidu.com22
austintweet.com9
m.facebook.com2
www.perplexity.ai1
www.bing.com1
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
47.79.0.0/16658136
43.173.0.0/16645479
43.172.0.0/16357262
47.82.0.0/16290152
66.249.0.0/162363
35.193.0.0/162311
192.42.0.0/1615638
141.94.0.0/169213

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 2314172,3381,0862,789616,29799%
Oct 2430401,4918881,722784,23697%
Oct 2514163,7017313,790918,33999%
Oct 2620269749634,671836,72798%
Oct 2727301,380922947743,37896%
Oct 2816161,139758836742,84496%
Oct 2919221,407967673773,16396%
Oct 3011121,204875989753,15897%
Oct 3114172,2321,1081,572594,99498%
Nov 120222,6551,0572,025525,84898%
Nov 29112,1057252,832445,72399%
Nov 312152,2987131,700484,78698%
Nov 413169949245,189527,20799%
Nov 5892,1025641,951494,68099%
Nov 624255,0404433,690349,25199.2%

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.