Machine protocols
What does the Machine protocols cluster cover?
AdminKit groups this topic into the Machine protocols cluster: MQTT, Modbus, RDP, VNC and the other protocols your devices and legacy systems speak were mostly designed for trusted local networks, not the open internet — exposing one is a common way in for an attacker.
Tools (3)
All tools →- MQTT exposure Check whether your own MQTT broker accepts unauthenticated connections, live.
- Modbus exposure Check whether your own Modbus/TCP device is reachable from the internet, live.
- RTSP camera exposure Check whether your own RTSP camera or video server is exposed and readable without authentication, live.
Guides (42)
All guides →- Is Your BACnet/IP Device Exposed? | AdminKit Guide
- Open Redis and Unauthenticated Databases | AdminKit Guide
- RDP and VNC Exposed to the Internet | AdminKit Guide
- Port Check for Exposed Cameras and Routers | AdminKit
- TR-069 and Port 7547: When ISP Access Is a Risk | AdminKit
- Is Port 2049 (NFS) Exposed? | AdminKit
- Is Port 5060 (SIP) Exposed? | AdminKit
- Is Port 6443 (Kubernetes API) Exposed? | AdminKit
- Is Port 123 (NTP) Exposed? | AdminKit
- Is Port 21 (FTP) Exposed? | AdminKit
- Is Port 5900 (VNC) Exposed? | AdminKit
- Network Hygiene Checklist for Small Business | AdminKit
- How to Harden RDP (Port 3389) Exposure | AdminKit
- Is Port 6379 (Redis) Exposed? | AdminKit
- Is Port 22 (SSH) Exposed? | AdminKit
- Is Port 2375 (Docker API) Exposed? | AdminKit
- Is Port 23 (Telnet) Exposed? | AdminKit
- Is Port 3389 (RDP) Exposed? | AdminKit
- Is Port 445 (SMB) Exposed? | AdminKit
- Is Port 8080 (Admin Panel) Exposed? | AdminKit
- Certificate Transparency Logs Explained | AdminKit Guide
- How to Harden a Home or SMB MQTT Broker | AdminKit
- How to Secure an MQTT Broker | AdminKit Guide
- Is Modbus TCP (Port 502) Exposed? | AdminKit
- Is Port 11211 (Memcached) Exposed? | AdminKit
- Is Port 161 (SNMP) Exposed? | AdminKit
- Is Port 1521 (Oracle) Exposed? | AdminKit
- Is Port 1883 (MQTT) Open on My Router? | AdminKit
- Is Port 27017 (MongoDB) Exposed? | AdminKit
- Is Port 3306 (MySQL) Exposed? | AdminKit
- Is Port 389 (LDAP) Exposed? | AdminKit
- Is Port 47808 (BACnet/IP) Exposed? | AdminKit
- Is Port 5432 (PostgreSQL) Exposed? | AdminKit
- Is Port 554 (RTSP) Exposed? | AdminKit
- Is Port 5683 (CoAP) Exposed? | AdminKit
- Is Port 7547 (TR-069) Exposed? | AdminKit
- Is Port 8883 (MQTTS) Exposed? | AdminKit
- Is Port 9200 (Elasticsearch) Exposed? | AdminKit
- mDNS, SSDP and UPnP: LAN Discovery Explained | AdminKit
- Modbus TCP 502 Remediation Playbook | AdminKit
- Securing an Exposed Telnet Device (Beyond Off) | AdminKit
- Using Port Check to Inventory IoT Device Exposure | AdminKit
Glossary (56)
Full glossary →- ACME protocol — ACME, defined in RFC 8555, lets a server prove it controls a domain and receive a signed TLS certificate automatically, with no human filling out a CA request form by hand. It's what makes short-lived certificates practical, like Let's Encrypt's 90-day ones. AdminKit's SSL/TLS check can confirm the validity window of a certificate an ACME client like Let's Encrypt issued.
- ALPN (Application-Layer Protocol Negotiation) — ALPN (Application-Layer Protocol Negotiation) is a TLS extension, defined in RFC 7301, letting a client and server agree which protocol -- h2 or http/1.1 -- to run over a connection inside the TLS handshake, before any data is sent. That negotiation happens inside the same handshake AdminKit's SSL/TLS check inspects, though its result doesn't surface the negotiated protocol.
- BACnet — BACnet (Building Automation and Control Networking protocol) is a communication standard used to connect and control building-automation equipment: HVAC, lighting, access control and fire and life-safety systems. BACnet/IP, which runs on UDP port 47808, has no built-in authentication or encryption, so AdminKit's port check tool can confirm whether a building's automation network is reachable from the open internet.
- Certificate authority (CA) — A certificate authority (CA) is an organization trusted, under the X.509 framework in RFC 5280, to verify a domain's identity and sign a TLS certificate vouching for it, chained back to a root that browsers trust directly. AdminKit's SSL check tool shows the certificate authority and chain a live site actually presents.
- Certificate chain — A certificate chain is the ordered sequence of certificates, per RFC 5280's path-validation rules, linking a server's TLS certificate up through one or more intermediate certificates to a root a client already trusts. AdminKit's SSL/TLS check inspects whether a server actually sends every certificate in that chain, since a missing intermediate breaks validation for clients that won't fetch it themselves.
- Certificate Pinning — Certificate pinning constrains a client to accept only a specific certificate or public key for a given host, instead of trusting any certificate chaining to a trusted root, as formalized for HTTP in RFC 7469's Public-Key-Pins header. AdminKit's guide to certificate chain completeness explains the broader trust model pinning narrows.
- Certificate Transparency (CT) log — A Certificate Transparency (CT) log, defined in RFC 6962, is an append-only, publicly auditable record that every trusted certificate authority must publish each TLS certificate into before browsers treat it as valid. AdminKit's guide to monitoring CT logs explains how to catch a mis-issued certificate for your own domain.
- Cipher suite — A cipher suite is the specific combination of cryptographic algorithms a client and server negotiate for a TLS connection; RFC 8446 simplified TLS 1.3's naming to just an AEAD cipher plus a hash. AdminKit's SSL check tool shows the TLS version and cipher suite a live site actually negotiates.
- CoAP — CoAP (Constrained Application Protocol, RFC 7252) is a lightweight, RESTful protocol for low-power IoT and sensor devices, running over UDP instead of a full HTTP/TCP stack, often without its optional DTLS encryption enabled. AdminKit's port check tool can confirm whether a device's CoAP port is reachable from the internet, where it is a known DDoS amplification target.
- Content-Security-Policy (CSP) — Content-Security-Policy (CSP) is an HTTP response header, specified by the W3C, that lets a site allowlist which sources of scripts and other resources a browser may load, mitigating cross-site scripting. AdminKit's HTTP headers tool checks whether a site sends a Content-Security-Policy header, and what it actually allows.
- CRL (certificate revocation list) — A certificate revocation list (CRL) is a certificate authority's signed, periodically published list of certificate serial numbers it has revoked before their stated expiry, defined in RFC 5280's X.509 standard. AdminKit's SSL check tool shows a live certificate's details, including which revocation mechanism -- CRL or OCSP -- it actually references.
- CSR (Certificate Signing Request) — A CSR (Certificate Signing Request) is the file a server operator sends a certificate authority to request a TLS certificate, structured under RFC 2986's PKCS #10 format and signed with the matching private key. AdminKit's SSL check tool shows the certificate a CSR eventually becomes, as a live server presents it.
- DNP3 (Distributed Network Protocol 3) — DNP3 (Distributed Network Protocol 3), standardized as IEEE 1815, carries readings and control commands between a master station and field devices on electric, water and gas utility SCADA networks. AdminKit's Modbus/TCP check targets DNP3's sibling OT protocol, which shares the same often-disabled-authentication exposure on internet-facing industrial networks.
- Docker Remote API — The Docker Remote API (also called the Docker Engine API) is the HTTP interface the Docker daemon exposes for creating and inspecting containers, carrying no authentication of its own unless TLS client certificates are configured. AdminKit's port-exposure guide shows how to check whether your own Docker Engine API is reachable from the internet without one.
- Elasticsearch HTTP API — Elasticsearch exposes its search and cluster-administration functions through a JSON-over-HTTP API, by default on port 9200, Elastic's own documented default rather than an IANA-assigned port. Versions before 8.0 shipped with security disabled unless configured, which is why AdminKit's guide checks whether your own port 9200 is reachable without authentication.
- Encrypted ClientHello (ECH) — Encrypted ClientHello (ECH), defined in the IETF TLS working group's draft-ietf-tls-esni and built on TLS 1.3 (RFC 8446), encrypts the ClientHello so a network observer can no longer read the plaintext Server Name Indication. AdminKit's SSL/TLS check reports the handshake details a connection actually negotiates, including whether SNI is visible or ECH-protected.
- FTP (File Transfer Protocol) — FTP (RFC 959) is a decades-old protocol for transferring files between a client and server, typically on port 21, whose USER and PASS commands send a login's username and password as plain, unencrypted text. AdminKit's guide checks whether a device's FTP port is actually reachable from the public internet.
- Honeypot — A honeypot is a deliberately exposed decoy system set up to attract scanning and attack traffic so defenders can observe attacker behavior without risking any real system or data. AdminKit's protective DNS product uses this kind of sensor data, gathered by honeypot and sensor networks, to inform its blocklists.
- HSTS (HTTP Strict Transport Security) — HSTS (HTTP Strict Transport Security, RFC 6797) is a response header that tells a browser to reach a host only over HTTPS for a set number of seconds and to refuse certificate-error click-throughs. AdminKit's HTTP security headers check fetches a URL live and shows whether Strict-Transport-Security is sent, with its value.
- HSTS preload list — The HSTS preload list is a hardcoded browser list, maintained via hstspreload.org, that forces HTTPS from a domain's very first connection, closing a bootstrap gap in RFC 6797's HSTS header. Ordinary HSTS only protects a domain after a browser's first successful HTTPS visit. AdminKit's guide explains why preloading isn't recommended for every site.
- HTTP/3 — HTTP/3, defined in RFC 9114, is the first HTTP version to run over QUIC (RFC 9000) instead of TCP, so one lost packet only delays its own stream rather than stalling every multiplexed request. AdminKit's TLS certificate chain check validates the same chain concept that carries into the QUIC connection HTTP/3 runs on.
- LDAP — LDAP (Lightweight Directory Access Protocol, RFC 4511) queries directory services like Active Directory for user accounts and authentication data. Plain LDAP on port 389 sends bind credentials without encryption unless upgraded with STARTTLS or run over LDAPS (port 636), so AdminKit's port check tool can confirm a directory service isn't directly reachable from the open internet.
- Modbus/TCP — Modbus/TCP is the TCP/IP version of a decades-old industrial protocol used to read and write values on programmable logic controllers, typically over port 502, with no authentication, authorization or encryption built in. AdminKit's guide explains how to check whether a Modbus/TCP device is exposed to the internet.
- MongoDB wire protocol — The MongoDB wire protocol is the TCP message format MongoDB's own drivers and mongosh use to talk to a mongod or mongos process, normally on port 27017, documented in MongoDB's own manual rather than an independent spec. AdminKit's guide to checking an exposed MongoDB port explains why an internet-reachable 27017 usually means a deliberately widened bind address.
- MQTT — MQTT (Message Queuing Telemetry Transport) is a lightweight publish/subscribe messaging protocol built for constrained devices and unreliable networks, which is why it became the default choice for a huge range of IoT products. AdminKit's guide to checking an open MQTT broker explains why its default port, 1883, so often ships with no authentication at all.
- Mutual TLS (mTLS) — Mutual TLS (mTLS) is a TLS handshake where the server also requests and verifies a certificate from the client, authenticating both sides instead of only the server a normal HTTPS connection authenticates. AdminKit's guide to securing an MQTT broker covers when issuing a certificate per device is worth the operational cost over username and password alone.
- MySQL wire protocol — The MySQL wire protocol is the TCP message format MySQL's own client libraries use to connect, authenticate and exchange queries with a mysqld server, normally on port 3306. AdminKit's guide to checking an exposed MySQL port explains why a reachable 3306 has been a documented ransomware target since 2017.
- NTP (Network Time Protocol) — NTP (Network Time Protocol), defined in RFC 5905, synchronizes a device's clock against a hierarchy of time servers -- accuracy that DNSSEC quietly depends on, since RRSIG signatures expire on a wall-clock timestamp. AdminKit's glossary covers RRSIG, the DNSSEC record an inaccurate NTP clock can break.
- OCSP stapling — OCSP stapling lets a server prove its TLS certificate hasn't been revoked by attaching a signed, time-stamped response to the handshake itself, so the client doesn't have to query the certificate authority separately. AdminKit's SSL/TLS check shows a server's certificate and negotiated protocol, including whether stapling is enabled.
- OPC UA — OPC UA, defined in the IEC 62541 series, is an industrial protocol for PLCs, SCADA and sensors with authentication and encryption built in as configurable options -- unlike older protocols such as Modbus or BACnet. AdminKit OT remote access, delivered by Netbase, reaches OPC UA devices outbound-only.
- PEM format — PEM (Privacy-Enhanced Mail) format is the base64 text container -- BEGIN/END headers -- that most TLS certificates and keys are stored in, standardized for that reuse by RFC 7468. AdminKit's SSL check tool reads the certificate chain a server presents, typically distributed to it in PEM form.
- PKI (public key infrastructure) — Public key infrastructure (PKI), profiled for internet use in RFC 5280, is the system of certificate authorities, certificates and trust chains that lets a client verify a server's identity without ever sharing a secret in advance. AdminKit's SSL check tool verifies whether a site's certificate chains up to a trusted root, PKI's core guarantee.
- PostgreSQL wire protocol — The PostgreSQL wire protocol is the message format a client uses to connect, authenticate and query over TCP, normally on port 5432, documented as PostgreSQL's own frontend/backend protocol. AdminKit's guide checks whether your own PostgreSQL port 5432 is reachable from the internet, since the default binds only to localhost.
- QUIC — QUIC, defined in RFC 9000, is a transport protocol that runs over UDP and builds the TLS 1.3 handshake into connection setup, avoiding the head-of-line blocking TCP-based HTTP/2 can't escape. AdminKit's TLS check guide explains the handshake version your tool reports, over TCP, distinct from the one QUIC carries over UDP.
- RDP (Remote Desktop Protocol) — RDP (Remote Desktop Protocol) is Microsoft's protocol, specified in MS-RDPBCGR, for remotely controlling a Windows desktop over the network, typically on port 3389 -- one of the internet's most consistently attacked exposed ports. AdminKit's guide checks whether RDP is reachable from the public internet on a given host.
- RDP Network Level Authentication (NLA) — Network Level Authentication (NLA) makes an RDP client authenticate before Windows creates a full remote-desktop session, instead of presenting the login screen to any connection first. AdminKit's RDP hardening guide lists NLA as the first control to enable beyond simply closing port 3389 to the internet.
- Redis protected mode — Redis protected mode, a default Redis has shipped since version 3.2.0, restricts an unauthenticated instance with no bind address set to loopback-only connections, per Redis's own security documentation. AdminKit's guide explains why Redis ships without a password by default, and what protected mode does and doesn't cover.
- Referrer-Policy — Referrer-Policy is an HTTP header, specified by the W3C, that controls how much of a page's URL browsers send cross-origin in the Referer header when loading a resource or following a link elsewhere. AdminKit's HTTP security headers guide explains what each header result means, Referrer-Policy included.
- RESP (Redis Serialization Protocol) — RESP (REdis Serialization Protocol) is the simple, text-based wire protocol Redis clients and servers exchange commands and replies over, typically port 6379, with no authentication built into the protocol itself. AdminKit's guide to checking an exposed Redis port explains why an internet-reachable RESP connection with no password is immediately exploitable.
- RTSP — RTSP (Real-Time Streaming Protocol) is a control protocol IP cameras, NVRs and video doorbells use to negotiate a live video stream, typically on port 554, with no mandatory authentication or encryption of its own. AdminKit's guide explains how to check whether a camera's RTSP port is exposed to the internet.
- SAN (Subject Alternative Name) — SAN (Subject Alternative Name), defined in RFC 5280, is the X.509 certificate extension listing every hostname a certificate actually covers -- the field browsers check for a match, not the legacy subject Common Name. AdminKit's SSL checker shows the exact SAN list a live certificate presents.
- Self-signed certificate — A self-signed certificate is an X.509 certificate whose issuer and subject are the same entity, signed with its own key rather than a certificate authority, so no trust chain backs it. AdminKit's SSL checker tool reports whether a live certificate is self-signed or chains to a publicly trusted root.
- SIP (Session Initiation Protocol) — SIP (Session Initiation Protocol, RFC 3261) is the signalling protocol IP phones, softphones and voice gateways use to register, set up, change and end calls, by default on port 5060 over UDP or TCP and 5061 over TLS. AdminKit's port check does not test SIP ports; its fixed list covers nine other TCP ports.
- SMB (Server Message Block) — SMB (Server Message Block) is Microsoft's protocol for sharing files, printers and some remote administration between machines on a local network, most commonly reached on TCP port 445. AdminKit's guide explains why CISA still tells every network to block SMB at the internet-facing perimeter entirely.
- SNMP — SNMP (Simple Network Management Protocol) monitors and configures routers, switches and other network equipment by reading and writing values from a device's management database, often using a plaintext community string left at its default. AdminKit's Port Check tool checks whether this kind of weakly authenticated management protocol is reachable from outside.
- SSDP — SSDP (Simple Service Discovery Protocol) is the UPnP discovery mechanism devices use to announce themselves over multicast UDP on port 1900 within a local network, which becomes a UDP amplification risk if a router answers SSDP from the public internet. AdminKit's Port Check tool checks whether port 1900 is reachable from outside.
- Subresource Integrity (SRI) — Subresource Integrity (SRI) lets a web page specify a cryptographic hash a fetched script or stylesheet must match before the browser executes it, blocking a tampered file from a CDN or third-party host. AdminKit's guide to judging header strength covers the related script-trust problem Content-Security-Policy addresses from the response side.
- Telnet — Telnet (RFC 854) is a decades-old protocol for opening a remote terminal session, typically on port 23, that carries no encryption at all -- a username, password, and every keystroke travel in plain text. AdminKit's guide checks whether a device's Telnet port is actually reachable from the public internet.
- TLS handshake — The TLS handshake is the message exchange, compressed to one round trip by TLS 1.3 (RFC 8446), in which a client and server agree a cipher suite, the server proves its identity with a certificate, and both derive session keys. AdminKit's SSL checker reports the negotiated version and cipher suite a live handshake completes with.
- TLS SNI (Server Name Indication) — Server Name Indication (SNI), defined in RFC 6066, is a TLS extension letting a client state the hostname it wants inside the cleartext ClientHello, so a server hosting multiple HTTPS sites on one IP can pick the right certificate. AdminKit's SSL checker shows which certificate a server actually presents for a hostname.
- TR-069 — TR-069, also called CWMP (CPE WAN Management Protocol), is a standard ISPs use to remotely configure and update customer routers and modems, typically on port 7547. Reachable from the public internet instead of just the ISP's own network, a misconfigured TR-069 service has caused real router-compromise incidents, which is exactly what AdminKit's port check tool can help confirm.
- UPnP — UPnP (Universal Plug and Play) lets devices on a local network discover each other and open port-forwarding rules on the router automatically, without the owner reviewing each request. AdminKit's port check tool shows which ports are open on your connection, including ones UPnP may have opened without your knowledge.
- VNC (Virtual Network Computing) — VNC is a cross-platform protocol for remotely viewing and controlling another computer's graphical desktop, built on the RFB protocol (RFC 6143) and typically reachable on port 5900. Its classic authentication truncates passwords to 8 characters, a legacy weakness the RFC itself documents -- AdminKit's port-exposure guide covers checking whether a device's VNC port is reachable at all.
- Well-known URI — A well-known URI is a resource published at a path beginning /.well-known/ on a host, under the registry RFC 8615 establishes so a new protocol can define a discoverable location for site-wide metadata. AdminKit's MCP server hardening checklist requires publishing OAuth metadata at two separate well-known URIs.
- X.509 certificate — An X.509 certificate is the standardized data structure, defined in RFC 5280, that binds a public key to an identity and is signed by the certificate authority that issued it. Every TLS certificate AdminKit's SSL/TLS check tool inspects is an X.509 certificate, carrying a subject, issuer, validity period and Subject Alternative Name list.
- Zero trust — Zero trust is a security model built on the assumption that no device, user or network segment should be trusted by default, including ones already inside a traditional perimeter -- every request is authenticated and authorized on its own merits. AdminKit OT remote access, delivered by Netbase, replaces an open inbound port with outbound-only, zero-trust access.
Comparisons (0)
All comparisons →No comparisons in this cluster yet — see the full comparisons list.
Related clusters
AI agents & MCP
The Model Context Protocol lets AI agents call tools and read resources over a network connection, which means an unauthenticated or misconfigured MCP server can hand an agent — or an attacker — more access than intended.
Security basics
TLS certificates, HTTP security headers and open ports are the fundamentals every internet-facing service should get right, independent of which protocol, operating system or cloud provider it runs on — most breaches start with one of these basics left unchecked.
Frequently asked questions
Why is exposing Modbus or MQTT directly to the internet risky?
Both protocols were designed for trusted local networks: classic Modbus TCP has no built-in authentication or encryption at all, and MQTT's authentication and TLS are optional broker configuration, not a protocol requirement — a device or broker left reachable from the internet with defaults intact will accept commands or subscriptions from anyone who finds it. NIST SP 800-82 covers this exposure pattern across operational technology protocols generally.
Does MQTT have security built in?
The MQTT v5.0 OASIS standard defines authentication (username/password, enhanced auth) and supports running over TLS, but both are optional — a broker can be deployed with no credentials and no encryption and still be a fully valid MQTT v5.0 implementation. The protocol doesn't force a secure default; the broker operator has to turn authentication and TLS on.
What port does Modbus use, and is it authenticated by default?
Modbus TCP listens on port 502 by default and has no authentication, authorization or encryption defined in the protocol — any client that can reach port 502 can issue read and write function codes. AdminKit's Modbus exposure check looks specifically for port 502 reachable from the public internet, which is the condition that matters in practice.