← Blog

Is your remote desktop open to the whole internet? Here's how to find out.

Tenant Strike2 min read

Attackers don't need a clever exploit when remote desktop is left reachable from anywhere. Automated scans find it for them. Here is how to check, and what to do if yours is exposed.

Somebody set up remote desktop years ago so the bookkeeper could work from home, or so a vendor could fix the server. It worked, nobody thought about it again, and the door has been open ever since.

Remote Desktop, usually called RDP, lets someone control a computer over a network. When it's reachable from the public internet, it stops being a private tool. Attackers run automated scans across the whole internet looking for it. They aren't choosing your company. They're collecting every address that answers.

What it looks like when it goes wrong

Huntress, a security firm that responds to these incidents, described three real cases earlier this year:

  • A healthcare organization had an RDP server directly exposed. The attacker needed nothing more than the open port. Huntress's point was that one firewall rule could have stopped the whole incident.
  • Attackers came in through an exposed Remote Desktop web portal and were removed. They came back the next morning through the same portal with a different account, because the portal was still open.
  • In the third, attackers got in through a vulnerable VPN and then turned on RDP themselves, to move around inside the network.

That second case is the one to remember. Kicking someone out doesn't help if the door they used stays open. Huntress has also reported that exposed RDP was the second most common way in across the cases it handled in one 2025 summary, behind compromised VPN appliances.

How to find out

Ask whoever manages your network. Try this wording: "Is remote desktop reachable from the internet at any of our locations, on any port?" The "any port" matters, because moving RDP off its usual port doesn't hide it from a scan.

Look at it from the outside. Our free scan reads public internet-scan records for the addresses connected to your domain, and it flags remote desktop if those records show it. A clean result isn't proof, though. It only covers addresses tied to your domain, so a server on a separate internet connection or at a home office may not show up.

If you find it

  1. Close it at the firewall, then confirm from outside that it's really closed.
  2. If people still need remote access, put it behind a VPN or a gateway that requires multi-factor authentication.
  3. Change the passwords on any account that could sign in through it, and check the sign-in history for logins nobody recognizes.

Tenant Strike's Pro plan runs the same outside check alongside its review of your Microsoft 365 settings, because an open door on a server and a weak setting in a tenant often end up in the same incident.

AI-researched from public sources. We label AI-assisted writing — see our trust page.

See your own risk

Want this for your own Microsoft cloud?

Tenant Strike finds the security gaps in your Microsoft 365 and Azure, shows how they chain into a real break-in, and hands you a step-by-step fix for every one — read-only. The scanner never requests a write permission. The optional configuration reader holds one, ConfigurationMonitoring.ReadWrite.All, whose only writes are Microsoft’s own snapshot records; it cannot change your tenant. Start a 7-day Pro trial — no credit card.