user agent device safari

The latest user agents for Safari

Updated at: Jul 01, 2024

Apple's Safari web browser runs on mobile devices (iPhones, iPads and iPod Touches) and macOS computers. Depending on which platform you're using (or want to pretend you're using!) the user agent will be a bit different.

Here we have the latest user agents for Safari on mobile and computer platforms.

Unlike some other popular browsers and platforms, we've noticed that Safari definitely seems to have less "extra" stuff in its user agent - standard Safari will never announce the exact model number of the device being used, and there's generally much less additional fragments added by installed addons/apps - toolbars and so on.

That said, you're welcome to explore our huge listing of various Safari user agents to see the different variations of user agents.

Latest Safari on macOS User Agents

Latest safari on ios user agents, special notes, safari on ios 13.

You may have already noticed, but Safari on the latest version of iOS (version 13) no longer includes fragments to indicate that Safari's running on iOS... instead the user agent is indistinguishable from the desktop version of macOS.

As such, it's not possible to provide valid sample user agents for them any more.

Build numbers and OS version numbers

Test it out.

You can use our User Agent Parser page to try out different user agent varieties, or to test if your user agent switcher is working properly.

Database of user agents

If you're interested in our database of many millions of user agents, please check out our API which provides access to our user agent database . You can perform very detailed and specific queries on it to find user agents that match your exact criteria - version numbers, hardware types, platforms and so on.

Update my web browser

Do i need to update my browser.

Find out if your browser is out of date Is my browser out of date?

Why should I update my browser?

There are very good reasons to, find out here! Why update your browser?

Is it free to update Chrome?

Find out about the cost of updating Chrome... Does Chrome cost anything?

Get help with our guides

How to enable javascript.

Change your JavaScript settings Guide to enabling Javascript

How to enable Cookies

Configure your cookie settings for privacy Guide to enabling cookies

Related articles

Web browsers without ai.

Some web browsers manufacturers have started adding AI features to their browsers, others have decided not to. Which web browsers don't have AI in them?

I can't log in to a website.

We've got a detailed guide to help you solve login problems How to fix website log in problems

Why do websites use cookies?

Why are cookies useful? Do you need them? What's the deal with cookies?

Clear Cache, Cookies and History

How to reset your browsing history How to reset your browser

Try a different web browser

Different web browsers have different features - try a different one to see if you prefer it. Experiment a bit!

Use a VPN to hide your IP address

We recommend NordVPN to hide your IP address or to unblock websites. Hide your IP Address

• Do Not Sell My Personal Info

How to Change User Agents in Chrome, Edge, Safari & Firefox

Discover how to change user agents in web browsers for testing purposes. Learn how to ensure your campaigns are running properly and target the right audience.

Whether you are an SEO pro, marketer, or web developer, you might often need to change your browser’s user-agent to test different things.

For example, imagine you’re running a MAC-OS-specific campaign. To find out if your campaign is running properly and not targeting Linux users, changing the user-agent of your browser can help you test.

Changing user-agents is almost a daily task for web developers, as they need to test how websites behave in different browsers and devices.

What Is A User-Agent?

A user-agent is an HTTP request header string identifying browsers, applications, or operating systems that connect to the server.

Browsers have user-agents, and so do bots and crawlers such as search engines Googlebot , Google AdSense, etc.

Here, we will learn how to change your browser’s user-agent.

The process is called user-agent spoofing .

Spoofing occurs when a browser or client sends a different user-agent HTTP header from what it is and fakes it.

While the term may be alarming, this is not a dangerous activity and will not cause you any problems. (Feel free to spoof your user-agent as much as you want.)

How To Change Your User-Agent On Chrome & Edge

Since Microsoft Edge is now using Chromium , the settings for both Chrome and Edge are the same.

1. Right Click Anywhere On Webpage > Inspect

Alternatively, you can use CTR+Shift+I on Windows and Cmd + Opt +J on Mac.

2. Choose More Tools > Network Conditions

Screen new.

Click on the three vertical dots in the upper right corner.

3. Uncheck Select Automatically Checkbox

4. Choose One Among The Built-In User-Agents List

If the user-agent you want doesn’t exist, you can enter any string you want on the field below the list.

For example, you can enter the following (Googlebot’s user-agent) into the custom field:

This may be useful for SEO professionals to identify if there is a cloaking on the website where the webpage shows specific content to Googlebot and different content to website visitors.

Alternatively, you can use the Chrome extension User-Agent Switcher and Manager .

That said, I try not to use browser extensions when the browser can perform the action I want. This is to avoid overloading the browser with add-ons.

Also, extensions have a habit of breaking websites unexpectedly sometimes.

While you might think the website you visited has an issue, the root cause can be one of the add-ons you’re using.

How To Change User-Agent On Safari

1. go to preferences.

2. Enable Develop Menu Bar

Go to Advanced  and check Show Develop menu in menu bar .

3. Navigate To Develop > User-Agent

You can again select from a predefined list or enter a custom user-agent string by choosing “Other…”

How To Change User-Agent In Firefox

In Firefox, it is possible to change user-agents via the browser’s built-in settings.

However, it is not as user-friendly as on Chrome or Safari.

It is a real pain to use the browser’s built-in feature.

Instead, we will use a Firefox add-on called User-Agent Switcher .

After installing the add-on, you will see an icon in the upper right corner.

You can select one of the predefined user-agents or enter a custom user-agent by clicking on the pen icon below.

Another extension you can use is User-Agent Switcher and Manager .

User-Agents Are Easy To Spoof

The user-agents are easy to spoof, and anyone can use these easy tricks to alter them.

This feature is useful for testing web apps against various devices, especially when the HTML is different for mobile  or tablet devices.

It is a cost-efficient way to test websites as one doesn’t need to have many physical devices to be able to test.

However, certain issues may appear on the real device but not when testing by changing the user agent and using a browser emulator.

In that case, if you want to test on multiple real devices, I suggest using Browserstack , which offers testing opportunities on almost all devices.

What is a user agent?

User agent is a HTTP request header string identifying browser, application, operating system which connects to the server. Not only browsers have user agent but also bots, search engines crawlers such as Googlebot, Google Adsense etc. which are not browsers.

What is user-agent spoofing?

When browser or any client sends different user-agent HTTP header from what they are and fakes it that is called spoofing .

How does changing the user-agent help SEO professionals?

SEO professionals may find changing the user-agent to be a critical part of their audit process. It is beneficial for several reasons:

• Identifying cloaking issues : By mimicking different user-agents, such as Googlebot, SEO experts can uncover whether a website presents different content to search engines than users, which violates search engine guidelines.
• Compatibility: It ensures web applications are compatible across various browsers and devices.
• User Experience : Developers can optimize the user experience by understanding how content is rendered on different systems.
• Debugging: Changing the user-agent can help pinpoint browser-specific issues.
• Quality Assurance: It’s an essential step in quality assurance and helps maintain the integrity and performance of a website.

Can changing your browser’s user-agent pose a security risk?

No, changing your browser’s user-agent, commonly called user-agent spoofing, does not inherently pose a security risk. While the term “spoofing” might suggest malicious intent, this practice in the context of user-agents is harmless. It is a tool for developers and marketers to test how websites and applications interact with various devices and browsers.

More resources:

• An Introduction to Rendering For SEO
• Using Chrome DevTools To Diagnose Site Issues In An Audit
• 7 Essential SEO Browser Extensions & Plugins

Featured Image: /Shutterstock

All screenshots taken by author, May 2024

I am dedicated to ensuring the smooth and uninterrupted operation of Search Engine Journal. As the Director of Technology, I ...

Subscribe To Our Newsletter.

Conquer your day with daily search marketing news.

Useragents.me

Last updated: 17 june, 2024.

A self-updating list of the latest and most common useragents seen on the web across all device types, operating systems, and browsers. Data is always fresh, updating weekly.

This user agent list is perfect for web scrapers looking to blend in, developers, website administrators, and researchers.

The most common useragents list is compiled from the user logs data of a number of popular sites across niches and geography, cleansed (bots removed), and enriched with information about the device and browser.

Most Common Desktop Useragents

Most common mobile useragents, latest windows desktop useragents.

• Latest Mac Desktop Useragents

Latest Linux Desktop Useragents

Latest iphone useragents, latest ipod useragents, latest ipad useragents, latest android mobile useragents, latest tablet useragents.

• Smartproxy: Fast, Reliable Proxies
• Free Proxy Checker

An updated list of the most common useragents on the web, specifically the most common desktop useragents. You can see the relative share of each useragent included in the data table below. Hint: scroll sideways if you're viewing this page on a mobile device.

Get useragent list as JSON or TSV

Get the most common desktop useragents list conveniently in JSON format

Get the most common desktop useragents list conveniently in TSV (tab separated values) format

An updated list of the most common useragents on the web, specifically the most common mobile useragents. You can see the relative share of each useragent included in the data table below. Hint: scroll sideways if you're viewing this page on a mobile device.

Get the most common mobile useragents list conveniently in JSON format

Get the most common mobile useragents list conveniently in TSV (tab separated values) format

A complete list of the absolute latest Windows (desktop) useragents.

Latest Mac OS X Desktop Useragents

A complete list of the absolute latest Mac OS X (desktop) useragents.

A complete list of the absolute latest Linux (desktop) useragents.

A complete list of the absolute latest iPhone (mobile) useragents.

A complete list of the absolute latest iPod (touch mp3 player) useragents.

A complete list of the absolute latest iPad (tablet) useragents.

A complete list of the absolute latest android (mobile) useragents.

A complete list of the absolute latest tablet useragents.

About useragents.me

Useragents.me was created for web scrapers to give them quick and easy access to a list of the latest and most commmon useragents. Many similar lists have appeared in the past before us, but which have been quickly forgotten about and left to die.

Useragents.me is run and developed by someone working directly in the business of web scraping and who uses the site himself daily. Furthermore it's designed to be self-sustaining, self-updating, and low mantinence — meaning it will be a resource you can trustfully rely on for years.

What can I do with the useragents listed here?

The useragents listed here are most commonly used by web crawlers and web scrapers who want to mask their requests.

How often is the list of most common user agents updated?

The list of most common useragents (both desktop and mobile) is updated every week (specifically, on Sunday nights).

What is my current useragent?

As far as we can see, it's:

What is the difference between the most common and latest useragents listed here?

• The most common useragents list is a list of useragents that were observed accessing a set of sites in a given period of time. If you need to scrape a large number of pages and want your scraping requests to 'blend in', you can likely safely use this list in rotation to be successful.
• The latest useragents list is a list of the absolute latest useragents for a specific browser and device type. If you don't have a large scraping task (and so don't need to rotate useragents), you can likely safely use just one of these.

