Identifying DNN Cookies and their Functions


DNN extensively uses cookies to control authentication and data for various features. You may need to know the functions of various cookies when troubleshooting login and security issues.


A cookie is a small amount of text data provided to a web browser by a web server. The cookie is then stored on the visitor's hard drive and returned to the specific web server each time the browser requests a page from that server. The main purpose of cookies is to assign a unique identifier to each visitor of the website. It allows the website to track visitors as they navigate through the portal.

The most important cookie that DNN uses would be the forms authentication cookie. This cookie is generated when a user logs into the site. By default, it is a temporary (session) cookie. However, a user can change it to be a persistent cookie by checking the remember me option.

Cookies are also used for analytics in DNN; the application can track when users log in and which pages they open.

To see a list of available cookies in the Google Chrome browser, you can:

  1. Press F12 in your browser and open the Developer Tools
  2. In Click Application > Expand Cookies > Click the URL



Below is a list of DNN cookies to be aware of:


This cookie is used by the sites that are using .NET. It enables the site to track unique users that are not logged in.


This cookie is issued by DNN. It is necessary for site functionality. It is created when a user logs in. It is configured by using Forms Authentication.


This cookie is issued by Azure and is used mainly in Microservices.


Anti-forgery cookie issued by web applications that are built using the ASP.NET MVC technologies. It is designed to stop the unauthorized posting of content to a website (known as Cross-Site Request Forgery). It contains no information about the user and is deleted when the browser is closed.


A DNN forms authentication cookie, which is created when a user logs in.


A DNN cookie used by the CMS to determine if the visitor is using a Mobile Device.


A DNN cookie that is used to store the current language. In a monolingual portal, it contains the browser default language. However, if the site supports multiple languages, this cookie may be different based on the language selected by the user.


A DNN cookie used by the CMS to store the TabID of the last visited page.


A DNN cookie used by the CMS to determine the UI state across postbacks (i.e., it determines whether or not to reload the page with the Editing interface).



Back to top



Please sign in to leave a comment.