How to See Who Logged Into Your WordPress Site
WordPress tells you nothing about logins by default. One small log answers the question every owner eventually asks: was that me?
On this page
WordPress login history does not exist out of the box. The Users screen shows accounts and roles, nothing about when anyone last signed in or from where. To answer “who logged into my WordPress site”, you need a log that listens for login events and stores them. Here is what that log should capture, how to read it, and what to do the day you see a login that was not you.
What WordPress gives you
Nothing in the admin. Two things exist outside it:
Server access logs. Your host records every request, including POSTs to wp-login.php, with IP and time. They do not say which username or whether the attempt succeeded, and on shared hosting they can be hard to reach.
Session tokens. Each user’s profile has a Sessions section with a button to log out everywhere else. It is a control, not a history.
So the practical answer is a plugin.
What a login log should record
For every attempt, successful or not:
- Username that was tried. For failures, this shows whether bots are guessing real accounts or just admin.
- Result. Success or failure, and for failures, why if known.
- Time. In your site’s timezone, so odd hours are obvious.
- IP address. The single most useful field for “was that me”.
- User agent. Browser and device. A login from a browser you never use is a clue.
An activity log that also records logouts, password resets, role changes and profile email changes gives you the full account story, not just the door. DevDome Activity Log records logins and failed logins with IP, plus user creation, deletion and role changes, in a filterable table with search and CSV export. It is free, local and needs no account. We make it, so weigh that; the field list above is what to check in any log.
How to read it
Open the log, filter to login events, and look for three patterns.
Successes you do not recognise. Sort successes by IP. Every one should belong to you or a team member. Look up any you do not know; a geolocation lookup on the IP takes seconds. A success from a datacenter or a country nobody on the team was in is a compromised account until proven otherwise.
Failures against real usernames. Failures against admin or nonsense names are background noise. Failures against your actual editor’s username mean someone has harvested it, probably from author archive URLs, and is working on the password. Make sure that account has a strong password and two-factor.
Timing. Logins at 3 a.m. from your own IP are probably you. Logins at 3 a.m. from a new IP are not. Clusters of failures followed by one success are the signature of a successful brute-force attempt.
When a login is not yours
Act in this order, within minutes:
- Reset the password for the affected account, to something long and new.
- End every session. Use the Sessions button on the profile, or change the security keys in wp-config.php to log out everyone at once. A password change alone leaves the attacker’s session alive.
- Enable two-factor for that account and every administrator.
- Check what they did. Filter the activity log to that user since the suspicious login: new users, role changes, plugin installs, edited pages. Undo each.
- Scan the files. A logged-in administrator can upload a plugin, which means a backdoor may exist that the log cannot see. Run a malware scan that verifies core and plugins against WordPress.org.
- Find how the password leaked. Reuse from another breach is the usual answer. A password manager and unique passwords close that door.
Looking up an IP you do not recognise
Most unfamiliar IPs turn out to be innocent: a colleague on a phone network, a hotel, a new home connection. A quick lookup settles it. Paste the address into any IP lookup service and read three things: the country, the organisation that owns the range, and whether it is a residential provider or a hosting company. A residential provider in a city where a team member lives is almost certainly them; ask. A hosting or cloud provider is not where people browse from, and a successful login from one is a red flag even if the country is yours. A VPN provider is ambiguous, since both staff and attackers use them; check whether anyone on the team was on a VPN at that time. Note what you found in the log’s notes field if it has one, so the next time that address appears you do not look it up again.
Cut the noise so the signal shows
A login log on a site with no protection is mostly failures from bots. Three changes make it readable:
- Rename or remove the admin username.
- Limit login attempts and disable XML-RPC unless something needs it.
- Run bot protection that recognises scanners by behaviour and blocks them before they reach the form; the Record Bots mode in DevDome Bot Protection shows what it would block before you turn blocking on.
Afterwards the log shows your team, a trickle of blocked noise, and nothing else. That is the state where a wrong login stands out the moment it happens.
Keep it bounded
Ninety days of login history covers any investigation you will realistically run. Restrict the log to administrators, do not store more than the fields above, and tell your team it exists. A login log is a security tool, not surveillance, and keeping it small and open about keeps it that way.
Related reading: Stop Spam Registrations in WordPress Without Annoying Real Users.
Disclosure: DevDome publishes this blog and makes the products it mentions. We describe what they do rather than promise results.
Key takeaways
- WordPress stores no login history. Only a plugin or server logs can tell you who signed in and when.
- A login log should record the user, the time, the IP address, success or failure, and ideally the user agent.
- Read it for three things: successes from unfamiliar IPs, bursts of failures against real usernames, and logins at odd hours.
- A successful login you do not recognise means a compromised password. Reset it, end sessions, enable two-factor.
- Keep the log bounded and private: 90 days is plenty, and only administrators should see it.
Sources
- WordPress Developer Resources: wp_login hook : the event a login log listens to
- WordPress Developer Resources: wp_login_failed hook : the event for failed attempts
- WordPress.org: Two-factor authentication : what to enable after a suspicious login
Links last checked October 17, 2026.
Frequently asked questions
Can I see login history in WordPress without a plugin?
Not in the admin. Your web server's access log records requests to wp-login.php with IPs and timestamps, but not which user or whether it succeeded. A plugin that hooks the login events is the practical answer.
How do I know if a login was me?
Compare the IP and time with where you were. Your home, office and phone networks have IPs you can look up. A login from a country or a datacenter range you have never used, especially at night, is the red flag.
What are all these failed logins for admin?
Automated bots trying the default username against common passwords. If you have no user called admin, they fail harmlessly. If you do, rename it. Limit attempts and let bot protection block the scanners.
Should I log out all users after a suspicious login?
Yes. Changing the password does not end existing sessions on its own. Use the Sessions option on the user's profile, or change the security keys in wp-config.php to end every session at once.