Popular topics: Multilogin X, Multilogin 6,
-
Retrieving the token Using the automation token in a workspace Retrieving profile, folder, and workspace IDs Retrieving the user ID Selenium automation example Playwright automation example Puppeteer automation example Logging in to Multilogin automatically Setting up automatic cookie collection Auto-launching the agent Exporting proxy details from profiles Converting external proxy lists into API-ready JSON files Automation FAQ
-
Error: Failed to get IP data: can't connect through proxy Error: Javax.crypto.badpaddingexception: pad block corrupted Status: Update in progress...Loading (1) of 2 components Error: Fingerprint composition failed Connection error due to non-Latin characters in Windows username Error: Mimic/Stealthfox executable is not found Multilogin 6 browser profile shows "Error" in status Can't launch a profile in Multilogin 6 JavaScript error when switching to dark mode in Multilogin 6 Common errors and solutions in Multilogin 6
Multilogin X
Multilogin 6
Passive OS fingerprint masking (TCP/IP fingerprint)
Written by Yelena Varabyeva
Updated on July 27th, 2024
It's possible to identify a device's operating system by analyzing its network traffic. Variations in the TCP/IP stack implementations across operating systems assist in determining the OS that generated the package.
This set of OS-specific package parameters is known as an OS fingerprint. As this method entails observing traffic without sending requests, it's referred to as passive OS fingerprinting.
You can check this fingerprint on browserleaks.com/ip under "TCP/IP Fingerprint". In Multilogin you may encounter the following results:
- A proxy server intercepts your network packages and repacks them – that's why if you use a proxy, the above test may show an OS different from your original one
- If you use Multilogin on a VM, the above test may show your original OS regardless of the OS selected in the profile settings
TCP/IP fingerprint is a connection fingerprint, and Multilogin cannot affect it in any way. Websites, for the most part, ignore this parameter, since mismatches between TCP/IP Fingerprint and actual OS are common in normal traffic. They are caused by certain network devices and configurations.
Nevertheless, it's possible to mask this fingerprint on the proxy level by using services that specifically provide this type of masking solution – for example, iproxy.online.