When should I use a mobile or desktop useragent?

Some sites will give you different content depending on the device you're using, so you should select the user agent with the correct device type for the task.

Node.js API Wrapper

useragents-me-api (by Davide Violante)

Built something with our API and want it featured here? — DM me @_stayml .

Useragents.me has been featured in...

• latenightlinux
• stackoverflow
• infoextreme
• Softantenna
• 阮一峰的网络日志 (Ruan Yifeng's weblog)

© 2022 - 2024 Useragents.me

Home » Tech Tips » Browsers » How to Change User Agent in Mac Safari Browser?

How to Change User Agent in Mac Safari Browser?

Mac comes with Safari as a default web browser app. Though Safari works well for visiting website, many prefer Chrome for development and integration purposes. If you are using Safari, did you anytime wonder how a website you see in Safari will look like in Chrome on Mac? You will probably install Chrome and check the site. However, what will you do if you want to test in Chrome Windows version or Microsoft Edge Windows version? Good thing is that it is not necessary to install Chrome and you can change the user agent in Safari as Chrome and test the sites easily.

User Agents

Each browser has its own user agent string so that the website owner can identify how the site is being accessed. The string will change based on the device, operating system and browser version you use. For example, below is the user agent for Chrome in Mac. You can use this free tool to check your browser’s user agent.

From this information, you can find the device is Macintosh and Chrome version 114 is used to access your website. For mere testing purposes, you do not need to install Chrome, Edge or Firefox in your Mac for checking the websites on those browsers. All you need is to simply switch the user agent string in Safari and test the site’s appearance.

Changing User Agent in Safari Mac

Since user agent is kind of developer stuff, Safari by default will disable this feature. You need to first enable “Develop” menu to reveal the feature in Safari.

• Open Safari app in Mac and go to “Safari > Settings…” menu.

• Go to “Advanced” tab and enable “Show features for web developers” option showing at the bottom.

• Close Safari Settings pop-up and now you will see a “Develop” menu added to the browser.
• Click on “Develop” menu and hover over “User Agent” to view a list of items.
• By default, Safari automatically chooses the user agent and you can switch to one of the available agents from the list.
• If you want to check the string, just hover over any item and Safari will show the full string as a tooltip for you to check.

Available and Custom User Agents

As of Safari 17.0, below are the available user agents showing in the menu items for the latest OS/browser versions. User agent string will be automatically updated in Safari when the OS/browser gets new version.

• Safari – Mac, iPhone, iPad Mini and iPad.
• Microsoft Edge – macOS and Windows
• Google Chrome – macOS and Windows
• Firefox – macOS and Windows

You can switch the user agent to any of these browsers and test the site. If you want to use custom string, then click on “Custom” menu showing as a last option in the menu. This will show a text box in the pop-up where you can enter your custom user agent string and click “OK” button.

Testing Websites

After choosing the user agent, open the site that you want to test. Now, Safari will load the site as if you are seeing on different browser or device.

You can switch the user agent any time and Safari will reload the page using the new user agent. This way you can test whether the site is loading properly on different browsers without installing them on your Mac.

If you are using Chrome, learn more on how to change user agent in Google Chrome .

About Nagasundaram Arumugham

Naga is the founder and chief content editor of WebNots. He has over 20 years of experience in technology field and published more than 2000 articles.

You also might be interested in

Fix Slow Page Loading Waiting for ajax.googleapis.com in Browsers

Are you tiered of seeing the message waiting for “ajax.googleapis.com”[...]

Top 10 Google Chrome Extensions for Improving Your Productivity

Extensions are a great way to enhance productivity and perform[...]

Top 5 Safari Browser Alternatives in iPhone

Safari is the default browser in iPhone. It comes with[...]

DOWNLOAD EBOOKS

• SEO Guide for Beginners
• WordPress SEO PDF Guide
• Weebly SEO PDF Guide
• Alt Code Emoji Shortcuts PDF
• Free ALT Code Shortcuts PDF
• View All eBooks

TRENDING TECH ARTICLES

• 600+ Windows Alt Codes for Symbols
• Fix Chrome Resolving Host Problem
• Fix Slow Page Loading Issue in Google Chrome
• View Webpage Source CSS and HTML in Google Chrome
• Fix Safari Slow Loading Pages in macOS
• Fix Windows WiFi Connection Issue
• ROYGBIV or VIBGYOR Rainbow Color Codes
• Fix I’m Not A Robot reCAPTCHA Issue in Google Search
• Structure of HTTP Request and Response

POPULAR WEB TUTORIALS

• Move WordPress Localhost Site to Live Server
• Move Live WordPress Site to Localhost
• Move WordPress Media Folder to Subdomain
• Fix WooCommerce Ajax Loading Issue
• Create a Free Weebly Blog
• Edit Weebly Source Code HTML and CSS
• Add Scroll To Top Button in Weebly
• Add Table in Weebly Site
• How to Add Advanced Data Table Widget in Weebly?
• Up to $500 Free Google Ads Coupon Codes

FREE SEO TOOLS

• Webpage Source Code Viewer
• HTTP Header Checker
• What is My IP Address?
• Google Cache Checker
• Domain Age Checker Tool
• View All Free Web and SEO Tools

© 2024 · WebNots · All Rights Reserved.

Type and press Enter to search

Parse a User Agent String

Every time your web browser makes a request to a website, it sends a HTTP Header called the " User Agent ". The User Agent string contains information about your web browser name, operating system, device type and lots of other useful bits of information.

But every browser sends its user agent in a different format, so decoding them can be very tricky.

Use this tool to parse any user agent string you want to understand. We'll show you what the user agent means; whether it's a popular system like Safari on iPad, Chrome on Windows, whether it's a search engine spider bot or security analysing tool.

Why not start by parsing your browser's own user agent .

Explore the database of User Agents

We've got a huge collection of user agents grouped by browser, OS, platform, hardware and software types and layout engines.

• Facebook App (8,591,685)
• Chrome (5,019,455)
• Instagram (4,943,685)
• Android WebView (4,007,680)
• TikTok (665,198)
• Opera (636,879)
• Google News (540,099)
• Snapchat (515,196)
• WeChat (254,295)

Browse all Software Names

Operating Systems:

• Android (18,729,759)
• iOS (7,643,072)
• Windows (308,010)
• Linux (69,946)
• macOS (60,589)
• Mac OS X (44,074)
• Fire OS (14,018)
• Symbian (6,742)
• Chrome OS (2,988)

Browse all Operating Systems

Operating Platforms:

• Apple iPhone (1,630,389)
• Google Pixel 2 (881,858)
• LG Nexus 5 (876,785)
• Samsung SM-G900P (873,700)
• Motorola Moto G (786,253)
• Redmi (391,593)
• Apple iPhone 11 (390,418)
• Apple iPhone 13 (302,610)
• Apple iPhone 12 (287,782)

Browse all Operating Platforms

Software Types:

• In-App Browser (19,860,594)
• Web Browser (6,979,891)
• Crawler (131,265)
• Application (16,397)
• Site Monitor (12,069)
• Analyser (2,555)
• Bot (1,806)
• Media Player (1,612)
• Software Library (727)

Browse all Software Types

Hardware Types:

• Phone (14,997,455)
• Mobile (9,868,413)
• Tablet (1,516,726)
• Computer (477,160)
• Server (148,958)
• TV (15,163)
• E-Book Reader (14,050)
• Music Player (4,366)

Browse all Hardware Types

Layout Engines:

• WebKit (17,657,003)
• Blink (8,733,051)
• EdgeHTML (170,014)
• Gecko (74,046)
• NetFront (53,259)
• Trident (20,457)
• Presto (1,894)
• Goanna (370)

Browse all Layout Engine Names

Sick of looking at user agents? Use our API.

• Your User Agent

Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)

