Overview
Netlab360 is a security scanner from Qihoo 360 Netlab used for security scanning, malware checks, vulnerability assessment, certificate review, and site-safety analysis.
Its primary user-agent pattern is Netlab360.
Netlab360 is Unverified at the identity-evidence level. The listed identity remains useful for detection, but this record does not currently contain authoritative evidence sufficient to authenticate the identity claim.
Robots.txt behavior is not currently confirmed.
Netlab360 should be monitored first, then rate-limited or blocked if the crawl rate, paths, or behavior are unwanted.
Identity
- User-Agent Pattern
-
Netlab360 - HTTP Agent Examples
-
Netlab360 - Robots Token
- Netlab360
- Identity Type
- Observed
- Evidence Method
- Treat `Netlab360` as an identity signal only. Confirm it with current operator documentation, cryptographic verification, forward-confirmed reverse DNS, source-network ownership, or other authoritative evidence before trusting the claimed identity.
Classification
- Type
- Security scanner
- Kind
- Security scanner
- Family
- Qihoo 360 Netlab
- Purpose
- Security scanning
Behavior and handling
- Common Use
- Netlab360 is used for security scanning, malware checks, vulnerability assessment, certificate review, and site-safety analysis.
- Detection Notes
- Netlab360 traffic is primarily detected by the `Netlab360` user-agent pattern. Compare source IPs, reverse DNS, request paths, and crawl cadence with Qihoo 360 Netlab infrastructure before trusting the traffic.
- Respects robots.txt
- Unknown
- Spoofing Risk
- Netlab360 has medium spoofing risk because user-agent strings can be copied; pair the match with DNS, IP, behavior, or operator evidence.
- Risk
- Caution
- Recommended Handling
- Monitor
Rules and controls
- Robots.txt Snippet
-
# robots.txt behavior is unconfirmed. Do not rely on this rule without verification.
Relationships
- Operator
- Qihoo 360 Netlab Checked 2026-08-07
Relationships without an Evidence link are normalized from the canonical directory record. They should not be interpreted as independent proof of physical presence or request origin.