safari 605.1.15

• Mobile Site
• Staff Directory
• Advertise with Ars

Filter by topic

• Biz & IT
• Gaming & Culture

Front page layout

rapid security recall —

Apple releases, quickly pulls rapid security response update for 0-day webkit bug, update for ios 16, macos ventura can be uninstalled if you're having problems..

Andrew Cunningham - Jul 11, 2023 1:52 pm UTC

Further Reading

Yesterday, Apple published a new Rapid Security Response update for iOS 16, iPadOS 16, and macOS Ventura to patch yet another actively exploited WebKit code execution bug. But shortly after installation, users began having issues accessing certain websites, and Apple has apparently pulled the update to fix the problem.

According to MacRumors , affected sites include Facebook, Instagram, WhatsApp, and Zoom, which began showing warning messages about not being supported following the update.

Luckily for anyone who has installed it, Rapid Security Response updates can be removed just as quickly as they were installed; on iOS, navigate to the About page in the Settings app, tap on your iOS version, and then tap “Remove Security Response.”

The benefit of Rapid Security Response updates is that they’re small in size and quick to install. The updates Apple has released so far have required a restart on my devices, but total downtime was much less than it was for a typical software update. This is because Apple has stored many Safari and WebKit components outside of the main Signed System Volume (SSV) , a tamper-proof read-only volume for most system files that must be mounted separately, patched, and re-sealed every time most system updates are installed.

The downside of Rapid Security Response updates is that they may not be tested as thoroughly as some system updates; Apple is currently on its fifth developer betas of iOS 16.6 and macOS 13.5, and both updates have been in testing since mid-May. Though you’ll typically want to install them quickly because the bugs they’re patching tend to be severe, you may occasionally run into problems.

WebKit vulnerabilities in iOS tend to be especially severe since any app that wants to render web content needs to use a webview powered by the built-in WebKit engine used by Safari. This includes third-party browsers like Google Chrome, Mozilla Firefox, and Microsoft Edge, which can’t use their own native rendering engines on iOS or iPadOS the way they can on macOS, Windows, or other platforms. Apple has long maintained that this restriction improves security on the platform .

Apple announced the Rapid Security Response feature as part of iOS 16 and macOS Ventura last June but didn't actually start using the feature publicly until a couple of months ago . When contacted for comment, an Apple spokesperson pointed us to this support document , which says that new iOS/iPadOS 16.5.1 (b) and macOS 13.4.1 (b) Rapid Security Response updates will be available to resolve the issues soon.

reader comments

Promoted comments.

Channel Ars Technica

• Home New Posts Forum List Trending New Threads New Media Spy
• WikiPost Latest summaries Watched WikiPosts
• Support FAQ and Rules Contact Us

Still showing as 10.15.

• Thread starter wellander1
• Start date Jun 19, 2021
• Sort by reaction score
• macOS Monterey (12)

Contributor

• Jun 19, 2021

In Monterey beta 1 the User agent string in in Safari on my M1 Mac shows this Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.0 Safari/605.1.15 Will this ever be fixed?  

No, that's an intentional decision, it's not a bug.  

macrumors G5

216593 – [macos] limit reported macos release to 10.15 series.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

internet Explorer user agent

I want to use the Internet Explorer user agent from the Develop tab to use a specific website. However on my version of Safari (13.0.3) none of the IE versions are shown - only Edge. I have tried searching for the user agent strings but cannot find them.

Can anyone help how to install those user agents into Safari ?

MacBook Pro 13", macOS 10.14

Posted on Nov 14, 2019 2:37 PM

Loading page content

Page content loaded

Nov 15, 2019 4:07 AM in response to dominic23

We have been told Edge will not work on this website - IE only. I would put a string into the other filed if I could find one for IE. I have searched the Web and find all sorts for Chrome etc but I cannot find a string to paste for IE of any version to run on Safari 13

Nov 15, 2019 10:27 AM in response to Satcom_Eng

I couldn't find Safari 13 specific IE user agent string either.

If Apple don't provide one, it is going to be tough to get IE user agent string working.

Do you have clone backup with previous version of Safari installed?

Nov 18, 2019 6:10 AM in response to Satcom_Eng

