Bot traffic: 1.deptmatic.com

all sites · all domains · last 15 days

All sites · All Domains · Visit 1.deptmatic.com

Who is really visiting 1.deptmatic.com?

Between Oct 23 and Nov 6, 1.deptmatic.com received 68,204 requests. About 99.2% came from automated software and about 0.7% look like real people.

That works out to about 148 human visitors, roughly 10 a day, who opened 264 pages between them. 78 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
148human visitors (estimate)
264pages opened by people
68,204total requests, 15 days

Where the requests came from

People 0.7%Named bots 14%Disguised bots 18%Scanners 67%Unclear 0.2%

Requests per day

PeopleNamed botsDisguised botsScannersUnclear
03,1256,2509,37512,500Oct 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Σ 68,204ShareData sentBlockedby the serverWhat this means
Break-in scanners28,47942%6 MB220Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers17,37025%24 MB277Other requests from an address also caught probing for weak spots.
Disguised scrapers8,28412%12 MB63Claims 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.
Search engines5,7538.4%4 MB4Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
Other named bots2,1583.2%2 MB47Any other software that identifies itself as a bot.
No name given1,8042.6%5 MB29Requests that give no software name at all.
AI crawlers1,6532.4%2 MB65AI companies gathering pages or answering a user's question, and saying so.
Scripts and tools1,4662.1%2 MB41Programs such as curl or Python, or anything with an unrecognizable name.
App link sweepers5390.8%<1 MB140Touches only login, app or embed links and no actual content.
Likely people4370.6%<1 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
Unclear1220.2%<1 MB0Browser name, but fetched only an image or data file and no page. Could be either.
SEO and marketing tools1190.2%<1 MB92Commercial tools that sell data about websites.
Automated browsers100.0%<1 MB0Loads images like a browser, but too fast for a person or with a faked browser name.
Possibly people100.0%<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.

Named bots

Botas it names itselfTypeRequests
GooglebotSearch engines3,365
PetalBotSearch engines1,369
bingbotSearch engines770
ClaudeBotAI crawlers337
InfrawatchOther named bots252
RiverBotOther named bots190
OAI-SearchBotAI crawlers179
CensysInspectOther named bots173
GPTBotAI crawlers157
AmazonbotAI crawlers149
KGBSEARCHOther named bots132
ApplebotSearch engines92
MJ12botSEO and marketing tools80
DeepSeekBotAI crawlers76
Meta-ExternalFetcherAI crawlers75

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/account/login141

How people arrived

Referring siteHuman visitors
google.com, http:8
www.google.com6
www.atlantea.org3
hub.ceotim.com2
hot.dev.wholetech.com2
www.shniudi.com1
www.lycee-smndc.fr1

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
103.102.0.0/168041
3.107.0.0/165781
43.157.0.0/1619835
43.130.0.0/1617734
34.91.0.0/161751
195.178.0.0/161571
47.82.0.0/1615073
43.166.0.0/1614028

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 2310127475903,659105,03299.3%
Oct 2461032039875081,49398%
Oct 255102471,33017361,77199%
Oct 2616268935538,9491510,45699.4%
Oct 277182886863,042114,05199.1%
Oct 2821274465872,05243,13798%
Oct 2910189371,2333,090125,30599.2%
Oct 30798686442,40273,93999.4%
Oct 31453761,0683,96885,43099.7%
Nov 1681,4476506,21488,33399.7%
Nov 218261,0187542,96344,78199.0%
Nov 317405734292,50843,57698%
Nov 410201,1131,0703,21265,43599.3%
Nov 59182549691,523142,78799%
Nov 613171561,1421,34452,67899%

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.