Web Security
User Agent Parser
Web logs are full of User-Agent strings, and half of SOC triage is deciding whether one is a real visitor, a search crawler or a scanner pretending to be a browser.
Parsing uses local pattern matching only. Your own User-Agent is read from navigator.userAgent in your browser and never transmitted.
Treat User-Agent as a claim, not evidence
- Anyone can send any User-Agent, so never use it as an access-control decision.
- Legitimate crawlers can be verified with forward-confirmed reverse DNS on the source IP.
- Empty, very short or default library strings (curl, python-requests) in web logs usually mean scripting.
- Very old browser versions appearing suddenly can indicate a headless tool with a stale hardcoded string.
Related tools
Security Log Analyzer
Paste sample logs and extract IPs, timestamps, users, URLs and severity indicators.
HTTP Security Headers Checker
Check a site for CSP, HSTS, X-Frame-Options and other security headers, with honest CORS limits.
Phishing URL Inspector
Break a suspicious URL into its parts and flag common phishing and obfuscation traits.