im having the exact same problem . there was a IE extension that used to be free on chrome as well and now they want to charge u for it . I usually use the developer tab but my computer auto updated itself to 13.0.3 and not IE is gone ...

Nov 22, 2019 9:12 AM in response to Satcom_Eng

There has not been an Internet Explorer version for Mac in 16 years. There is no user Agent String that would Identify a current Internet Explorer version on a Mac.

But not sure why you need that. If you just want to trick the website into thinking you are using Internet Explorer, then any current version of Internet Explorer you would be using would have to be on Windows, so those strings should work.

Jan 12, 2020 11:44 AM in response to Da-Kang

HI Da-Kang - I was wondering what it was that you found that WORKS!!

I am too trying to "use" IE and EDGE does not work - Please advise what did it for you!

Best regards

PS I see the DEFAULT string showing on my MAC under Develop/User Agent/other is:

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

Is this for Internet explorer?

Jan 30, 2020 3:05 PM in response to aofrombeaconsfield

This will work I have a website that only will run on ie 8-11 this following string run the website when used in the agent string.

Unfortunately, you have to do this step each time you want to use the in question website..

Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0)

Apr 6, 2020 6:51 AM in response to felippemagoo

felippemagoo wrote:

I think these user agents don’t work for Mac.

They do. User Agents are platform agnostic, they'll work anywhere. On Mac, on Pc, even on Linux.

As I said before, there are no user agents that will identify your browser as Internet Explorer on Mac because there has been no Internet Explorer on Mac for 16 years. So no user agent either.

If the website is expecting Internet Explorer, then its expecting Internet Explorer on Windows which is what these user agents would make it think you have.

May 9, 2020 5:16 AM in response to Phil0124

I have the same problem now and good thing I've stumbled in this discussion. I have tried the link you provided and used all the strings but none is working too. Not sure what needs to be done next. :-(

May 9, 2020 8:52 AM in response to ProvinceBoy

Define “not working”. What does the website do when using the user agent strings?

There’s also the possibility, the website you are trying to access is not using the user agent to identify the browser. It may be looking for support of a particular Javascript function, or some other mechanism of identifying the browser.

May 10, 2020 6:34 AM in response to Kurt Lang

I guess I was able to figure this one out on how to make it work. At least from what I have experienced. Downloaded chrome for Mac, then added an ie extension.

From that ie extension's options and settings, I have chosen IE 10 Forced Standard Mode.

Nov 22, 2019 2:38 PM in response to VikingOSX

i take it back Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0) this works perfectly

thanks again ...

Nov 15, 2019 3:27 AM in response to Satcom_Eng

• Have you tried Microsoft Edge as the User Agent?
• Try 'Other" at the bottom of the pop-up, enter the user agent string and "OK".

Nov 18, 2019 6:44 AM in response to Satcom_Eng

Latest user agents for Internet Explorer .

Nov 22, 2019 9:00 AM in response to VikingOSX

Thanks for the link but they all seem to be for Windows machines. I need the string for IE on OS X 13 ? Unless I am reading those incorrectly.

it works !!!!!

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.

Chromium Blog

Changing the chrome on ios user agent for request desktop site.

