explaingit

internetkafe/deathcore

Analysis updated 2026-05-18

179GoAudience · ops devopsComplexity · 4/5Setup · moderate

TLDR

A Go command line tool for load testing your own VLESS proxy servers by opening large numbers of concurrent encrypted connections.

Mindmap

mindmap
  root((deathcore))
    What it does
      VLESS load testing
      High connection concurrency
      Post quantum encryption
    Tech stack
      Go
      Xray-core
      VLESS protocol
    Use cases
      Server capacity testing
      Transport config testing
      Silent unattended runs
    Audience
      Server operators
    Caution
      Authorized targets only
      Illegal if misused

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Check how many concurrent connections a VLESS proxy server can handle before it degrades.

USE CASE 2

Load test a Reality or XHTTP transport configuration before relying on it in production.

USE CASE 3

Verify post-quantum encryption settings work under many simultaneous connections.

USE CASE 4

Run silent, unattended load tests and review live connection statistics.

What is it built with?

GoXray-coreVLESS

How does it compare?

internetkafe/deathcoresphireinc/foundrypgrwl/pgrwl
Stars179183159
LanguageGoGoGo
Setup difficultymoderatemoderatemoderate
Complexity4/53/54/5
Audienceops devopsdeveloperops devops

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 30min

Only intended for servers you own or have explicit permission to test, per the README's own disclaimer.

The available README content does not state a license.

In plain English

Deathcore is a command line load testing tool written in Go that generates very high volumes of network traffic through VLESS tunnels, a proxy protocol used in tools like Xray-core. The README frames it explicitly as a stress and load testing tool, and it opens with a disclaimer stating it should only be used on servers the operator owns or has explicit permission to test, and that unauthorized use may be illegal. According to the README, deathcore takes a VLESS connection URL, parses its parameters automatically, and opens a large number of concurrent encrypted connections using goroutines, Go's lightweight concurrency feature. It supports several transport methods including XHTTP, gRPC, and the Reality TLS obfuscation feature, along with post quantum key exchange using a combination of ML-KEM768 and X25519. The README lists three attack modes: a raw byte flood mode, an HTTP mode using custom request templates, and a gRPC mode using protocol buffer messages. It also describes automatic reconnection after a dropped connection, an optional live statistics display showing connection counts and bytes sent, a silent mode that disables logging entirely, and a build process that compiles to a single executable file with one go build command. Because deathcore is built on the existing Xray-core project, the README states it does not need to implement VLESS protocol handling itself. The tool is intended for people who already run VLESS based infrastructure and want to load test their own servers before relying on them in production, such as checking how many concurrent connections a proxy setup can handle before it degrades or fails. The README does not state a license for the project.

Copy-paste prompts

Prompt 1
Explain what each of deathcore's attack modes, flood, http, and grpc, actually does differently.
Prompt 2
Walk me through building deathcore from source with a single go build command.
Prompt 3
What does the Reality TLS obfuscation feature this tool supports actually protect against?
Prompt 4
Help me understand the legal and ethical boundaries around load testing tools like this one.

Frequently asked questions

What is deathcore?

A Go command line tool for load testing your own VLESS proxy servers by opening large numbers of concurrent encrypted connections.

What language is deathcore written in?

Mainly Go. The stack also includes Go, Xray-core, VLESS.

What license does deathcore use?

The available README content does not state a license.

How hard is deathcore to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is deathcore for?

Mainly ops devops.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.