__RequestVerificationToken_ on www.ipfin.co.uk
About this cookie:
This is an anti-forgery cookie set by web applications built using ASP.NET MVC technologies. It is designed to stop unauthorised posting of content to a website, known as Cross-Site Request Forgery. It holds no information about the user and is destroyed on closing the browser.
There is no specific information about this cookie from this host provider. If you have any information about how this cookie is used by this host, please get in touch.
Related general information about __RequestVerificationToken_:
We don’t have enough information about this cookie or the website hosting it to be able to assign it to a category at this time. However, we are constantly updating our knowledge base, so do check back if you need to know more. If it is urgent then get in touch and maybe we can look into it for you.More about cookie classifications.
Third Party Cookies
If the host domain for a cookie is different to the one in the browser bar when it was downloaded, then it is a third party cookie.
They are usually placed in a website via scripts or tags added into the web page. Sometimes these scripts will also bring additional functionality to the site, such as enabling content to be shared via social networks.
For example, if you visit a site that has a YouTube video in one of its pages. This has been included by the website owner, using a piece of code provided by YouTube. YouTube will then be able to set cookies through this code, and know that you have watched that video, or even just visited the page the video is in.
Online advertising is the most common use of third party cookies. By adding their tags to a page, which may or may not display adverts, advertisers can track a user (or their device) across many of the websites they visit.
This allows them to build up a 'behavioural profile' of the user, which can then be used to target them with online ads based around their 'calculated' interests.
Session Cookies are only stored temporarily in the browser's memory, and are destroyed when it is closed down, although they will survive navigating away from the website they came from.
If you have to login to a website every time you open your browser and visit it - then it is using a session cookie to store your login credentials.
Many websites use session cookies for essential site functions, and to make sure pages are sent to the browser as quickly and efficiently as possible.
Secure cookies are only transmitted via HTTPS - which you will typically find in the checkout pages of online shopping sites.
This ensures that any data in the cookie will be encrypted as it passes between the website and the browser. As you might imagine – cookies that are used by e-commerce sites to remember credit card details, or manage the transaction process in some way, would normally be secure, but any other cookie might also be made secure.
This protects it from so-called cross-site-scripting (XSS) attacks, where a malicious script tries to send the content of a cookie to a third party website.