In the table below, you will see which cookies are set for users, that are able to login to the webpage.
| Name | Provider | Purpose | Expiry | Type |
|---|---|---|---|---|
| wfwaf-authcookie-(hash) | wordfence.com | It is used to authenticate a user’s login request, and it allows Wordfence to detect non-logged in users and restrict their access to secure areas. | 12 hours | HTTP Cookie |
| wf_loginalerted_(hash) | wordfence.com | This cookie is used to notify the Wordfence admin when an administrator logs in from a new device or location. This is only set for administrators. | 1 year | HTTP Cookie |
| Wp-settings-1 | wordpress.org | WordPress sets a wp-settings-{UID} cookie for each individual logged-in user. The number on the end is the individual user ID from the users database table. This is used to customize the view of admin interface. | 1 year | HTTP Cookie |
| wordpress_sec_{hash} | wordpress.org | This cookie is used to store your authentication details. Its use is limited to the admin console area, /wp-admin/ | Session | HTTP Cookie |
| WordPress_test_cookie | wordpress.org | Checks if the browser accepts cookies | Session | HTTP Cookie |
| wp-settings-time-{UID} | wordpress.org | WordPress sets a wp-settings-time-{UID} for each individual logged-in user. The number on the end is the individual user ID from the users database table. | 1 year | HTTP Cookie |