Skip to content

Exposed services checker

See whether your domain's servers accept connections on ports that should rarely be open to the internet, such as databases and remote desktop.

Run this check on a domain you have verified

Looking for exposed services means opening connections to ports on your servers, so Ironfang runs it only after you prove you control the domain (a DNS TXT record) and confirm you are authorised to assess it. It is part of the free External Security Check: create an account, add the domain, verify it and run the check.

The 21 ports it tries
  • FTP21
  • SSH22
  • Telnet23
  • HTTP80
  • HTTPS443
  • SMB445
  • Microsoft SQL Server1433
  • Oracle Database1521
  • Docker API2375
  • MySQL / MariaDB3306
  • Remote Desktop (RDP)3389
  • PostgreSQL5432
  • VNC5900
  • CouchDB5984
  • Redis6379
  • HTTP (alternate)8080
  • HTTPS (alternate)8443
  • Cassandra9042
  • Elasticsearch9200
  • Memcached11211
  • MongoDB27017

Example report

example.com
  • 1 High
  • 1 Information
  • 5 passed
  • Database port reachable from the internetHigh

    192.0.2.10 accepted a connection on port 3306 (MySQL) from the internet.

    Next step

    Close the port to the internet with a firewall or security group, and reach the database over a private network, VPN or bastion instead.

    View fix guide

  • SSH reachable from the internetInformation

    192.0.2.10 accepted a connection on port 22 (SSH) from the internet.

    Next step

    Review whether SSH needs to be public.

    View fix guide

What the exposed services check looks at

  • Databases

    SQL Server, Oracle, MySQL, PostgreSQL, Redis, MongoDB and four more.

  • Remote access

    SSH, Remote Desktop and VNC.

  • File sharing and containers

    Windows file sharing (SMB) and the unencrypted Docker API.

  • Plaintext services

    FTP and Telnet, which send passwords unencrypted.

One connection attempt per port, with nothing sent over it. Addresses in Cloudflare's proxy network are skipped.

Understand the issue and your next step

Each finding explains what we found, why it matters and what you can change. Start with the issues that need attention, then open the evidence when you want the detail.

  1. Enter your domain
  2. Review the findings
  3. Follow the fix guides
Example finding

Database port reachable from the internetHigh

A port normally used by a database accepted a connection from the internet.

3306/tcp (MySQL): connection accepted

Common exposed service issues you can put right

  • Database port reachable from the internetHigh

    A database that accepts connections from the internet is open to password guessing and to any flaw found in it later. Limit it to known networks, a VPN or a bastion host.

    Read the fix guide

  • Remote desktop port reachable from the internetMedium

    Remote desktop is a frequent target of automated login attempts. Put it behind a VPN or an access gateway rather than on a public port.

    Read the fix guide

  • SSH reachable from the internetInformation

    SSH is often public on purpose. Use key-based logins only, keep it updated, and limit it to known addresses where you can.

    Read the fix guide

  • Windows file sharing reachable from the internetHigh

    The SMB port (445) accepted a connection from the internet.

    Read the fix guide

  • Container API port reachable from the internetHigh

    The Docker API port (2375) accepted a connection from the internet.

    Read the fix guide

  • Unencrypted remote service reachableHigh

    A Telnet or FTP service accepted a connection from the internet.

    Read the fix guide

  • Web service on a non-standard portInformation

    A web-style port other than 80 or 443 accepted a connection.

    Read the fix guide

Keep watch after you've fixed it

Ironfang Security rechecks a verified domain every week or every day and tells you what changed: new findings, fixes and certificates nearing expiry.

Free during the preview. Domain verification required.

  1. NewIssue detected
  2. FixedConfirmed by recheck
  3. ReopenedDetected again

How the check works

  • One TCP connection attempt to each of 21 fixed ports, listed above, on the domain's public addresses.
  • Databases: SQL Server (1433), Oracle (1521), MySQL and MariaDB (3306), PostgreSQL (5432), CouchDB (5984), Redis (6379), Cassandra (9042), Elasticsearch (9200), Memcached (11211) and MongoDB (27017).
  • Remote access and file sharing: SSH (22), Remote Desktop (3389), VNC (5900) and SMB (445).
  • Plaintext and container services: FTP (21), Telnet (23) and the unencrypted Docker API (2375).
  • Web ports: 80 and 443, which a website is expected to answer on, and the alternate ports 8080 and 8443.
  • Nothing is sent to any port. Each connection is opened and closed, and a greeting is read only from services that speak first: FTP, SSH, MySQL and VNC.

Reading a result

A service that accepts connections from the internet can be reached by anyone, including the automated scanners that sweep address ranges for open databases and remote desktop logins. For many sites only the web ports need to be public; the rest should be reachable only from known networks, a VPN or a bastion host.

A finding means a port accepted a TCP connection from the scanner. It does not mean the service accepts logins or has a known flaw. It means the service is reachable, and so open to password guessing and to any vulnerability found in it later.

Databases, SMB, the Docker API and plaintext services are raised as High, remote desktop as Medium. SSH and extra web ports are informational, because they are often public on purpose; review them rather than close them by reflex.

What it does not do

  • It tries only the 21 listed ports. A service on any other port is not seen.
  • Addresses in Cloudflare's proxy network are skipped, because an open port there belongs to Cloudflare and says nothing about your origin server. The origin behind them is not looked for or tested.
  • It sees what is reachable from the scanner's address. A firewall rule that admits only certain source addresses can hide a port that others can still reach.
  • It does not log in, send requests, try passwords or look for vulnerabilities in the services it finds. It is an automated external check, not a penetration test.

What happens to the domain you enter

This check runs in Ironfang Security, for a domain you have verified and confirmed you are authorised to assess, and its results are kept in that domain's history.

Guides

A few things worth knowing

Why can I not check any domain for open ports?
Because the check connects to the domain's servers. Ironfang runs it only for a domain whose DNS you control, proven with a TXT record, and after you confirm you are authorised to assess it. None of the free tools on this site scans ports.
Is an open SSH port a problem?
Not in itself, so it is reported as informational. Use key-based logins only, keep OpenSSH updated, and limit it to known source addresses where you can.
What traffic does the check send?
One TCP connection attempt to each listed port, paced per address, from Ironfang Security's published scanner address. Nothing is sent over the connection, and a greeting is read only from services that speak first.
My site is behind Cloudflare. Is my origin server checked?
No. Cloudflare addresses are skipped, because an open port there is Cloudflare's, not yours. An origin server's ports are checked only when the domain resolves to its address directly.