Skip to content

Port 8883 — MQTT over TLS

Key idea:

TCP/8883 — standard port for MQTT over TLS (encrypted). MQTT (Message Queuing Telemetry Transport) — pub/sub protocol for IoT: sensors → broker → apps. Plain MQTT = TCP/1883. 8883 adds TLS 1.2/1.3 + usually X.509 client certs (mutual TLS). Used by: AWS IoT Core, Azure IoT Hub, HiveMQ, Mosquitto.

Below: details, example, related, FAQ.

Try it now — free →

Details

  • MQTT 5.0 (2019) — shared subscriptions, enhanced auth, user properties
  • QoS 0/1/2: fire-and-forget, at-least-once, exactly-once
  • Retained messages: broker keeps the latest per topic
  • Will message: notifies of client disconnect
  • mTLS: client-cert for device authentication — IoT industry standard

Example

# mosquitto_pub with TLS
$ mosquitto_pub -h broker.example.com -p 8883 \
    --cafile ca.crt --cert client.crt --key client.key \
    -t sensor/temperature -m "23.5"

# Python paho-mqtt
import paho.mqtt.client as mqtt
c = mqtt.Client()
c.tls_set('ca.crt', 'client.crt', 'client.key')
c.connect('broker.example.com', 8883)
c.publish('sensor/temperature', '23.5')

Related

Understanding MQTT Security with Port 8883

Common Use Cases for Port 8883 in IoT Applications

Configuring MQTT Clients to Use Port 8883

CertificateExpiry, issuer, domains (SAN)
ChainIntermediate and root CA validation
TLS ProtocolTLS version and cipher suite
VulnerabilitiesHeartbleed, POODLE, weak ciphers

Why teams trust us

TLS 1.3
supported
Full
CA chain check
<2s
result
30/14/7
days-to-expiry alerts

How it works

1

Enter domain

2

TLS chain verified

3

Expiry date & vulnerabilities

What Does the SSL Check Cover?

SSL/TLS is the encryption protocol that protects data between the browser and server. Our tool analyzes the certificate, chain of trust, TLS version, and knownvulnerabilities.

Certificate Details

Issuer, validity period, signature algorithm, covered domains (SAN), and validation type (DV/OV/EV).

Chain of Trust

Full chain verification: from leaf certificate through intermediates to root CA.

TLS Analysis

Protocol version (TLS 1.2/1.3), cipher suites, Perfect Forward Secrecy (PFS) support.

Expiry Alerts

Set up a monitor — get Telegram and email alerts 30/14/7 days before expiration.

DV vs OV vs EV Certificates

DV (Domain Validation)
  • Confirms domain ownership only
  • Issued in minutes automatically
  • Free via Let's Encrypt
  • Suitable for most websites
  • Most common certificate type
OV / EV
  • Organization (OV) or Extended Validation (EV)
  • Issued in 1-5 business days
  • Costs $50 to $500/year
  • For finance, e-commerce, government sites
  • Increases user trust

Who uses this

DevOps

SSL certificate monitoring

Security

TLS config audit

SEO

HTTPS as ranking factor

E-commerce

customer trust

Common Mistakes

Expired certificateBrowsers block sites with expired SSL. Set up auto-renewal or monitoring.
Incomplete certificate chainWithout intermediate CA, some browsers and bots cannot verify the certificate.
Mixed content on HTTPS siteHTTP resources on an HTTPS page — the browser lock icon disappears, reducing trust.
Using TLS 1.0/1.1Legacy TLS versions have known vulnerabilities. Use TLS 1.2+ or 1.3.
Domain mismatch in certificateThe certificate must cover all site domains, including www and subdomains.

Best Practices

Set up auto-renewalLet's Encrypt + certbot with cron — certificate renews automatically every 60-90 days.
Enable HSTSStrict-Transport-Security header forces browsers to always use HTTPS.
Use TLS 1.3TLS 1.3 is faster (1-RTT handshake) and safer — legacy ciphers removed.
Monitor expiration datesCreate a monitor on Enterno.io — get notified well before expiration.
Verify chain after renewalAfter certificate renewal, confirm that intermediate certificates are installed.

Get more with a free account

SSL certificate monitoring, check history and alerts 30 days before expiry.

Sign up free

Learn more

Frequently Asked Questions

MQTT vs HTTP for IoT?

MQTT: persistent connection, pub/sub, tiny header (~2 bytes). HTTP: simpler, RESTful, each request = handshake. Low-traffic, battery-powered IoT — MQTT.

MQTT 5 vs 3.1.1?

5.0 adds enhanced auth, user properties, session expiry. Adoption: AWS IoT Core 2024, Mosquitto 2, HiveMQ 4+.

Do I need a client cert?

Production — yes, mutual TLS. Plain username/password breaks once device fleet hits 10k+.

Try the live tool that powered this guide

Free plan — 20 monitors, 5-minute checks, no card required. Upgrade for 1-minute interval and multi-region monitoring.