Most recent
navigate open esc close Corpus index built 2026-06-07 23:58 UTC

← All reference

Reference

Common AI/LLM Infrastructure Ports

Source: https://github.com/nuclide-research/AI-LLM-Infrastructure-OSINT/blob/main/reference/ports

Cross-cutting port reference for AI/ML-adjacent services. Useful for Shodan/Censys/FOFA queries, nmap/naabu scan prioritization, firewall audits, and asset discovery.

Sorted numerically. Where a port hosts multiple AI/ML services, the primary ones are listed first.

Quick-Reference Table

PortService(s)Notes
80 / 443Generic HTTP(S), Dify, Flowise, reverse-proxied everythingFilter by http.title: / HTML fingerprint
1337Jan, DevikaHacker-cute defaults
1984LangSmith
2375Docker daemon (unauth)RCE → host foothold
2379etcd (Milvus metadata), Kubernetes control plane
3000Flowise, Open WebUI, AnythingLLM, AgentGPT, SuperAGI, Langfuse, Promptfoo, OpenDevin, GrafanaMost crowded port in AI
3001AnythingLLM
4000LiteLLM ProxyProvider keys live here
4040Apache Spark UIOften co-deployed with ML pipelines
4317OpenTelemetry gRPC (OTLP)LLM observability transport
4318OpenTelemetry HTTP (OTLP)LLM observability transport
4567Rivet
5000MLflowModels, artifacts, experiments
5001KoboldCpp
5050pgAdminOften default creds
5432PostgreSQL + pgvector, Supabase, Neon, Timescale
5500ChromaDB (alt)
5601Kibana, OpenSearch DashboardsVector index admin
5678n8nAI workflow automation
6006Phoenix/Arize, TensorBoardTraces + training viz
6333Qdrant (HTTP)Snapshots downloadable
6334Qdrant (gRPC)
6379Redis / Redis Stack (vector search)Often no auth
6443Kubernetes API serverML workload orchestration
6900ArgillaRLHF/annotation data
7474Neo4j BrowserGraph memory stores
7501Lightning AI
7687Neo4j Bolt, Memgraph
7860Gradio, LangFlow, unsloth, text-generation-webuiHuggingFace Spaces default
7997Infinity (embeddings)
8000LangChain, vLLM, Triton, FastAPI generic, ChromaDB, AutoGPT, BentoML, Ray Serve, MetaGPT, Mem0, many /v1/* OpenAI-compatSingle most common LLM port
8001RedisInsight
8008ClearML
8080LocalAI, llama.cpp, Vespa, BabyAGI, Axolotl, Determined AI, Kubeflow, Airflow, Helicone, Dgraph, NVIDIA, Vast.ai, HF TEI/TGI, PhidataGeneric “alt-HTTP”
8081mongo-express
8088Hadoop YARN ResourceManagerTraining data pipelines
8089Splunk HECSometimes LLM log sink
8108TypesenseAPI key enumeration risk
8123LangGraph Studio, ClickHouse
8161ActiveMQ Web ConsoleML pipeline message broker
8265Ray DashboardCluster job submission, RCE
8443SageMaker Notebook, alt-HTTPS
8501Streamlit
8529ArangoDB
8787Cloudflare AI Gateway, Portkey, RStudio Server
8882Marqo
8888Jupyter, RunPodRCE if no token
9000MinIO (Milvus backing), PortainerVector blobs in buckets
9090PrometheusEvery ML stack exports metrics here
9091Milvus metrics, Zilliz
9092Apache KafkaLLM event streams, training pipelines
9200Elasticsearch / OpenSearchdense_vector / kNN
9400NVIDIA DCGMGPU telemetry
9870Hadoop NameNode (HDFS)Training data at rest
9998Apache TikaDocument ingestion
10250KubeletK8s node attack surface
11434OllamaMost-exposed LLM runtime in 2025-26
19530Milvus (gRPC)
27017MongoDBIncreasingly used as vector store
50070Hadoop NameNode (legacy)

Patterns Worth Knowing

Highest-yield single-port queries

  • port:11434, catches tens of thousands of unauth Ollama instances. Model-naming leaks org context (e.g. acme-internal-rag:latest discloses tenant identity before authenticating).
  • port:7860, Gradio/HuggingFace Spaces ecosystem; favicon hash -1294819032 catches reverse-proxied instances that strip the title.
  • port:8000 + "/v1/chat/completions", OpenAI-compatible endpoint regardless of underlying engine. vLLM, LM Studio, llama.cpp, LocalAI, text-generation-webui all collapse into this.
  • port:6006, historically TensorBoard, now also Phoenix/Arize for LLM traces. Same port, very different exposure surface: training metrics vs. live prompt/response logs.

Port ranges by deployment pattern

  • Enthusiast / self-hosted: 1337, 4567, 7501, 8123, 11434, less likely to have org-grade auth.
  • Production-ish web UIs: 3000, 8080, 7860, SaaS-flavored, sometimes wrapped in Cloudflare but often not.
  • Data plane (never meant to be public): 5432, 6379, 9200, 19530, 27017, direct database exposure = bypass of any auth layer the app imposes.
  • Control / admin planes: 2375, 2379, 6443, 8265, 9000, one of these exposed means the entire workload is owned.

Co-location signals

If you see these ports together on one host, infer the stack:

  • 11434 + 3000 → Ollama + Open WebUI (self-hosted private ChatGPT)
  • 6333 + 8000 + 4000 → Qdrant + a RAG app + LiteLLM proxy
  • 5000 + 8265 + 9400 → MLflow + Ray + NVIDIA DCGM (training cluster)
  • 9200 + 5601 + 3000 → Elasticsearch + Kibana + Langfuse (RAG observability stack)
  • 8888 + 8265 → Jupyter + Ray (notebook-driven ML cluster)

Ports that are always worth a second look

PortWhy
2375Unauth Docker daemon = host RCE via /containers/create
8265Ray cluster job submission = arbitrary code execution across GPU nodes
6443 / 10250K8s API / Kubelet = full workload control if unauth
11434Ollama exposes /api/generate → free inference + model enumeration
4000LiteLLM proxy admin UI leaks master provider keys if misconfigured

Scanning Tips

# Fast first-pass of common AI ports with naabu
naabu -host <target> -p 2375,3000,4000,5000,5432,6006,6333,6379,7860,8000,8080,8265,8888,9090,9200,11434,19530

# Nmap service detection on the long list
nmap -sV -p 80,443,1337,1984,2375,2379,3000,3001,4000,4040,4317,4318,4567,5000,5001,5050,5432,5500,5601,5678,6006,6333,6334,6379,6443,6900,7474,7501,7687,7860,7997,8000,8001,8008,8080,8081,8088,8089,8108,8123,8161,8265,8443,8501,8529,8787,8882,8888,9000,9090,9091,9092,9200,9400,9870,9998,10250,11434,19530,27017,50070 <target>

# Shodan facet to see which ports dominate a given org
shodan search --facets port org:"Example Inc" "api" | head

Contributing

New AI-adjacent port? Open a PR adding a row (keep sorted numerically) with the service name and a Notes column entry when the exposure has non-obvious impact. See CONTRIBUTING.md.