• 10th birthday 4
• abusive ads 1
• abusive notifications 2
• accessibility 3
• ad blockers 1
• ad blocking 2
• advanced capabilities 1
• anti abuse 1
• anti-deception 1
• background periodic sync 1
• benchmarks 1
• better ads standards 1
• browser interoperability 1
• capabilities 6
• capable web 1
• chrome 81 1
• chrome 83 2
• chrome 84 2
• chrome ads 1
• chrome apps 5
• Chrome dev 1
• chrome dev summit 1
• chrome dev summit 2018 1
• chrome dev summit 2019 1
• chrome developer 1
• Chrome Developer Center 1
• chrome developer summit 1
• chrome devtools 1
• Chrome extension 1
• chrome extensions 3
• Chrome Frame 1
• Chrome lite 1
• Chrome on Android 2
• chrome on ios 1
• Chrome on Mac 1
• Chrome OS 1
• chrome privacy 4
• chrome releases 1
• chrome security 8
• chrome web store 32
• chromedevtools 1
• chromeframe 3
• chromeos.dev 1
• cloud print 1
• coalition 1
• coalition for better ads 1
• contact picker 1
• content indexing 1
• core web vitals 2
• cumulative layout shift 1
• custom tabs 1
• dashboard 1
• Data Saver 3
• Data saver desktop extension 1
• deceptive installation 1
• declarative net request api 1
• developer dashboard 1
• Developer Program Policy 2
• developer website 1
• devtools 13
• digital event 1
• discoverability 1
• DNS-over-HTTPS 4
• emscriptem 1
• enterprise 1
• extensions 27
• Fast badging 1
• faster web 1
• field data 1
• first input delay 1
• form controls 1
• frameworks 1
• google earth 1
• google event 1
• google io 2019 1
• google web developer 1
• googlechrome 12
• harmful ads 1
• incognito 1
• insecure forms 1
• intent to explain 1
• ios Chrome 1
• issue tracker 3
• javascript 5
• labelling 1
• largest contentful paint 1
• lazy-loading 1
• lighthouse 2
• Lite Mode 2
• Lite pages 1
• loading interventions 1
• loading optimizations 1
• lock icon 1
• long-tail 1
• manifest v3 2
• microsoft edge 1
• mixed forms 1
• native client 8
• native file system 1
• New Features 5
• notifications 1
• origin trials 2
• pagespeed insights 1
• pagespeedinsights 1
• passwords 1
• payment handler 1
• payment request 1
• performance 20
• performance tools 1
• permission UI 1
• permissions 1
• play store 1
• prefetching 1
• privacy sandbox 4
• private prefetch proxy 1
• profile guided optimization 1
• progressive web apps 2
• Project Strobe 1
• protection 1
• quieter permissions 1
• root program 1
• safe browsing 2
• Secure DNS 2
• security 36
• site isolation 1
• slow loading 1
• sms receiver 1
• spam policy 1
• store listing 1
• subscription pages 1
• suspicious site reporter extension 1
• the fast and the curious 21
• transparency 1
• trusted web activities 1
• user agent string 1
• user data policy 1
• web assembly 2
• web developers 1
• web intents 1
• web packaging 1
• web payments 1
• web platform 1
• web request api 1
• web vitals 1
• web.dev live 1
• webassembly 1
• webmaster 1
• websockets 5
• webtiming 1
• writable-files 1
• yerba beuna center for the arts 1

• Latest iOS 17 user agents:

About Applebot

Learn about Applebot, the web crawler for Apple.

Applebot is the web crawler for Apple. Products like Siri and Spotlight Suggestions use Applebot.

Identifying Applebot

Traffic coming from Applebot is identified by its user agent, and reverse DNS shows it in the *.applebot.apple.com domain, originating from the 17.0.0.0 net block.

Verifying that traffic is from Applebot

In macOS, the host command can be used to determine if an IP address is part of Applebot. These examples show the host command and its result:

The host command can also be used to verify that the DNS points to the same IP address:

Verifying Applebot user agent

The user-agent string contains ”Applebot” and other information. This is the format: 

Examples for desktop:

Examples for mobile:

Customizing robot.txt rules

Applebot respects standard robots.txt directives that are targeted at Applebot. In this example, Applebot doesn't try to crawl documents that are under /private/ or /not-allowed/:

If robots instructions don't mention Applebot but do mention Googlebot, the Apple robot will follow Googlebot instructions.

Rendering and robot rules

Applebot may render the content of your website within a browser. If javascript, CSS, and other resources are blocked via robots.txt, it may not be able to render the content properly. This includes XHR, JS, and CSS that the page might require.

In order for Applebot to index the best content for the page, make sure that everything needed for a user to render the page is available to Applebot. Alternatively, make sure that the website renders cleanly, even if all of the resources are not available. This is often referred to as graceful degradation.

Customizing indexing rules for Applebot

Applebot supports robots meta tags in HTML documents. To specify robots rules in meta tags, put the tags in the <head> section of the document, like this:

Applebot also supports the following directives:

• noindex: Applebot won't index this page, and it won't appear in Spotlight or Siri Suggestions.
• nosnippet: Applebot won't generate a description or web answer for the page. Any suggestions to visit this URL will only include the page's title.
• nofollow: Applebot won't follow any links on the page.
• none: Applebot won't index, snippet, or follow links on the page, as described above.
• all: Applebot provides the document for suggestions and snippets the contents so that a short description of the page can appear next to a representative image. Applebot may follow links on the page to provide more suggestions.