• Your IP Address

185.80.149.115

• Country Name: Russian Federation
• Latitude: 55.7386
• Longitude: 37.6068

• Browser Information
• Browser Name: unknown
• Browser Type: Unknown
• Browser Version: unknown
• Browser Engine: unknown
• Opera System Information
• Name: unknown
• Version: unknown
• Platform: unknown
• Device Information
• Brand: Desktop
• Type: Desktop

What Is a User Agent?

A browser's user agent string (UA) helps identify which browser is being used, what version, and on which operating system. When feature detection APIs are not available, use the UA to customize behavior or content to specific browser versions.

Useragent is a small piece of data that is sent by your web browser when accessing a website or application. It is used to identify the type of browser you are using, what device and operating system you are using, and the version of the browser you are using. This information is important for websites and applications to ensure optimal performance and compatibility. It also allows developers to customize their websites and applications based on user agent data.

How-To Geek

How to change your browser's user agent without installing any extensions.

Your changes have been saved

Email Is sent

Please verify your email address.

You’ve reached your account maximum for followed topics.

Steam's Summer Sale is Live

10 years later, i'm still using this popular android automation app, this new android 15 feature is going to save my battery life, quick links, google chrome, mozilla firefox, microsoft edge and internet explorer, apple safari.

If you ever wanted to make your web traffic seem like it was coming from a different browser--say, to trick a site that claims it's incompatible with yours--you can. All popular browsers offer built-in user agent switchers, so you can change your user agent without installing any extensions.

Related: What Is a Browser's User Agent?

Websites identify browsers by their " user agents ". Change a browser's user agent and it will report it's a different browser to websites. This allows you to request web pages intended for different browsers--or even different devices, like smartphones and tablets.

Chrome's user agent switcher is part of its Developer Tools. Open them by clicking the menu button and selecting More Tools > Developer Tools. You can also use press Ctrl+Shift+I on your keyboard.

Click the menu button to the right of the "Console" tab at at the bottom of the Developer Tools pane and select "Network Conditions"

If you don't see the console at the bottom, click the menu button at the top right corner of the Developer Tools pane--that's the button just to the left of the "x"--and select "Show Console".

On the Network conditions tab, uncheck "Select automatically" next to User agent. You can then select a user agent from the list or copy and paste a custom user agent into the box.

This setting is temporary. It only works while you have the Developer Tools pane open, and it only applies to the current tab.

In Mozilla Firefox, this option is buried on Firefox’s about:config page.

To access the about:config page, type

into Firefox’s address bar and press Enter. You’ll see a warning--be careful when you change settings here, you could mess up Firefox’s settings.

into the filter box. We’re looking for the

preference, but it probably won’t exist on your system.

To create the preference, right-click on the about:config page, point to New, and select String.

Name the preference

Enter your desired user agent as the value of the preference. You’ll have to look up your desired user agent on the web and enter it exactly. For example, the following user agent is used by Googlebot, Google’s web crawler:

Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)

You can find extensive lists of user agents on various websites, such as  this one .

This setting applies to every open tab and persists until you change it, even if you close and reopen Firefox.

To revert Firefox to the default user agent, right-click the "general.useragent.override" preference and select Reset.

Microsoft Edge and Internet Explorer have user agent switchers in their developer tools, and they're nearly identical. To open them, click the settings menu and select "F12 Developer Tools" or just press F12 on your keyboard.

The developer tools will open in a separate pane at the bottom of the window. Click the "Emulation" tab and choose a user agent from the "User agent string" box. You can also select the "Custom" option in the User agent string list and type a custom user agent into the box. You can find extensive lists of user agents on various websites, such as  this one .

This setting is temporary. It only applies to the current tab, and only while the F12 Developer Tools pane is open.

This option is available in Safari's normally hidden Develop menu. To enable it, click Safari > Preferences. Select the "Advanced" tab and enable the "Show Develop menu in menu bar" option at the bottom of the window.

Click Develop > User Agent and select the user agent you want to use in the list. If the user agent you want to use isn't shown here, select "Other" and you can provide a custom user agent. You can find extensive lists of user agents on various websites, such as  this one .

This option only applies to the current tab. Other open tabs and tabs you open in the future will use the "Default" user agent.

• Control Panel

Sign up for our daily newsletter

• Privacy Policy
• Advertise with Us

How to Change the User Agent in Safari for Mac

In order to let websites serve browser-specific settings and pages, your browser sends a string called user agent to the websites that you visit on your computer. That way the target website gets to know what browser you are using and serves the pages accordingly. While most websites look the same in every browser, some have specific files that are only rendered when using a specific browser, Safari, for example. If you wish to see how a site looks in a specific browser, you can change the user agent in Safari on your Mac and pretend to be another browser.

When you change the user agent string, it technically changes the way websites interact with your browser. For example, if a site has a file that only renders when you’re using Chrome for Android, you can change the user agent to Chrome for Android in Safari and see that site as if you’re viewing it for real on your Android device.

Here’s how you can go about doing that.

Changing the User Agent in Safari for Mac

Fire up Safari on your Mac from the dock.

Click on “Safari” in the top left corner and select “Preferences…” You will be taken to the preferences panel for your browser.

Once in the “Preferences” panel, click on the “Advanced” tab located in the top bar. It should open the advanced settings for your browser.

In the “Advanced” tab, you should see an option that says “Show Develop menu in menu bar.” Tick mark it, and it will add a new menu in the menu bar for you to change the user agent.

Pull down the new menu by clicking on “Develop” in the menu bar. Then select “User Agent,” and you should see a list of the predefined user agents that you can use right away with your browser. Click on any and it will be selected.

If you can’t find the user agent you want to use, click on “Other” in the menu, and it will let you manually specify one.

You should see a prompt asking you to enter a user agent string that you wish to use in Safari on your Mac. This part is usually used by the geeks or developers who know what a user agent looks like and how to write one. If you are unsure, you can use the help of the User Agent String website to try out various agents in your browser.

When you are done entering the string, click on “OK,” and it will save it for you.

To check whether the new user agent works or not, just visit any site that lets you check what browser you are using, and it will tell you the name of the browser depending on what user agent you provided in the previous step. I have provided the Opera Mini user agent thus the browser check site says I’m using Opera Mini, although my actual browser is Safari.

The user agent has been changed in Safari on your Mac, and you are now telling websites that you don’t use Safari but use another browser because the user agent string says so.

If you are looking to see how a website looks like in another browser without actually downloading it, you can use the above method and have Safari pretend to be the browser you want.

Our latest tutorials delivered straight to your inbox

Mahesh Makvana is a freelance tech writer who's written thousands of posts about various tech topics on various sites. He specializes in writing about Windows, Mac, iOS, and Android tech posts. He's been into the field for last eight years and hasn't spent a single day without tinkering around his devices.

User-Agent Switcher and Manager

205 ratings

Spoof websites trying to gather information about your web navigation to deliver distinct content you may not want

Usage example: You can alter your user-agent string to indicate you?re on a mobile device if you prefer seeing mobile versions of sites so they load quicker. -- This extension allows you to spoof your browser "user-agent" string to a custom designation, making it impossible for websites to know specific details about your browsing arrangement. Video overview: https://www.youtube.com/watch?v=4M6_Zc4o1MQ Notes: 1. You can easily set custom "user-agent" strings from the toolbar popup 2. The extension uses a two-factor technique to mimic your default "user-agent" string, which is the most reliable method 3. The extension does not use any resources when it is not spoofing the user-agent 4. The extension enables user-agent spoofing on specific domains only; it is conversely possible to exclude certain domains from spoofing. Check the Options page for more info. 5. You can set per-site user-agent strings 6. There is an option to randomize user-agent strings. 7. It is possible to set user-agent string for a single window; you can have a separate user-agent string for each browser window For more info and general bug reports please use: https://add0n.com/useragent-switcher.html For technical bug reports please use: https://github.com/ray-lothian/UserAgent-Switcher/

4.4 out of 5 205 ratings Google doesn't verify reviews. Learn more about results and reviews.

Brickstin Jun 25, 2024

Recent updates to this extension has completely prevented Facebook.com from functioning. This extension is completely useless now............It has broken Facebook entirely.. Worked great while it lasted.

Bill Diavastis (Ironhead HD) Jun 24, 2024

Does what it's supposed to do, not to complete perfection, but i think it's deserving of a 5 star rating.

This developer declares that your data is

• Not being sold to third parties, outside of the approved use cases
• Not being used or transferred for purposes that are unrelated to the item's core functionality
• Not being used or transferred to determine creditworthiness or for lending purposes

