Web-exposed Screen Profiler

The Web-exposed Screen Profiler visualizes web-exposed screen information to show you what your screen and browser window looks like to a website.

This also demonstrates how the visitor’s OS can be deduced without using user-agent data and how extended displays can be derived without using the Multi-Screen Window Placement API. It can be a useful tool to help develop more comprehensive detection scripts that can infer more device details beyond user-agent data which can be easily spoofed and mimicked.

Try resizing your window, moving it to a different screen, zooming in or out, changing the size of your taskbar/menu bar, and turning your bookmark bar on and off. Take a screenshot of it with a bot or online screenshot tool and see if it gets detected as a VM.

Then give me a star and buy me a coffee 😜
Star Follow @snokamedia

In the mid-2000s, the Window object's capabilities expanded with the introduction of the screen API. The screen API provides information about the user's display, such as screen resolution, color depth, and available screen space. This API allowed developers to create web applications that could adapt to different screen sizes and resolutions.

The screenLeft and screenTop properties were first introduced in Internet Explorer 4, which was released in 1997. They were later adopted by other major browsers, including Netscape Navigator and Mozilla Firefox. The properties were included in the W3C's CSSOM View Module, which was released as a recommendation in 2008.

In the early days of the web, the screenLeft and screenTop properties were useful for creating pop-up windows that were positioned relative to the screen, rather than the browser window. They were often used for displaying ads, as well as for creating custom login forms and other UI elements that needed to be positioned outside of the browser window.

Additional Credits:
UAParser.js
Accordion CSS.