Skip to content
Pricing RU Sign In
RU

Port 8554 — RTSP

By · Updated
Key idea:

TCP/8554 — a widely used alternate port for RTSP (Real-Time Streaming Protocol). The standard is 554 (RFC 2326), but 8554 is popular for test servers (GStreamer rtsp-simple-server), secondary instances, and CGNAT bypass. Used by IP cameras, video conferencing, live streaming. Security: digest auth at minimum, TLS via RTSPS (322/8322).

Below: details, example, related, FAQ.

Try it now — free →

Details

  • RTSP is a "remote control" for media streams, not data transport (RTP uses other ports)
  • URL schema: rtsp://user:pass@192.168.1.10:8554/stream1
  • ONVIF cameras often expose 8554 for an alternate profile
  • FFmpeg, VLC, GStreamer — all speak rtsp:// URIs
  • WebRTC is pushing RTSP out of web apps, but IP cameras still run RTSP

Example

# Check stream with ffmpeg
$ ffmpeg -rtsp_transport tcp -i rtsp://admin:pass@192.168.1.10:8554/live -frames 1 test.jpg

# GStreamer play
$ gst-launch-1.0 rtspsrc location=rtsp://192.168.1.10:8554/live ! decodebin ! autovideosink

# Nmap scan
$ nmap -p 8554 --script rtsp-url-brute 192.168.1.10

Related

Related guides

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
<2s
result
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

Related tools

TracerouteDNS LookupWHOISSSL Check

Frequently Asked Questions

Why 8554 specifically?

Often — a user-space alternative to privileged 554. Standalone servers without root use 8554 / 8888 / 10554.

RTSP security?

Digest auth + IP whitelist. Real security — TLS tunnel (stunnel / nginx-rtmp-module) or WebRTC + SRTP.

Replace RTSP?

Browser — WebRTC or HLS. IP cameras and professional video — RTSP for another 5+ years.

Start monitoring for free

Sign up and get access to API, monitoring and notifications

Create Account API Documentation