For help with questions, suggestions, or problems, visit the developer's support site

Spoof Timezone

Change the time zone setting for web pages in the browser to a randomly selected or user-specified time zone.

WebRTC Control

Have control over WebRTC (disable | enable) and protect your IP address.

Fingerprint Spoofing

Modify your broswer fingerprint!

Canvas Fingerprint Defender

Defending against Canvas fingerprinting by reporting a fake value.

User-Agent Switcher for Chrome

Spoofs & Mimics User-Agent strings.

User Agent Switcher

Simplest way to switch between user-agents in your browser!

User-Agent Switcher

Switch between popular useragent strings from toolbar popup!

Random User-Agent (Switcher)

Automatically change the user agent after specified period of time to a randomly selected one, thus hiding your real user agent

Automate changing IP Address for TM Proxy!

치직치지직 (ChzkChzzk)

치지직(chzzk.naver.com)을 더 유용하게!

User-Agent like never before! Set User-agent by domain, URL, wildcard, keyword, regex (or global). Keep Mobile page or desktop…

User-Agent Switcher (Deprecated)

Change User-Agent Setting. Spoof it to the UA of Firefox, Android, Chromebook, Safari, Googlebot or a custom string.

What's my user agent?

See what your user-agent detection library really thinks!

According to  useragent  v2.2.1:

• rawUa: Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)
• family: Googlebot
• device: Spider 0.0.0
• string: Other 0.0.0
• family: Other

According to  ua-parser-js  v0.7.31:

According to  platform.js  v1.3.6:.

• name: Google Browser
• product: Google bot 2.1
• manufacturer: Google
• description: Google Browser on Google bot 2.1

GET /api/v1/ua?ua=<ua-string>&version=<ua-parser-version>

Parameters:

• ua-string : Be sure to url-encode it. Defaults to your request's user agent string.
• ua-parser-version : Coming soon. Defaults to "latest".

User Agent in Safari on iPadOS

During authentication flow in Safari, we have a case when in order to satisfy a condition policy, user needs to install the app on his device. Depending on the OS, we ask him to install different applications. Since on iPadOS User Agent in Safari is same as on MacOS Catalina, what is recommened way to distinguish OS on server side?

Safari : Mozilla/5.0 ( Macintosh; Intel Mac OS X 10_15 ) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.0 Safari/605.1.15

MacOS Catalina:

Safari : Mozilla/5.0 ( Macintosh; Intel Mac OS X 10_15_0 ) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.100 Safari/537.36

I have a similar situation as antrix1989 where our webclient determines if a user is browsing via an iPad with JavaScript and alters/restricts the content. We can then market our clients to a subscription on/with our native iOS app. Would be super helpful if the User Agent stated it was iPad OS instead of Mac OS X:

so a regex match could be done to fairly certain determine a user was on iPad.

Hopefully this will change closer to or after the release?

Any update on this? Will the issue be solved before ios13 is released? I'm facing the same issue on iPads.

In our case we use the user agent to detect if the browser belongs to a mobile device.

This is important because on mobile devices we set our web application to listen the touch events such touchstart, touchend, etc, to drag some elements. But currently we cannot subscribe to those events since we cannot detect it is a mobile device.

Somebody in another forum suggested me to verify if Safari browser is not set to show the desktop version of the web site. I'll check that today. But I think this is still an issue because even if user agent is retrieved as the desktop device, mouse events are not being emulated by safari.

I opened Settings -> Safari -> Request Desktop Website -> All websites. That option is enabled by default. I disabled it and the proper User Agent is now displayed.