To put multiple directives in a single meta tag, use a comma-separated list or multiple meta tags. Examples:

About search rankings

Apple Search may take the following into account when ranking web search results:

• Aggregated user engagement with search results
• Relevancy and matching of search terms to webpage topics and content
• Number and quality of links from other pages on the web
• User location based signals (approximate data)
• Webpage design characteristics 

Search results may use the above factors with no (pre-determined) importance of ranking. Users of Search are subject to the privacy policy in  Siri Suggestions, Search & Privacy .

If you have questions or concerns, please contact us at [email protected] .

Information about products not manufactured by Apple, or independent websites not controlled or tested by Apple, is provided without recommendation or endorsement. Apple assumes no responsibility with regard to the selection, performance, or use of third-party websites or products. Apple makes no representations regarding third-party website accuracy or reliability. Contact the vendor for additional information.

Start a discussion in Apple Support Communities

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

Firefox user agent string reference

This document describes the user agent string used in Firefox 4 and later and applications based on Gecko 2.0 and later. For a breakdown of changes to the string in Gecko 2.0, see Final User Agent string for Firefox 4 (blog post). See also this document on user agent sniffing and this Hacks blog post .

General form

The UA string of Firefox itself is broken down into four components:

Mozilla/5.0 (platform; rv:geckoversion) Gecko/geckotrail Firefox/firefoxversion

• Mozilla/5.0 is the general token that says the browser is Mozilla compatible, and is common to almost every browser today.
• platform describes the native platform the browser is running on (e.g. Windows, Mac, Linux or Android), and whether or not it's a mobile phone. Firefox OS phones say " Mobile "; the web is the platform. Note that platform can consist of multiple "; "-separated tokens. See below for further details and examples.
• rv:geckoversion indicates the release version of Gecko (such as " 17.0 ").
• Gecko/geckotrail indicates that the browser is based on Gecko.
• On Desktop, geckotrail is the fixed string " 20100101 "
• Firefox/firefoxversion indicates the browser is Firefox, and provides the version (such as " 17.0 ").
• From Firefox 10 on mobile, geckotrail is the same as firefoxversion .

Note: The recommended way of sniffing for Gecko-based browsers (if you have to sniff for the browser engine instead of using feature detection) is by the presence of the " Gecko " and " rv: " strings, since some other browsers include a " like Gecko " token.

For other products based on Gecko, the string can take one of two forms, where the tokens have the same meaning except those noted below:

Mozilla/5.0 (platform; rv:geckoversion) Gecko/geckotrail appname/appversion Mozilla/5.0 (platform; rv:geckoversion) Gecko/geckotrail Firefox/firefoxversion appname/appversion

• appname/appversion indicates the application name and version. For instance, this could be " Camino/2.1.1 ", or " SeaMonkey/2.7.1 ".
• Firefox/firefoxversion is an optional compatibility token that some Gecko-based browsers may choose to incorporate, to achieve maximum compatibility with websites that expect Firefox. firefoxversion will generally represent the equivalent Firefox release corresponding to the given Gecko version. Some Gecko-based browsers may not opt into using this token; for this reason, sniffers should be looking for Gecko — not Firefox!

Prior to Firefox 4 and Gecko 2.0, it was possible for extensions and plug-ins to add user agent parts, but that has not been possible since Firefox bug 581008 .

Mobile and Tablet indicators

The platform part of the UA string indicates if Firefox is running on a phone-sized or tablet device. When Firefox runs on a device that has the phone form factor, there is a Mobile; token in the platform part of the UA string. When Firefox runs on a tablet device, there is a Tablet; token in the platform part of the UA string instead. For example:

Note: The version numbers are not relevant. Avoid inferring materials based on these.

The preferred way to target content to a device form factor is to use CSS Media Queries. However, if you use UA sniffing to target content to a device form factor, please look for Mobi (to include Opera Mobile, which uses "Mobi") for the phone form factor and do not assume any correlation between "Android" and the device form factor. This way, your code will work if/when Firefox ships on other phone/tablet operating systems or Android is used for laptops. Also, please use touch detection to find touch devices rather than looking for "Mobi" or "Tablet", since there may be touch devices which are not tablets.

