Skip to content
RU

Port 6380: Redis over TLS

Key idea:

Port 6380 (TCP) is the standard for Redis over TLS. Redis 6+ supports TLS on a separate port (usually 6380) alongside plain 6379. Cloud hosters (AWS ElastiCache, Redis Cloud, Yandex) expose only the TLS port — plain 6379 is off.

Below: what uses this port, security considerations, online check, FAQ.

Check your host & ports →

What runs on this port

Redis over TLS

Redis 6+ supports TLS on a separate port (usually 6380) alongside plain 6379. Cloud hosters (AWS ElastiCache, Redis Cloud, Yandex) expose only the TLS port — plain 6379 is off.

Security considerations

Redis without TLS = all commands + AUTH password in plain text. TLS (port 6380) + requirepass mandatory for public-facing Redis.

Check this port online

Check port online →

Enterno.io Ping + Port checker tests TCP reachability of any port from 3 regions (Moscow / Frankfurt / Virginia).

Understanding Redis over TLS Configuration

Configuring Redis to use TLS on port 6380 involves several steps to ensure secure communications between clients and the Redis server. Below is a step-by-step guide:

  • Install Redis 6 or later: Ensure that you are using a version of Redis that supports TLS. You can download it from the official Redis website.
  • Generate SSL Certificates: You will need a server certificate, a private key, and a certificate authority (CA) certificate. Use the following OpenSSL commands to create a self-signed certificate:
openssl req -new -x509 -days 365 -nodes -out redis-server-cert.pem -keyout redis-server-key.pem
  • Configure Redis for TLS: Edit the Redis configuration file (usually redis.conf) to include the following parameters:
tls-port 6380
tls-cert-file /path/to/redis-server-cert.pem
tls-key-file /path/to/redis-server-key.pem
tls-ca-cert-file /path/to/ca-cert.pem
  • Start Redis: Launch Redis with the modified configuration file:
redis-server /path/to/redis.conf

Once configured, Redis will only accept secure connections on port 6380. It is recommended to disable the non-TLS port (6379) for added security.

Common Use Cases for Port 6380 in Redis

Port 6380 is primarily used for secure connections to Redis servers, especially in cloud environments. Here are some common use cases:

  • Cloud Database Services: Providers like AWS ElastiCache and Redis Cloud exclusively expose port 6380 for secure access. This ensures all data transmitted between your application and Redis is encrypted.
  • Microservices Architecture: In microservices environments, where multiple services interact with Redis, using TLS on port 6380 helps maintain data integrity and confidentiality across service boundaries.
  • Data Ingestion Pipelines: For applications that process sensitive data, such as personal information or financial transactions, using Redis over TLS on port 6380 safeguards against eavesdropping and man-in-the-middle attacks.
  • Regulatory Compliance: Organizations subject to regulations like GDPR or HIPAA may require encryption for data in transit. Utilizing Redis over TLS on port 6380 can help meet these compliance standards.

By adopting port 6380 for Redis, businesses can enhance security while ensuring reliable data management across various applications.

Testing and Diagnosing TLS Connection on Port 6380

To ensure that your Redis instance is correctly configured to accept TLS connections on port 6380, you can perform a series of tests using command-line tools. Here’s how you can test and diagnose the TLS connection:

  • Using OpenSSL: You can test the TLS connection by running the following command:
openssl s_client -connect your-redis-server:6380 -tls1_2

This command attempts to establish a secure connection to your Redis server. Look for the Verify return code: 0 (ok) message, which indicates that the TLS certificate is valid.

  • Redis CLI with TLS: If you have the Redis CLI configured for TLS, you can connect using:
redis-cli -h your-redis-server -p 6380 --tls

Once connected, you can run Redis commands securely. If you encounter any connection issues, make sure to check the following:

  • Ensure that your Redis server is running and listening on port 6380.
  • Verify that the certificates are correctly specified in your redis.conf file.
  • Check firewall settings to ensure that port 6380 is open and accessible.

By following these steps, you can effectively diagnose and validate your Redis TLS setup on port 6380.

ICMP PingHost availability and latency
Port ScannerOpen TCP port detection
LatencyResponse time in milliseconds
Packet LossPercentage of dropped packets

Why teams trust us

ICMP+TCP
check protocols
14
key ports scanned
2,014
checks in 30 days
3
regions

How it works

1

Enter IP or domain

2

ICMP packets sent

3

Latency & packet loss shown

How Do Ping and Port Scanning Work?

Ping sends ICMP packets to a host and measures response time. Port scanning checks which TCP ports are open and accepting connections — helping diagnose serviceavailability issues.

Configurable Ping

Choose packet count (3, 4, 6, 10). Stats: min/avg/max latency and packet loss.

Common Port Scanner

Check 14 key ports: HTTP, HTTPS, SSH, FTP, SMTP, MySQL, PostgreSQL, and more.

Cloud-Based Check

Testing from our server — see site availability from outside, not just your local network.

Uptime Monitoring

Need constant monitoring? Create a monitor — checks every minute with notifications.

Who uses this

DevOps

availability diagnosis

Network engineers

TCP port scanning

Developers

connection debugging

SRE

basic health check

Common Mistakes

ICMP blocked = server is downMany servers block ICMP. Ping fails but site works — check ports instead.
High ping = server problemLatency depends on geography. 150ms between continents is normal, not an error.
Closed ports — cause for alarmClosed ports of unused services are good. Unnecessary open ports are a risk.
One check = sufficientNetworks are unstable. A single timeout ≠ a problem. Check multiple times or set up monitoring.

Best Practices

Combine ping and port checksPing shows host availability, ports show specific service availability. Use both.
Check from different locationsThe problem may be local. A cloud test shows the real picture.
Close unused portsEvery open port is a potential attack vector. Keep only necessary ports open.
Set up monitoringManual checks do not scale. Set up automated monitoring with notifications.

Get more with a free account

Ping check history, host availability monitoring and downtime alerts.

Sign up free

Learn more

Frequently Asked Questions

Is port 6380 open by default?

No, modern cloud providers (AWS, Google Cloud, Yandex) close all incoming ports by default. You must explicitly allow port 6380 in a Security Group or firewall.

How to check if port 6380 is reachable?

Use Enterno Ping + Port Checker. Or in shell: nc -vz example.com 6380.

Is port 6380 safe to expose?

Depends on the service. Redis over TLS should never be exposed publicly without authentication + TLS. See our 2026 exposure research.

Try the live tool that powered this guide

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