Mozilla/5.0 ( iPad ; CPU OS 13_0 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.0 Mobile/15E148 Safari/604.1

IMO it should be disabled by default and if a user enables it a modal window should be displaying indicanting not all web sites will be supported properly. Or maybe you may consider to add the iPad word to the first user agent to allow us to detect if it is an ipad emulating safari desktop or enable mouse event emulation, because I think when it is released several websites will fail.

I have the same issue with one of our sites, we render certain functionality for mobile devices (ipad included) based on the user agent.

The workaround esteban26 suggested works, but it's not ideal if it's enabled by default, It would be great if Apple considers adding the iPad word, or any other identifier to the user agent string.

Agree this should be disabled by default. The current user-agent lies about both the OS and the chipset (Intel vs Arm)

I had submitted a request to add a User Agent change function similar to the Desktop. On my desktop, there are some enterprise web apps speicifally look at browser versions and break on the latest version even though the app would work perfectly fine. I've done this several times where I change the Safari user agent to Chrome or IE11 and apps function just fine. It's just one more thing that would release corporate users from a desktop.

We have same issue here, certain functinalities are dependent on iPad word as well. I also expecting also Apple added back iPad or other keyword to identify iPad.

I have a similar situation.

Any solution or update ?

Again we need some way of determining an iPad

FYI, I submitted feedback/bug report via the Feedback app on the iPad back on July 3rd, 2019. Apple responded on the 19th wanting specific details/steps on how to reproduce the error... I gave specific steps on how to view the user agent via the safari developer console and have yet to hear back from them. The feeback app is reporting "More than 10" recent similar reports and the resolution is still "Open".

Starting to think they're not concerned about this.

Hopefully it will be resolved before launch.

This will impact thousands of our users 😟

Any news on this?

This is a problem for one of our application which is provided for major clients.

Would there be any meta tag which if present by default will launch the site in mobile?

Anyone else have any update on this?

Hi Antrix1989,

from what I've observed another way to load a mobile version of a given website on iPadOS is to ensure that the browser's width is compact. To achieve this you must use the multi-tasking feature and place safari in a popup or split paned with another app such that Safari now has compact width.

This doesn't work for me running iOS 13.1.2 on iPad. I turned "Request Desktop Website On All Websites" OFF and UserAgent still reports "Macintosh".

Is there something obvious I'm missing here? I am shocked this isn't causing complete chaos with all the web apps out there.

I'm starting to wonder if 'iPadOS' is code for Catalyst.

After all, we're told we can build one app for mac and ipad...where is the bifurcation to help websites deliver their mobile-centric version?

Now that ios13 is out of Beta and deployed does anybody else still see the UA issue for Safari

Is there any fix on the horizon - We can't ask the entire Safari iPad using internet to know about and toggle this Dev tools fix

I can't believe they set this option to default on iPads, from minimal testing it's the Safari and Firefox browsers on iPads that default to "Desktop View" (Chrome still defaults to mobile website on ipads) and no one is offering a way for developers to get around this.

I collapse my menus on mobile devices and remove/add certain elements that are different from my desktop site and this completely destroys all of that coding.

This is still an issue. Yes, the Desktop settings workaround does help get a sensible userAgent, but nobody on a large iPad is ever going to set that. The main issue I have is that I'm developing an HTML5 Audio player where we want to hide our volume control interface when the device is an iPhone or iPad, since there is no way to control HTML5 Audio volume property via Javascript on these devices. Does anyone have a sane solution to this?

OK I have a solution.

Simply create an HTML5 Audio object and attempt to set the .volume property.

Mobile Safari can't do this.

You're welcome.

Agreed. This is a devasting user experience for the iPad. And you want people to choose an iPad over a Mac and you make completely stupid moves like this? For example, iPadOS does not auto-uncompress .zip files like a Mac. Users come on the support saying how nothing works, because when they tap the download it's broken. Even sophisticated users have to poke around to find "Uncompress" buried at the bottom of the the long-touch menu. If you didn't LIE to my web server, I could offer the uncompressed link, and everything would be fine.

Do not LIE about your user-agent, certainly CPU architecture and operating system. That is the kind of schmuck moves the old Microsoft would make. Perhaps they hired the MSIE team. So short sighted. *** Apple?

Hi, so it looks like User Agent "sniffing" will no longer work for iPad iOS 13+. If you have control over the devices, you could turn off the setting "Request Desktop Website" (Settings -> Safari -> Request Desktop Website (under Settings for Websites), but... I'm assuming you don't have control over the client device settings.

I did find this fix Repeated link if the embedded one doesn't work: ( https://stackoverflow.com/questions/9038625/detect-if-device-is-ios ).

Essentially, just tack on the solution to whatever current User Agent detection you are running.

(copied below in case the answer is lost on Stack)

Maybe Apple specifically wants iPadOS users to experience desktop websites by default, so they made its default user agent look like it's macOS?

How to Change Your Browser's User Agent and Trick Websites

Your changes have been saved

Email Is sent

Please verify your email address.

You’ve reached your account maximum for followed topics.

When Does Facebook Messenger Notify Others About Screenshots?

4 vpns that don't require you to sign up or register, the best smartphone controllers of 2024.

In the early days of the internet, websites didn't care what browser you used, because most pages were static. But today's dynamic websites often adapt to the operating system, browser, or screen size your device uses.

They typically do so through a bit of text called the user agent. So, let's look at what a user agent is, what it does, and how you can make your browser pretend to be another browser or another device.

What Is a User Agent?

A user agent is a string (line of text) that your browser sends to websites when you access them. It basically serves to tell the website that you're using the Chrome browser on Windows 10, for example.

If you'd like, you can see your user agent by visiting a site like WhatIsMyBrowser .

User agents are important because sites can use them to modify the content they send to your browser. For example, if you visit most modern sites in Internet Explorer 6, you'll see a message that you need to upgrade your browser for proper compatibility. User agents also come into play when browsing on a mobile device, so websites know to show you the mobile-friendly version of a page.

As it turns out, your user agent isn't permanent. It's easy to change if you know where to look, and some extensions let you change it in just a few clicks.

How to Change Your User Agent

Let's look at how to change your user agent in major browsers. This will let you trick websites into thinking you're on a different type of computer or browser.

Change Your User Agent in Chrome

Open Chrome's Developer Tools by right-clicking anywhere and choosing Inspect , hitting Ctrl + Shift + I , or by pressing F12 .

At the bottom of the resulting panel, you should see a section with the tabs Console , Network conditions , and What's New . Press Esc to show this if you don't see it.

On the Network conditions tab, uncheck Select automatically and you can then choose a new user agent from the list. Refresh to update the page with the new agent.

Note that this setting will revert back to normal when you close the developer panel, and only applies to your current tab.

For more control, check out Google's official User-Agent Switcher for Chrome extension . This lets you easily switch your user agent, including setting certain sites to use a different agent all the time.

Change Your User Agent in Firefox

The process to change your user agent in Firefox is clunky, as it requires you to manually paste a new user agent string. You're better off using an add-on to easily change your user agent.

User-Agent Switcher by Alexander Schlarb is well-reviewed and easy to use.

Change Your User Agent in Microsoft Edge

Microsoft Edge uses a similar setup to Chrome for changing your user agent. Press F12 or right-click on an empty spot of the page and choose Inspect element to open the developer tools window.

Along the top bar, select the Emulation tab---you may need to click the dropdown arrow to show it if it's hidden.

Here, change the User agent string box to trick the website into thinking you're something else. You can also change Browser profile from Desktop to Windows Phone to view the mobile version of webpages. Like Chrome, this only applies to the current tab while the developer tools panel is open.

Unfortunately, there are no extensions that easily change your user agent for the current version of Edge. When Microsoft's revised browser launches, this will hopefully change.

Change Your User Agent in Safari

You'll need to enable the hidden Develop menu in Safari before you can change your user agent. To do this, visit Safari > Preferences and go to the Advanced tab.

There, check the box labeled Show Develop menu in menu bar .

Next, select Develop > User Agent and pick the option you'd like. Safari even lets you choose Other to specify your own user agent string.

Request Desktop Site on Android and iPhone

While there's no quick toggle to change your user agent in the mobile versions of Chrome and Safari, you can easily make websites think your phone is a computer.

On Android, open Chrome and tap the three-dot Menu button in the top-right. Check the Desktop site box and it will reload to show you the full version.

On Safari for iOS, tap the aA button to the left of the address bar and choose Request Desktop Website . You'll find the same option in Chrome for iPhone by tapping the Share button at the top-right, followed by scrolling down and choosing Request Desktop Site .

Reasons to Change Your User Agent

Now you know how to trick websites into thinking you're on another device. But why would you change your browser's user agent when you can just install another browser?

Here are some situations where changing your user agent could prove to be fun, useful, or convenient.

1. Website Development

If you're developing a website (or learning about website development), it's important to make sure your site looks good and functions properly in a variety of browsers. While swapping your agent can't accommodate every possible real-world situation, it lets you get some basic testing done in a fraction of the time.

Perhaps you can test Chrome, Firefox, Edge, and Internet Explorer just fine on your own. But what if you don't have a Mac to run Safari, or don't have a tablet to test mobile versions of the page?

Further, if backward compatibility is important for your site, swapping your user agent to IE 8 is a lot easier than installing a copy of ancient browsers manually.

Whether for efficiency or because you don't own some of the devices needed to test your site, seeing how your site looks in a variety of browsers is easy using this method.

2. View Mobile Sites on Limited Connections

On a lot of sites, the mobile version offers a slimmed-down amount of content to reduce data usage for the mobile users. While we looked at how to view the full desktop site on a mobile browser, it's not as common to see desktop pages offer their mobile versions.

By changing your user agent to act as a mobile browser, you can force this change the next time you're using your phone as a mobile hotspot or working on a limited connection. Browsing mobile versions of pages means you only get the basics and aren't wasting data on multimedia or other large items.

3. Get Around Browser Restrictions

While not as common as it once was, sometimes you'll come across websites that tell you Firefox doesn't work with the page, or you must use Internet Explorer, or other similar warnings. If you know the site works fine in whatever browser you're using, you can swap your user agent to oblige the website without actually changing browsers.

Remember that changing your user agent doesn't actually modify the software you're running---it only changes what your browser reports to the website. Thus, this doesn't work if a website is truly IE-only because it uses archaic ActiveX controls or something similar. However, you're unlikely to come across such sites today.

4. Better OS Compatibility

Another uncommon reason for switching your user agent appears in reviews for user agent switching extensions. Some people explain that they use these services to get around sites that block entire operating systems.

While there's really no good reason for a site to block an entire OS, you could run into a page that complains about you using Linux. If this happens, you can just tell it you're using Internet Explorer and the site will think you're on Windows.

This could also come in handy if you're using an out-of-date operating system. Those still using an outdated browser on Windows XP will likely see warnings on most websites that the browser is no longer supported. As Windows 7 is left behind, this will also happen as major browsers drop support for it.

We recommend jumping ship to a modern operating system as soon as possible. But in the meantime, you can try swapping your user agent to squeeze a little more life out of your current system.

5. See a Different Perspective and Have Fun

Are the above options too boring for you? If so, you can still use agent switching just to have a bit of fun.

If you've used Windows all your life, you can jump around some sites and see if they look any different when using Mac or Linux. Or change your user agent to an ancient version of Internet Explorer, then see how many sites still support it. What kind of messages do they display, and how many block you from using the outdated browser?

Some browser-switching agents even allow you to pose as Googlebot, the robot Google uses to crawl and index the web. It could be interesting to see what content sites serve to the bots!

Seeing the web from a different perspective could be enjoyable once in a while, even if you can't get much practical use out of it.

Trick Websites With a New User Agent

We've looked at how to make your browser pretend it's something else by changing your user agent. While it's not something you'll probably need to do often, it comes in handy at times.

Keep in mind that the user agent isn't the only way to identify your browser, so sites may still be able to tell what you're actually using. Even though it is fun to trick websites, it's not a true measure of privacy.

For a deeper way to protect yourself online, you should start using a VPN if you don't already.

• Safari Browser
• Online Privacy

• Skip to main content
• Skip to search
• Skip to select language
• Sign up for free

Browser detection using the user agent

Serving different Web pages or services to different browsers is usually a bad idea. The Web is meant to be accessible to everyone, regardless of which browser or device they're using. There are ways to develop your website to progressively enhance itself based on the availability of features rather than by targeting specific browsers.

But browsers and standards are not perfect, and there are still some edge cases where detecting the browser is needed. Using the user agent to detect the browser looks simple, but doing it well is, in fact, a very hard problem. This document will guide you in doing this as correctly as possible.

Note: It's worth re-iterating: it's very rarely a good idea to use user agent sniffing. You can almost always find a better, more broadly compatible way to solve your problem!

Considerations before using browser detection

When considering using the user agent string to detect which browser is being used, your first step is to try to avoid it if possible. Start by trying to identify why you want to do it.

Look, or ask, in specialized forums: you're unlikely to be the first to hit this problem. Also, experts, or people with another point of view, can give you ideas for working around the bug. If the problem seems uncommon, it's worth checking if this bug has been reported to the browser vendor via their bug tracking system ( Mozilla ; WebKit ; Blink ; Opera ). Browser makers do pay attention to bug reports, and the analysis may hint about other workarounds for the bug.

Your site needs to use a specific Web feature that some browsers don't yet support, and you want to send those users to an older website with fewer features but that you know will work. This is the worst reason to use user agent detection because odds are eventually all the other browsers will catch up. In addition, it is not practical to test every one of the less popular browsers and test for those Web features. You should never do user agent sniffing. There is always the alternative of doing feature detection instead.

This is usually a bad practice, but there are some cases in which this is necessary. In these cases, you should first analyze your situation to be sure it's really necessary. Can you prevent it by adding some non-semantic <div> or <span> elements? The difficulty of successfully using user agent detection is worth a few disruptions to the purity of your HTML. Also, rethink your design: can you use progressive enhancement or fluid layouts to help remove the need to do this?

Avoiding user agent detection

If you want to avoid using user agent detection, you have options!

Feature detection is where you don't try to figure out which browser is rendering your page, but instead, you check to see if the specific feature you need is available. If it's not, you use a fallback. In those rare cases where behavior differs between browsers, instead of checking the user agent string, you should instead implement a test to detect how the browser implements the API and determine how to use it from that. An example of feature detection is as follows. In 2017, Chrome unflagged experimental lookbehind support in regular expressions , but no other browser supported it. So, you might have thought to do this:

The above code would have made several incorrect assumptions: First, it assumed that all user agent strings that include the substring "Chrome" are Chrome. UA strings are notoriously misleading. Then, it assumed that the lookbehind feature would always be available if the browser was Chrome. The agent might be an older version of Chrome, from before support was added, or (because the feature was experimental at the time) it could be a later version of Chrome that removed it. Most importantly, it assumed no other browsers would support the feature. Support could have been added to other browsers at any time, but this code would have continued choosing the inferior path.

Problems like these can be avoided by testing for support of the feature itself instead:

As the above code demonstrates, there is always a way to test browser support without user agent sniffing. There is never any reason to check the user agent string for this.

Lastly, the above code snippets bring about a critical issue with cross-browser coding that must always be taken into account. Don't unintentionally use the API you are testing for in unsupported browsers. This may sound obvious and simple, but sometimes it is not. For example, in the above code snippets, using lookbehind in short-regexp notation (for example, /reg/igm) will cause a parser error in unsupported browsers. Thus, in the above example, you would use new RegExp("(?<=look_behind_stuff)"); instead of /(?<=look_behind_stuff)/ , even in the lookbehind supported section of your code.

This design technique involves developing your website in 'layers', using a bottom-up approach, starting with a simpler layer and improving the capabilities of the site in successive layers, each using more features.

This is a top-down approach in which you build the best possible site using all the features you want, then tweak it to make it work on older browsers. This can be harder to do, and less effective, than progressive enhancement, but may be useful in some cases.

Arguably the most common use and misuse of user agent sniffing is to detect if the device is a mobile device. However, people too often overlook what they are really after. People use user agent sniffing to detect if the users' device is touch-friendly and has a small screen so they can optimize their website accordingly. While user agent sniffing can sometimes detect these, not all devices are the same: some mobile devices have big screen sizes, some desktops have a small touchscreen, some people use smart TV's which are an entirely different ballgame altogether, and some people can dynamically change the width and height of their screen by flipping their tablet on its side! So, user agent sniffing is definitely not the way to go. Thankfully, there are much better alternatives. Use Navigator.maxTouchPoints to detect if the user's device has a touchscreen. Then, default back to checking the user agent screen only if (!("maxTouchPoints" in navigator)) { /*Code here*/} . Using this information of whether the device has a touchscreen, do not change the entire layout of the website just for touch devices: you will only create more work and maintenance for yourself. Rather, add in touch conveniences such as bigger, more easily clickable buttons (you can do this using CSS by increasing the font size). Here is an example of code that increases the padding of #exampleButton to 1em on mobile devices.

As for the screen size, use window.innerWidth and window.addEventListener("resize", () => { /*refresh screen size dependent things*/ }). What you want to do for screen size is not slash off information on smaller screens. That will only annoy people because it will force them to use the desktop version. Rather, try to have fewer columns of information in a longer page on smaller screens while having more columns with a shorter page on larger screen sizes. This effect can be easily achieved using CSS flexboxes , sometimes with floats as a partial fallback.

Also try to move less relevant/important information down to the bottom and group the page's content together meaningfully. Although it is off-topic, perhaps the following detailed example might give you insights and ideas that persuade you to forgo user agent sniffing. Let us imagine a page composed of boxes of information; each box is about a different feline breed or canine breed. Each box has an image, an overview, and a historical fun fact. The pictures are kept to a maximum reasonable size even on large screens. For the purposes of grouping the content meaningfully, all the cat boxes are separated from all the dog boxes such that the cat and dog boxes are not intermixed together. On a large screen, it saves space to have multiple columns to reduce the space wasted to the left and to the right of the pictures. The boxes can be separated into multiple columns via two equally fair method. From this point on, we shall assume that all the dog boxes are at the top of the source code, that all the cat boxes are at the bottom of the source code, and that all these boxes have the same parent element. There a single instance of a dog box immediately above a cat box, of course. The first method uses horizontal Flexboxes to group the content such that when the page is displayed to the end user, all the dogs boxes are at the top of the page and all the cat boxes are lower on the page. The second method uses a Column layout and resents all the dogs to the left and all the cats to the right. Only in this particular scenario, it is appropriate to provide no fallback for the flexboxes/multicolumns, resulting in a single column of very wide boxes on old browsers. Also consider the following. If more people visit the webpage to see the cats, then it might be a good idea to put all the cats higher in the source code than the dogs so that more people can find what they are looking for faster on smaller screens where the content collapses down to one column.

Next, always make your code dynamic. The user can flip their mobile device on its side, changing the width and height of the page. Or, there might be some weird flip-phone-like device thing in the future where flipping it out extends the screen. Do not be the developer having a headache over how to deal with the flip-phone-like device thing. Never be satisfied with your webpage until you can open up the dev tools side panel and resize the screen while the webpage looks smooth, fluid, and dynamically resized. The simplest way to do this is to separate all the code that moves content around based on screen size to a single function that is called when the page is loaded and at each resize event thereafter. If there is a lot calculated by this layout function before it determines the new layout of the page, then consider debouncing the event listener such that it is not called as often. Also note that there is a huge difference between the media queries (max-width: 25em) , not all and (min-width: 25em) , and (max-width: 24.99em) : (max-width: 25em) excludes (max-width: 25em) , whereas not all and (min-width: 25em) includes (max-width: 25em) . (max-width: 24.99em) is a poor man's version of not all and (min-width: 25em) : do not use (max-width: 24.99em) because the layout might break on very high font sizes on very high definition devices in the future. Always be very deliberate about choosing the right media query and choosing the right >=, <=, >, or < in any corresponding JavaScript because it is very easy to get these mixed up, resulting in the website looking wonky right at the screen size where the layout changes. Thus, thoroughly test the website at the exact widths/heights where layout changes occur to ensure that the layout changes occur properly.

Making the best of user agent sniffing

After reviewing all of the above better alternatives to user agent sniffing, there are still some potential cases where user agent sniffing is appropriate and justified.

One such case is using user agent sniffing as a fallback when detecting if the device has a touch screen. See the Mobile Device Detection section for more information.

Another such case is for fixing bugs in browsers that do not automatically update. Webkit (on iOS) is a perfect example. Apple forces all of the browsers on IOS to use Webkit internally, thus the user has no way to get a better more updated browser on older devices. Most bugs can be detected, but some bugs take more effort to detect than others. In such cases, it might be beneficial to use user agent sniffing to save on performance. For example, Webkit 6 has a bug whereby when the device orientation changes, the browser might not fire MediaQueryList listeners when it should. To overcome this bug, observe the code below.

Which part of the user agent contains the information you are looking for?

As there is no uniformity of the different part of the user agent string, this is the tricky part.

Browser Name and version

When people say they want "browser detection", often they actually want "rendering engine detection". Do you actually want to detect Firefox, as opposed to SeaMonkey, or Chrome as opposed to Chromium? Or do you actually want to see if the browser is using the Gecko or the WebKit rendering engine? If this is what you need, see further down the page.

Most browsers set the name and version in the format BrowserName/VersionNumber . But as the name is not the only information in a user agent string that is in that format, you can not discover the name of the browser, you can only check if the name you are looking for exists. But note that some browsers are lying: Chrome for example reports both as Chrome and Safari. So to detect Safari you have to check for the Safari string and the absence of the Chrome string, Chromium often reports itself as Chrome too or Seamonkey sometimes reports itself as Firefox.

Also, pay attention not to use a simple regular expression on the BrowserName, user agents also contain strings outside the Keyword/Value syntax. Safari & Chrome contain the string 'like Gecko', for instance.

[1] Safari gives two version numbers: one technical in the Safari/xyz token, and one user-friendly in a Version/xyz token.

Of course, there is absolutely no guarantee that another browser will not hijack some of these things (like Chrome hijacked the Safari string in the past). That's why browser detection using the user agent string is unreliable and should be done only with the check of the version number (hijacking of past versions is less likely).

Rendering engine

As seen earlier, in most cases, looking for the rendering engine is a better way to go. This will help to not exclude lesser known browsers. Browsers sharing a common rendering engine will display a page in the same way: it is often a fair assumption that what will work in one will work in the other.

There are three active major rendering engines: Blink, Gecko, and WebKit. As sniffing the rendering engines names is common, a lot of user agents added other rendering names to trigger detection. It is therefore important to pay attention not to trigger false-positives when detecting the rendering engine.

Rendering engine version

Most rendering engines put the version number in the RenderingEngine/VersionNumber token, with the notable exception of Gecko. Gecko puts the Gecko version number in the comment part of the User Agent after the rv: string. From Gecko 14 for the mobile version and Gecko 17 for the desktop version, it also puts this value in the Gecko/version token (previous version put there the build date, then a fixed date called the GeckoTrail).

The Operating System is given in most User Agent strings (although not web-focused platforms like Firefox OS), but the format varies a lot. It is a fixed string between two semicolons, in the comment part of the User Agent. These strings are specific for each browser. They indicate the OS, but also often its version and information on the relying hardware (32 or 64 bits, Intel/PPC for Mac, or x86/ARM CPU architecture for Windows PCs).

Like in all cases, these strings may change in the future, one should use them only in conjunction with the detection of already released browsers. A technological survey must be in place to adapt the script when new browser versions are coming out.

Mobile, Tablet or Desktop

The most common reason to perform user agent sniffing is to determine which type of device the browser runs on. The goal is to serve different HTML to different device types.

• Never assume that a browser or a rendering engine only runs on one type of device. Especially don't make different defaults for different browsers or rendering engines.
• Never use the OS token to define if a browser is on mobile, tablet or desktop. The OS may run on more than one type of device (for example, Android runs on tablets as well as phones).

The following table summarizes the way common browser vendors indicate that their browsers are running on a mobile device:

In summary, we recommend looking for the string Mobi anywhere in the User Agent to detect a mobile device.

Note: If the device is large enough that it's not marked with Mobi , you should serve your desktop site (which, as a best practice, should support touch input anyway, as more desktop machines are appearing with touchscreens).

Parse User Agents

Parse User Agent

Explore User Agents

We have a huge collection of over 410 million different user agents. Look around to find user agents for which ever browser, operating system, device, software type or layout engine you need. If you need to decode a user agent, use the User Agent Parser or the Browser Detection API .

Detect Windows 11

• Facebook App (8,591,685)
• Chrome (5,019,455)
• Instagram (4,943,685)
• Android WebView (4,007,680)
• TikTok (665,198)
• Opera (636,879)
• Google News (540,099)
• Snapchat (515,196)
• WeChat (254,295)

Browse all Software Names

Operating Systems:

• Android (18,729,759)
• iOS (7,643,072)
• Windows (308,010)
• Linux (69,946)
• macOS (60,589)
• Mac OS X (44,074)
• Fire OS (14,018)
• Symbian (6,742)
• Chrome OS (2,988)

Browse all Operating Systems

Operating Platforms:

• Apple iPhone (1,630,389)
• Google Pixel 2 (881,858)
• LG Nexus 5 (876,785)
• Samsung SM-G900P (873,700)
• Motorola Moto G (786,253)
• Redmi (391,593)
• Apple iPhone 11 (390,418)
• Apple iPhone 13 (302,610)
• Apple iPhone 12 (287,782)

Browse all Operating Platforms

Software Types:

• In-App Browser (19,860,594)
• Web Browser (6,979,891)
• Crawler (131,265)
• Application (16,397)
• Site Monitor (12,069)
• Analyser (2,555)
• Bot (1,806)
• Media Player (1,612)
• Software Library (727)

Browse all Software Types

Hardware Types:

• Phone (14,997,455)
• Mobile (9,868,413)
• Tablet (1,516,726)
• Computer (477,160)
• Server (148,958)
• TV (15,163)
• E-Book Reader (14,050)
• Music Player (4,366)

Browse all Hardware Types

Layout Engines:

• WebKit (17,657,003)
• Blink (8,733,051)
• EdgeHTML (170,014)
• Gecko (74,046)
• NetFront (53,259)
• Trident (20,457)
• Presto (1,894)
• Goanna (370)

Browse all Layout Engine Names

Welcome to The User Agent Knowledgebase

We've been decoding user agents for more than 13 years and we've seen it all - the good, the bad and the downright weird! This website is a collection of resources dedicated to understanding and working with user agents, including the new proposal which may end up eliminating user agents: Client Hints .

As well as this, we've also got resources (such as our Frontend Library ) dedicated to detecting frontend web browser features and settings, so that you can understand what technology your website visitors are using and help solve their technical problems. It's the same technology we use on whatismybrowser.com .

You can use our user agent parser form to paste in a user agent and decipher it. If you want to automate sending lots of user agents, then look at our Browser Detection API - not only will it let you easily decode millions of user agents, it will tell you if your visitor's web browsers are up to date or if someone is trying to send you a dangerous or weird user agent . Our API has lots of helpful features and is trusted by thousands of companies - check it out now .

Learn about user agents

• Browse millions of user agents

Use the API

• Browser Detection API
• Check if your visitor's web browser is up to date
• Web Browser Version Numbers API
• Search the user agent database
• API use cases
• API documentation

Browser Detection

• Parse a user agent
• Use the API to automate Browser Detection.
• What does a user agent fragment mean?
• Software & Platforms we detect

• Skip to content
• Skip to search
• Skip to footer

Cisco Secure Firewall Management Center Device Configuration Guide, 7.6

Bias-free language.

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

• Device Management
• Device Management Using Templates
• Change Management
• Configuration Deployment
• Transparent or Routed Firewall Mode
• Logical Devices on the Firepower 4100/9300
• Multi-Instance Mode for the Secure Firewall 3100/4200
• High Availability
• Clustering for the Secure Firewall 3100/4200
• Clustering for Threat Defense Virtual in a Private Cloud
• Clustering for Threat Defense Virtual in a Public Cloud
• Clustering for the Firepower 4100/9300
• Interface Overview
• Regular Firewall Interfaces
• Inline Sets and Passive Interfaces
• DHCP and DDNS
• SNMP for the Firepower 1000
• Quality of Service
• Platform Settings
• Network Address Translation
• Alarms for the Cisco ISA 3000
• Static and Default Routes
• Virtual Routers
• Bidirectional Forwarding Detection Routing
• Policy Based Routing
• Object Management
• Certificates
• VPN Overview
• Site-to-Site VPNs
• Remote Access VPN
• Dynamic Access Policies
• VPN Monitoring and Troubleshooting
• Access Control Overview
• Access Control Policies
• Access Control Rules
• Cisco Secure Dynamic Attributes Connector
• URL Filtering
• Security Intelligence
• DNS Policies
• Prefiltering and Prefilter Policies
• Service Policies
• Threat Detection
• Intelligent Application Bypass
• Content Restriction
• Zero Trust Access
• SD-WAN Capabilities
• Network Analysis and Intrusion Policies Overview
• Getting Started with Intrusion Policies
• Tuning Intrusion Policies Using Rules
• Custom Intrusion Rules
• Layers in Intrusion and Network Analysis Policies
• Tailoring Intrusion Protection to Your Network Assets
• Sensitive Data Detection
• Global Limit for Intrusion Event Logging
• Intrusion Prevention Performance Tuning
• Network Malware Protection and File Policies
• Traffic Decryption Overview
• Decryption Policies
• Decryption Rules
• User Identity Overview

User Control With The Passive Identity Agent

• User Control with ISE/ISE-PIC
• User Control with Captive Portal
• User Control with Remote Access VPN
• User Control with TS Agent
• User Identity Policies
• Network Discovery Overview
• Host Identity Sources
• Application Detection
• Network Discovery Policies
• FlexConfig Policies
• Advanced Access Control Settings for Network Analysis and Intrusion Policies
• Getting Started with Network Analysis Policies
• Application Layer Preprocessors
• SCADA Preprocessors
• Transport and Network Layer Preprocessors
• Specific Threat Detection
• Adaptive Profiles
• Secure Firewall Threat Intelligence Director

Chapter: User Control With The Passive Identity Agent

The passive identity agent identity source, simple passive identity agent deployment, single passive identity agent monitoring multiple domain controllers.

• Multiple Passive Identity Agents Monitoring Multiple Domain Controllers

Passive Identity Agent Primary/Secondary Agent Deployments

How to create a passive identity agent identity source, create a microsoft ad realm, create a standalone passive identity agent identity source, create a primary or secondary passive identity agent identity source, about passive identity agent roles, create a secure firewall management center user for the passive identity agent, troubleshoot the passive identity agent, install the passive identity agent software, uninstall the passive identity agent software, monitor the passive identity agent.

• Edit Passive Identity Agents

Delete a Standalone Passive Identity Agent

• Delete Primary and Secondary Passive Identity Agents

Security Requirements for the Passive Identity Agent

Internet access requirements for the passive identity agent.

The following topics discuss how to configure and use the passive identity agent .

The passive identity agent identity source sends session data from Microsoft Active Directory (AD) to the Secure Firewall Management Center . All you need is a supported Microsoft AD setup as discussed in About Realms and Realm Sequences .

Passive identity agent roles

The passive identity agent supports the following roles:

Standalone: A passive identity agent that is not part of a redundant pair. A standalone agent can download users and groups from multiple Active Directory servers and domain controllers, provided the software is installed on all of them.

Primary: (Primary agent in a redundant pair.) Can be installed on a Microsoft AD domain controller, directory server, or any network client.

Handles all communication with the Secure Firewall Management Center unless it stops communicating, in which case communication is handled by secondary agents.

Secondary: (Secondary, or backup, agent in a redundant pair.) Can be installed on a Microsoft AD domain controller, directory server, or any network client.

Monitors the health of the primary agent and takes over if the primary agent stops communicating with the Secure Firewall Management Center .

Passive identity agent system requirements

The passive identity agent requires the following:

If you install it on a Windows Active Directory server, the server must run Active Directory 2008 or later.

If you install it on a Windows client attached to the domain, the client must run Windows 8 or later.

Secure Firewall Management Center must run 7.6 or later.

Any Secure Firewall Threat Defense managed by the Secure Firewall Management Center must run 7.6 or later.

Passive identity agent limitations

The passive identity agent the following limitations:

Up to 10 agents simultaneously

One passive identity agent identity source can monitor up to 50 AD directories

Up to 300,000 concurrent user sessions

Deploy the passive identity agent

For information about deployment options, see Deploy the Passive Identity Agent .

Deploy the Passive Identity Agent

You can install the Passive Identity Agent software on any machine that is part of a Microsoft Active Directory (AD) domain you want to use for user awareness and control. In other words, you can install it on any of the following:

The Microsoft Active Directory server

A domain controller

A client connected to the network that is neither the directory server nor a domain controller

Any particular passive identity agent can monitor one or several Active Directory domains.

The machine on which the passive identity agent must communicate with the Secure Firewall Management Center using the TLS/SSL protocol. For more information, see Internet Access Requirements for the Passive Identity Agent .

Types of agents

You can configure the following types of agents on the Microsoft AD directory server, domain controller, or on any client connected to the domain:

Standalone agent: One agent that can monitor one or several AD domains.

Primary agent and secondary agent: To provide redundancy, you can install a primary and secondary agent on different machines. The primary is responsible for communicating with the Secure Firewall Management Center but if communication fails, the secondary agent takes over.

See one of the following topics for more information.

The following diagram shows the simplest passive identity agent deployment.

In the preceding example, a standalone passive identity agent is installed on the AD domain controller. Users log in and out of the AD domain and the agent sends user name and IP address information to the Secure Firewall Management Center . As users access the network, access control and identity policies deployed to the Secure Firewall Threat Defense determine whether or not, and how, access is allowed.

A passive identity agent can be installed on the AD domain controller, directory server, or on any client connected to the domain you wish to monitor.

The following diagram shows a standalone passive identity agent that monitors several AD domain controllers.

In the preceding diagram, the standalone passive identity agent is installed on a client attached to the AD domain (or on the domain controller itself). Users log in to any domain controller and the agent sends user and IP address information to the Secure Firewall Management Center . As users access the network, access control and identity policies deployed to the Secure Firewall Threat Defense determine whether or not, and how, access is allowed.

Multiple Passive Identity Agent s Monitoring Multiple Domain Controllers

The following figure shows standalone monitoring multiple AD domain controllers:

In AD domain 1, a standalone passive identity agent installed on a machine attached to AD domain controller 1 sends user and group data to the Secure Firewall Management Center .

In AD domain 2, standalone agents installed on AD domain controllers 1 and 2 send user and group data to the Secure Firewall Management Center .

The preceding figure shows three passive identity agent s, each configured as a standalone. To do this:

Create two Microsoft AD realms: one for each AD domain.

See Create an LDAP Realm or an Active Directory Realm and Realm Directory .

For AD domain 2, create two directories, one for each domain controller.

Install the Passive Identity Agent software on a client that can log in to the domain.

Configure each passive identity agent individually to communicate with the Secure Firewall Management Center on which you configure the passive identity agent source.

See Install the Passive Identity Agent Software .

Create the Passive Identity Agent identity source.

See Create a Primary or Secondary Passive Identity Agent Identity Source .

To provide redundancy and to avoid a single point of failure, you can configure primary and secondary passive identity agent s in any of the ways shown in this topic.

Single AD domain controller with primary and secondary agents

The following figure shows how to set up primary and secondary passive identity agent s on one AD domain controller. If the primary agent fails, the secondary takes over.

To set this up:

Create a Microsoft AD realm that has one directory for the domain controller.

Install the passive identity agent software on any two network machines connected to the domain controller.

Create the identity source.

Multiple AD domain controllers, primary and secondary agents

The preceding figure shows how to configure primary and secondary agents to monitor three AD domain controllers. If the primary agent fails, the secondary agent takes over.

Install the passive identity agent software on any machine connected to the domain controller.

The following provides high-level tasks required to configure the passive identity agent identity source in the Secure Firewall Management Center and to deploy agent software to your Microsoft Active Directory (AD) servers.

What to do next

Create an LDAP Realm or an Active Directory Realm and Realm Directory .

Configure the Passive Identity Agent

The following topics discuss how to configure the passive identity agent .

The passive identity agent requires you to create a Microsoft AD realm and directories as discussed in Create an LDAP Realm or an Active Directory Realm and Realm Directory .

Create a Passive Identity Agent Identity Source

This task discusses how to create a passive identity agent that sends user session activity to the Secure Firewall Management Center .

Before you begin

Complete the following:

Review passive identity agent roles as discussed in About Passive Identity Agent Roles .

Create a Microsoft AD realm as discussed in Create an LDAP Realm or an Active Directory Realm and Realm Directory .

Step 7

Continue with:

Complete the tasks discussed in Create a Passive Identity Agent Identity Source .

The following figure shows an example of a standalone passive identity agent identity source.

Step 2

In the Configure Agent dialog box, click Save .

Step 3

In the top right corner of the page, click Save .

The following figure shows an example.

See Create a Secure Firewall Management Center User for the Passive Identity Agent

The following task continues from Create a Passive Identity Agent Identity Source .

The following figure shows an example of a primary agent:

The following figure shows an example of a secondary agent:

See Install the Passive Identity Agent Software

The passive identity agent has the following roles:

This task discusses how to create a Secure Firewall Management Center user with sufficient permissions to communicate with the passive identity agent .

Step 6

Click Save .

Install the Passive Identity Agent Software .

This topic discusses how you can troubleshoot the passive identity agent software on your Windows AD domain controller or directory server.

(Optional.) Set the log level

By default, the passive identity agent logs at the INFO level. To optionally change the log level, open C:\Program Files\Program Files (x86)\Cisco\Cisco Passive Identity Agent\CiscoPassiveIdentityAgentService.exe.config in a text editor, save the file, and restart the Cisco Passive Identity Agent service.

View log files

Passive identity agent log files are stored in plain text format in the agent's installation directory: C:\Program Files\Program Files (x86)\Cisco\Cisco Passive Identity Agent .

Use Notepad or another text editor to view these files. Log files rotate after reaching 10MB in size.

Use the Microsoft Active Directory event viewer

In the event you are not seeing user sessions in the Secure Firewall Management Center , you can look on your Microsoft Active Directory server's event viewers for the following events:

These events indicate users logged in. If you find the event viewer

This task discusses how to install the passive identity agent software. For a simple installation, you can install it on your Microsoft Active Directory (AD) domain controller.

Make sure your systems meet the following requirements:

Step 9

Click the name of the agent that is displayed.

Step 10

If you have a high availability pair, click I have Secondary FMC and enter the secondary's IP address or fully qualified host name and its listen port.

Step 11

Click Test .

Step 12

Only if the test succeeds, click Save .

This task discusses how to uninstall the passive identity agent software from your Microsoft AD servers.

The passive identity agent indicates whether or not it can communicate with the Secure Firewall Management Center and other agents if it's configured as primary-secondary. You can view the status at Integration > Other Integrations > Identity Sources .

Deployments

A standalone passive identity agent is represented as follows.

A primary-secondary pair is represented as follows.

The following table explains the meaning of the indicators.

Status indicators and colors

The passive identity agent indicates status using lines (that indicate whether communication with the Secure Firewall Management Center is active or standby) and colors (that indicate whether or not communication is successful).

The following table shows the meanings of lines and colors:

Manage the Passive Identity Agent

The following topics discuss how to edit or delete passive identity agent s you previously configured on the Secure Firewall Management Center .

Edit Passive Identity Agent s

This task discusses how to edit passive identity agent s you previously configured in the Secure Firewall Management Center .

This task discusses how to delete a standalone passive identity agent .

Delete Primary and Secondary Passive Identity Agent s

This task discusses how to delete primary and secondary passive identity agent s. You must delete a secondary agent before you can delete a primary agent.

To safeguard the system, you should install the passive identity agent on a protected internal network. Although the passive identity agent is configured to have only the necessary services and ports available, you must make sure that attacks cannot reach it.

If the passive identity agent and the management center reside on the same network, you can connect the management center to the same protected internal network as the passive identity agent .

Regardless of how you deploy your appliances, inter-system communication is encrypted. However, you must still take steps to ensure that communications between appliances cannot be interrupted, blocked, or tampered with; for example, with a distributed denial of service (DDoS) or man-in-the-middle attack.

By default, the passive identity agent is configured to communicate with the Firepower System over the internet using HTTPS on port 443/tcp (HTTPS). If you do not want the passive identity agent to have direct access to the internet, you can configure a proxy server.

The following information informs you of the ports the passive identity agent use to communicate with each other, with the management center , and with Microsoft Active Directory.

Was this Document Helpful?

Contact Cisco

• (Requires a Cisco Service Contract )