Note: Firefox OS devices identify themselves without any operating system indication; for example: "Mozilla/5.0 (Mobile; rv:15.0) Gecko/15.0 Firefox/15.0". The web is the platform.

Windows user agents have the following variations, where x.y is the Windows NT version (for instance, Windows NT 6.1).

Linux is a more diverse platform. Your distribution of Linux might include an extension that changes your user-agent. A few common examples are given below.

Android (version 40 and below)

Android (version 41 and above).

Beginning in version 41, Firefox for Android will contain the Android version as part of the platform token. For increased interoperability, if the browser is running on a version below 4 it will report 4.4. Android versions 4 and above will report the version accurately. Note that the same Gecko—with the same capabilities—is shipped to all versions of Android.

Focus for Android

From version 1, Focus is powered by Android WebView and uses the following user agent string format:

Tablet versions on WebView mirror mobile, but do not contain a Mobile token.

Starting in Version 6, users can opt into using a GeckoView-based Focus for Android with a hidden preference: it uses a GeckoView UA string to advertise Gecko compatibility.

Klar for Android

Since version 4.1, Klar for Android uses the same UA string as Focus for Android . Before version 4.1, it sent a Klar/<version> product/version token.

Focus for iOS

Version 7 of Focus for iOS uses a user agent string with the following format:

Note: this user agent was retrieved from an iPhone XR simulator and may be different on device.

Firefox for Fire TV

Version 3 (and probably earlier) of Firefox for Fire TV use a user agent string with the following format:

Firefox for Echo Show

From version 1.1, Firefox for Echo Show uses a user agent string with the following format:

Device-specific user agent strings

Although it is strongly discouraged by Mozilla, some handset manufacturers unfortunately include a token in their device's UA string that represents their device id. If this is the case, the Firefox OS UA string will look like the device-specific string in the table above, where nnnn; is the manufacturer's code for the device (see Guidelines ). Some of them we have noticed are of the form " NexusOne; ", " ZTEOpen; ", or " Open C; " (note that putting space is also discouraged). We provide this information to assist with your UA detection logic, but Mozilla discourages the detection of a device id in UA strings.

Here is a JavaScript regular expression that will detect all mobile devices, including devices with a device id in their UA string:

The i makes it case-insensitive, and mobi matches all mobile browsers.

Firefox OS version number

While the version number for Firefox OS is not included in the UA string, it is possible to infer version information from the Gecko version number present in the UA string.

Note: It's easy to find the correspondences by looking at the Mercurial repository names : repositories starting by mozilla-b2g are the release repositories for Firefox OS, and have both Firefox OS and Gecko versions in their names.

Firefox OS has a four-digit version number: X.X.X.Y . The first two digits are owned by the Mozilla product team and denote versions with new features (eg: v1.1, 1.2, etc.). The third digit is incremented with regular version tags (about every 6 weeks) for security updates, and the fourth is owned by the OEM.

• Recommendations on sniffing the UA string for cross-browser support
• window.navigator.userAgent

The latest user agents for web browsers on iOS

iOS is Apple's Operating System for iPhones, iPads and iPod Touches.

Here you can find the latest user agents for some of the most popular web browsers which run on iOS: Starting with Apple's own web browser: Safari, we've also got user agents for other browsers like Chrome and Firefox.

Explore our huge user agent listing , download our user agents database , (or you can search it ) if you're curious about other user agents.

Get latest user agents for iOS via API

Our Web Browser/Operating System Version Numbers API endpoint will provide you with the latest user agents for all sorts of popular web browsers and operating systems.

Experiment with different user agents

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.

Clear cache & history

Do i need to clear my cache.

Not sure why you've been asked to clear your cache? We can explain. Why you need to clear your cache

What is a cache?

Before you consider clearing your browser cache, you should know what it is! Learn a little bit about browser caches

Is it safe to clear my cache?

Are there any risks to clearing your cache? Find out if it's ok to clear your cache

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?

What does "Update browser" mean?

What does it actually mean? What does it mean to update your browser

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

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?

How to update your browser

Old software puts you at risk. Keep your browser fresh and up to date

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