The Universal Device Detection library for .NET that parses User Agents and detects devices (desktop, tablet, mobile, tv, cars, console, etc.), clients (browsers, feed readers, media players, PIMs, ...), operating systems, brands and models. This is a port of the popular PHP device-detector library to C#. For the most part you can just follow the documentation for device-detector with no issue.
Device Detection and User-Agent parser for .NET and C#. Detects the device, browser, operating system, and crawlers from the User-Agent and User-Agent Client Hints, using the 51Degrees cloud service with a Resource Key. This package is the cloud engine for the 51Degrees Pipeline API. An alternative to UAParser.js, DeviceAtlas, and WURFL.
Device Detection and User-Agent parser for .NET and C#. Detects the device, browser, operating system, and crawlers from the User-Agent and User-Agent Client Hints. This package contains shared classes used by the cloud and on-premise engines for the 51Degrees Pipeline API. An alternative to UAParser.js, DeviceAtlas, and WURFL.
The Universal Device Detection library for .NET that parses User Agents and detects devices (desktop, tablet, mobile, tv, cars, console, etc.), clients (browsers, feed readers, media players, PIMs, ...), operating systems, brands and models. This is a port of the popular PHP device-detector library to C#. For the most part you can just follow the documentation for device-detector with no issue.
Device Detection and User-Agent parser for .NET and C#. Detects the device, browser, operating system, and crawlers from the User-Agent and User-Agent Client Hints, reading a data file on your server. This package is the on-premise Hash engine for the 51Degrees Pipeline API. CMake is used to build the native binaries. An alternative to UAParser.js, DeviceAtlas, and WURFL.
Device Detection and User-Agent parser for .NET and C#. Detects the device, browser, operating system, and crawlers from the User-Agent and User-Agent Client Hints, on-premise with a data file or in the cloud. This package holds the builders that set up an on-premise or cloud pipeline with the 51Degrees Pipeline API. An alternative to UAParser.js, DeviceAtlas, and WURFL.
A library to parse user-agent strings in C#.
A service to parse user-agent strings in C#.
This is a .NET standard library that tries to parse and analyze the user agent string and extract as many relevant attributes as possible. The library aims to provides a reliable and extensible user agent parsing, browser and device detection. This is a semantic analyzer, so it doesn't rely on any database (except for some very little lookup tables), that means it is able to parse and recognize every day new kind of user agents and new patterns without updates. That makes the library very fast, flexible and easy to mantain, on the contrary the library can't extract info that are not present on user agent string without a proper mapping. The library doesn't aim to recognize every device in the world (there are several thousands), but it is able to work, analyze and extract all attributes available in the user agent. For most common devices we provide a lookup table in yaml file to identify device brand/model based on the few info available in the user agent. The library can be easily extended thanks to yaml files and a simple syntax (we don't rely on regular expression). Thanks to custom yaml definitions, you can make the library able to identify your company applications/ tools and extract your custom fields.
Advanced HTTP request analysis for device detection, browser identification, and geolocation services in ASP.NET Core applications. Provides comprehensive user agent parsing to detect device types (mobile, tablet, desktop), operating systems, browser versions, and bot detection. Includes IP-based geolocation with country, city, timezone detection using MaxMind GeoIP2 database. Features crawler/bot identification, proxy detection, and detailed request information extraction.
The User Agent Parser Library analyzes what device a customer or prospect is using to browse your site. It detects a wide range of browser types including Smart Phones, Tablets, Game Consoles, Smart TVs, Bots, Desktop, Applications, Validators, Vulnerability Scanners, Email Clients, and Site Monitors.
This client library enables working with Robots.txt. Key Features: - Parse robots.txt into Typed object. - Lookup Allowed/Disallowed/Crawldelay based on User-Agent. - Traverse sitemap in robots.txt for urls. For More info see: https://github.com/nicholasbergesen/robotsSharp/master/README.md
A simple middleware built on reflection designed to support your Search Engine Optimized (SEO) app by dynamically creating a Sitemap.xml and Robots.txt. This package is designed to be very simple for simple use cases but allows for custom disallowed routes, user agents, and custom node endpoints by supplying optional parameters to the middleware extension methods. Sitemaps.xml asks if you would like to parse the controllers - you can add the [NoSiteMap] attribute to any class or method you would not like included in the Sitemap.xml and the [Priority] attribute to set custom priorities per route. You can provide detail routing information for a dynamic sitemap.xml of items, e.g. a link for each product in the products database. The Robots middleware will allow you to add any number of RobotRules for defining your User-Agent and Disallowed routes. This middleware parses the existing controller structure and automatically includes all get endpoints in the dynamic Sitemap.xml while ignoring any Posts, Puts, or Deletes.
A simple middleware built on reflection designed to support your Search Engine Optimized (SEO) app by dynamically creating a Sitemap.xml and Robots.txt. This package is designed to be very simple for simple use cases but allows for custom disallowed routes, user agents, and custom node endpoints by supplying optional parameters to the middleware extension methods. Sitemaps.xml asks if you would like to parse the controllers - you can add the [NoSiteMap] attribute to any class or method you would not like included in the Sitemap.xml and the [Priority] attribute to set custom priorities per route. You can provide detail routing information for a dynamic sitemap.xml of items, e.g. a link for each product in the products database. The Robots middleware will allow you to add any number of RobotRules for defining your User-Agent and Disallowed routes. This middleware parses the existing controller structure and automatically includes all get endpoints in the dynamic Sitemap.xml while ignoring any Posts, Puts, or Deletes.
User Agent Parser parses user agent strings to extract browser, operating system, and hardware details. It identifies device types, CPU architecture, and bot traffic, so you can run user agent detection on every incoming HTTP request.
The Universal Device Detection library will parse any User Agent and detect the browser, operating system, device used (desktop, tablet, mobile, tv, cars, console, etc.), brand and model.
User Agent Generator creates realistic user agent strings for desktop, mobile, and tablet devices. Each request outputs the complete string with parsed browser and operating system names and versions, while paid plans add engine and CPU details.
Official .NET client library for the Ipregistry IP geolocation and threat data API. Look up a single IP address, the requester's own IP, or thousands in batch, and parse User-Agent strings. Async, cancellable, retrying, cacheable, DI-ready, and AOT/trimming compatible.
Optional IUserAgentParser for KustoLoco's parse_user_agent, backed by the canonical ua-parser/uap-core dataset (Apache-2.0). Core carries no user-agent dependency; register this provider on the host.