Works with your stack
Cookie consent and security, login and maintenance plugins
cookies that keep doors working
Security, login and maintenance plugins set cookies only for the visitors who need them: a two-step sign-in, a login with a Google or social account, a password page, or a bypass link during maintenance. These cookies keep a door working, so they are necessary and need no consent. Cookie Rocks recognises them and lists them in your cookie policy.

What these plugins keep in the browser
- Limit Login Attempts Reloaded
- A cookie keeps the two-step sign-in going.
- Loginizer
- Cookies keep a sign-in with a social account going.
- SiteGround Security
- Cookies keep the two-step sign-in going.
- Google Apps Login
- A cookie keeps the sign-in with a Google account going.
- Admin and Site Enhancements
- A cookie lets the visitor in after entering the site password.
- WP File Manager
- A session cookie tells the file manager that a download ended. Only people who use the file manager get it.
- Maintenance, CMP Coming Soon, Hostinger Tools
- A cookie lets a visitor with the bypass link see the site during maintenance or before launch.
- The Preloader
- The free version sets no cookie. The Pro version remembers that the preloader was shown once.
What matters for consent with Security and login
Necessary, not tracking
Each of these cookies serves a step the visitor asked for: signing in, entering a password, using a bypass link. None follows the visitor elsewhere.
Only for the people who use them
A visitor who never signs in or never gets a bypass link never gets these cookies.
Named in your policy
Cookie Rocks recognises them and lists them in your cookie policy, with their purpose.
What our tests found on Security and login
Good to know · WP File Manager, File Manager Advanced (elFinder)What elFinder file managers store in browsers
elFinder file managers: elfdl* (necessary, session, file manager users only).
Name Kept in Category What it is for elfdl*cookie Necessary Tells the file manager that a download has finished Read in the code of WP File Manager, File Manager Advanced (elFinder), 4 November 2026.
Full detail
File managers built on elFinder (WP File Manager, File Manager Advanced) set elfdl<request id> = 1, a session cookie limited to the connector path, when a download ends, so the interface knows it finished. Only people who use the file manager get it. The Audit 2.9.11 lists elfdl* without a category.
Good to know · Preloader (Alobaidi)Where the preloader_shown cookie comes from
Preloader: preloader_shown is set by the Pro version only (preference: show the preloader once).
Name Kept in Category What it is for preloader_showncookie Preferences Remembers that the preloader was already shown Read in the code of Preloader (Alobaidi), 4 November 2026.
Full detail
The free Preloader plugin (the-preloader 2.0.2) never sets preloader_shown: it only deletes it from an admin button. The cookie comes from the Pro version, which shows the preloader once per visitor. The Audit 2.9.11 lists it without a category because it is named in the free code.
Good to know · Limit Login Attempts ReloadedWhat Limit Login Attempts Reloaded stores in visitors' browsers
Limit Login Attempts Reloaded: 1 cookie(s) or browser key(s) for visitors, recognised by Cookie Rocks from 2.9.8.
Name Kept in Category What it is for llar_mfa_statecookie Necessary Keeps the two-step sign-in going Read in the code of Limit Login Attempts Reloaded, 2 November 2026.
Full detail
Limit Login Attempts Reloaded can store these in a visitor's browser: llar_mfa_state (cookie, necessary: Keeps the two-step sign-in going). Cookie Rocks recognises them from 2.9.8, with this category and purpose, and lists them in the cookie policy when it sees them.
Good to know · LoginizerWhat Loginizer stores in visitors' browsers
Loginizer: 2 cookie(s) or browser key(s) for visitors, recognised by Cookie Rocks from 2.9.8.
Name Kept in Category What it is for lz_social_errorcookie Necessary Keeps the sign-in with a social account going lz_social_logincookie Necessary Keeps the sign-in with a social account going Read in the code of Loginizer, 2 November 2026.
Full detail
Loginizer can store these in a visitor's browser: lz_social_error (cookie, necessary: Keeps the sign-in with a social account going); lz_social_login (cookie, necessary: Keeps the sign-in with a social account going). Cookie Rocks recognises them from 2.9.8, with this category and purpose, and lists them in the cookie policy when it sees them.
Good to know · SiteGround SecurityWhat SiteGround Security stores in visitors' browsers
SiteGround Security: 2 cookie(s) or browser key(s) for visitors, recognised by Cookie Rocks from 2.9.8.
Name Kept in Category What it is for sg_security_2fa_dnc_cookiecookie Necessary Keeps the two-step sign-in going sgs_2fa_login_noncecookie Necessary Keeps the two-step sign-in going Read in the code of SiteGround Security, 2 November 2026.
Full detail
SiteGround Security can store these in a visitor's browser: sg_security_2fa_dnc_cookie (cookie, necessary: Keeps the two-step sign-in going); sgs_2fa_login_nonce (cookie, necessary: Keeps the two-step sign-in going). Cookie Rocks recognises them from 2.9.8, with this category and purpose, and lists them in the cookie policy when it sees them.
Good to know · Google Apps LoginWhat Google Apps Login stores in visitors' browsers
Google Apps Login: 1 cookie(s) or browser key(s) for visitors, recognised by Cookie Rocks from 2.9.8.
Name Kept in Category What it is for wordpress_google_apps_logincookie Necessary Keeps the sign-in with a Google account going Read in the code of Google Apps Login, 2 November 2026.
Full detail
Google Apps Login can store these in a visitor's browser: wordpress_google_apps_login (cookie, necessary: Keeps the sign-in with a Google account going). Cookie Rocks recognises them from 2.9.8, with this category and purpose, and lists them in the cookie policy when it sees them.
See the 4 other findings
Good to know · Admin and Site EnhancementsWhat Admin and Site Enhancements stores in visitors' browsers
Admin and Site Enhancements: 1 cookie(s) or browser key(s) for visitors, recognised by Cookie Rocks from 2.9.8.
Name Kept in Category What it is for asenha_password_protectioncookie Necessary Lets the visitor in after entering the site password Read in the code of Admin and Site Enhancements, 2 November 2026.
Full detail
Admin and Site Enhancements can store these in a visitor's browser: asenha_password_protection (cookie, necessary: Lets the visitor in after entering the site password). Cookie Rocks recognises them from 2.9.8, with this category and purpose, and lists them in the cookie policy when it sees them.
Good to know · MaintenanceWhat Maintenance stores in visitors' browsers
Maintenance: 1 cookie(s) or browser key(s) for visitors, recognised by Cookie Rocks from 2.9.8.
Name Kept in Category What it is for skip_maintenance_modecookie Necessary Lets a visitor with the bypass link see the site during maintenance Read in the code of Maintenance, 2 November 2026.
Full detail
Maintenance can store these in a visitor's browser: skip_maintenance_mode (cookie, necessary: Lets a visitor with the bypass link see the site during maintenance). Cookie Rocks recognises them from 2.9.8, with this category and purpose, and lists them in the cookie policy when it sees them.
Good to know · CMP Coming Soon & MaintenanceWhat CMP Coming Soon & Maintenance stores in visitors' browsers
CMP Coming Soon & Maintenance: 1 cookie(s) or browser key(s) for visitors, recognised by Cookie Rocks from 2.9.8.
Name Kept in Category What it is for cmp_bypasscookie Necessary Lets a visitor with the bypass link see the site while it is in maintenance Read in the code of CMP Coming Soon & Maintenance, 2 November 2026.
Full detail
CMP Coming Soon & Maintenance can store these in a visitor's browser: cmp_bypass (cookie, necessary: Lets a visitor with the bypass link see the site while it is in maintenance). Cookie Rocks recognises them from 2.9.8, with this category and purpose, and lists them in the cookie policy when it sees them.
Good to know · Hostinger ToolsWhat Hostinger Tools stores in visitors' browsers
Hostinger Tools: 1 cookie(s) or browser key(s) for visitors, recognised by Cookie Rocks from 2.9.8.
Name Kept in Category What it is for hostinger_bypass_codecookie Necessary Lets a visitor with the bypass link see the site while it is in coming-soon mode Read in the code of Hostinger Tools, 2 November 2026.
Full detail
Hostinger Tools can store these in a visitor's browser: hostinger_bypass_code (cookie, necessary: Lets a visitor with the bypass link see the site while it is in coming-soon mode). Cookie Rocks recognises them from 2.9.8, with this category and purpose, and lists them in the cookie policy when it sees them.
Security
Other plugins of the same kind.
Questions
Do login cookies need consent?
No. A cookie that keeps a sign-in or a password page working is necessary. It still belongs in your cookie policy.
What happens after the 30-day trial?
The banner, your visitors’ choices and your proofs of consent keep working. Without a key, most settings lock, updates and support stop. Take a key at any time and everything opens again.
For sites with login or maintenance plugins
Doors that keep working, a policy that names them.
necessary
Every feature of the complete plugin for 30 days, no card. Your login and maintenance pages work as they do today.
- During the trial: everything, including the full settings and the scans
- After 30 days without a key: the banner, your visitors’ choices and your proofs of consent keep working
- What waits for a key: most settings, updates and support

Get your trial key
Your e-mail and your site. Your key arrives as soon as you confirm your e-mail.