Legacy and historic user agents

Internet Explorer 5 through 11, Presto-era Opera, Netscape, NCSA Mosaic and text-mode browsers.

42 user agents

0 matching user agents ·

User agent string Browser Platform Device Actions

Internet Explorer's shifting format

IE changed its string format three times, and the last change is the one that still catches people out. IE 11 removed the MSIE token entirely — deliberately, so that sites sniffing for MSIE would stop serving it degraded content.

IE 8:   Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0)
IE 10:  Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.2; Trident/6.0)
IE 11:  Mozilla/5.0 (Windows NT 10.0; Win64; x64; Trident/7.0; rv:11.0) like Gecko

Detecting IE 11 requires matching Trident/7.0 or rv:11.0. Any rule looking for MSIE misses it completely — which is exactly the outcome Microsoft intended.

The Trident version ladder

TridentInternet ExplorerReleased
Trident/7.0IE 112013
Trident/6.0IE 102012
Trident/5.0IE 92011
Trident/4.0IE 82009

Opera before Chromium

Until version 15, Opera used its own Presto engine and an unusual format that put the version at the end rather than the start:

Opera/9.80 (Windows NT 6.1; WOW64) Presto/2.12.388 Version/12.18

The leading Opera/9.80 was frozen for years and says nothing about the real version — the actual release is the Version/12.18 at the end. Parsers that read the first number report every late Presto Opera as 9.80.

Why any of this still matters

Legacy strings turn up in three places: archived log analysis, kiosk and industrial systems that never got replaced, and parser test fixtures. If you maintain a user agent parser, these are the cases that expose bad assumptions — a version at the end of the string, a missing product token, a Mozilla/4.0 prefix.

Frequently asked questions

How do I detect Internet Explorer 11?

Match Trident/7.0 or rv:11.0. IE 11 removed the MSIE token, so any rule built around MSIE will not see it. In JavaScript, !!window.MSInputMethodContext && !!document.documentMode is a reliable feature-based alternative.

Why does old Opera say 9.80?

Opera froze the leading Opera/9.80 token and moved the real version to a Version/ token at the end of the string. It was done for compatibility with sites that had hard-coded checks against the leading number, and it means a correct parser has to read the last token rather than the first.

Do people still use these browsers?

Not in meaningful numbers on the public web, but they persist in industrial control systems, medical equipment, ATMs and kiosk deployments where the software was certified against a specific browser and never revalidated. If your audience includes enterprise or government users, IE 11 traffic has not necessarily reached zero.

Other categories