360Spider

Operator

Online Media Group, Inc.

Type

Search bot

Official page

so.com

In Vireo

Excluded, reported under Search engines

User agent

Requests from 360Spider carry user agents like these:

Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0); 360Spider

Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1180.89 Safari/537.1; 360Spider

Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; MDDR; .NET4.0C; .NET4.0E; .NET CLR 1.1.4322; Tablet PC 2.0); 360Spider

Device Detector identifies it with this pattern (a case-insensitive regular expression):

(360Spider(?:-Image|-Video)?)

Anyone can put any name in a user agent. Where the operator publishes IP ranges, checking the request's address against them is the way to confirm a visit is genuine.

How Vireo counts 360Spider

Vireo keeps requests from 360Spider out of your pageviews and visitors and counts them on its bot report under Search engines, so you can see how much it left out rather than wonder why your server logs show more traffic.

Checked by running Vireo Analytics' own bot filter over 360Spider's user agents.

Sources

• 360Spider information page (so.com)
• Matomo Device Detector, bots.yml (LGPL-3.0)