Network inventory · evidence by version

Every connection needs a reason.

This is the network map for Luczystrap—not a generic list of domains. It separates traffic attributed to the official 1.4.9 process, routes found in public 1.3 code, optional integrations, and unresolved artifacts.

Direct answer: a 150-second Windows sandbox run of the official 1.4.9 SHA-256 observed Luczystrap connecting to setup.rbxcdn.com, api.github.com, and clientsettingscdn.roblox.com. That is a verified minimum, not a complete firewall allowlist: the run did not exercise every feature.
Flight recorder · 1.4.9Process attributed
GETsetup.rbxcdn.comRoblox version and package manifest200
GETapi.github.comLatest Luczystrap release metadata200
GETclientsettingscdn.roblox.comWindowsPlayer client version200
3app hosts shown
150stest window
0network threats

Scope: one automated startup workflow. The report counted 11 HTTP(S) requests overall, including unrelated Windows processes.

01 / What the current capture proves

Observed traffic, with a boundary.

The sample hash matches the official GitHub 1.4.9 asset. ANY.RUN enabled networking and a MITM proxy, ran the task for 150 seconds, and reported connections by process. It also warns that sandbox results can be affected by the environment and user actions.

Attributed to Luczystrap.exe

Current observation
  1. 01
    Roblox deployment

    setup.rbxcdn.com/version and a version-specific package manifest returned successfully.

  2. 02
    Luczystrap release check

    GitHub’s public latest-release route returned metadata for Luc6i/Luczystrap.

  3. 03
    Roblox client version

    The WindowsPlayer version endpoint on clientsettingscdn.roblox.com returned successfully.

What it does not prove

Absence from a short run is not absence from the app.

The sandbox did not join a Roblox server, enable location or uptime, use Account Switcher, install plugins, run custom integrations, or exercise every update and fallback path.

No complete feature coverage

Conditional endpoints may remain dormant until their setting or workflow is used.

No payload disclosure for TLS

The public table establishes routes and methods, not a complete field-by-field body for every request.

No permanent allowlist

Service hosts and application behavior can change in a later release.

02 / Endpoint inspector

Choose a route. See its purpose.

The inspector answers six practical questions: who owns the service, what triggers it, which identifiers may leave the PC, whether it is optional, and which version establishes the claim.

Endpoint or transport

Observed in 1.4.9

Roblox deployment CDN

The current sandbox observed a version check and a package-manifest request. Historical code used the same service family to test connectivity, choose a working deployment host, retrieve manifests, and download Roblox packages.

GEThttps://setup.rbxcdn.com/version · /version-{guid}-rbxPkgManifest.txt
Service ownerRoblox deployment infrastructure
TriggerStartup, Roblox version check, install or update
Data or parametersRequested version or package path; ordinary connection metadata
Can it be disabled?Blocking it can prevent Roblox version detection, install or update
Evidence1.4.9 sandbox + public 1.3 Deployment and Bootstrapper code
Current confidenceObserved host and request path; broader workflow inferred from historical code

Decision: treat as functional traffic for Roblox deployment. Do not label it analytics.

03 / Full working inventory

One table, three evidence classes.

Rows marked “observed” were attributed to the current process in the public 1.4.9 run. Historical rows come from public tag 1.3. “Unresolved” means the artifact exists but its runtime behavior has not been explained.

Host / transportPurposeRequest contextControl or failureEvidence
setup.rbxcdn.comRoblox version, manifest and packagesGET version and version-specific manifest observedBlocking can break detection, install or update1.4.9 observed
api.github.comLatest Luczystrap release metadataGET public repository latest-release route observedMay disable or break the update check; exact current toggle unverified1.4.9 observed
clientsettingscdn.roblox.comCurrent WindowsPlayer versionGET client-version route observedBlocking can prevent Roblox version resolution1.4.9 observed
setup-aws.rbxcdn.com
setup-ak.rbxcdn.com
roblox-setup.cachefly.net
s3.amazonaws.com/setup.roblox.com
Fallback Roblox deployment mirrorsHistorical connectivity tests, manifests and packagesMay be contacted when the preferred host fails1.3 source
clientsettings.roblox.comFallback client-version and settings serviceHistorical fallback after CDN request failureBlocking removes that fallback path1.3 source
config.luczystrap.appRemote project data cached as Data.jsonHistorical GET on startup unless ForceLocalData was enabledHistorical ForceLocalData used the local copy; current host/status unverified1.3 source
games.roblox.com
thumbnails.roblox.com
Experience metadata, icons and thumbnailsUniverse/place IDs and thumbnail request objectsDisable activity/presence context; images or game details may disappear1.3 source
users.roblox.comUser details and historical Account Switcher validationUser ID; authenticated route historically received the session cookie headerDo not use Account Switcher or enter .ROBLOSECURITY1.3 source
ipinfo.ioApproximate Roblox server locationRoblox server IP embedded in the lookup path; city/region/country returnedLeave server details/location offOptional · 1.3
apis.rovalra.comEstimated server first-seen timeGET and POST with place ID and server/job IDLeave server uptime offOptional · 1.3
Discord desktop RPCPublish Rich Presence locally to DiscordExperience, session time, images; optional account and join contextDisable Rich Presence and its optional fieldsOptional · 1.3
discord.com/api/webhooks/…Purpose and payload not disclosedCredential-like artifact reported statically; no matching runtime request shownNot suitable for an allowlist until the maintainer explains and removes or rotates itUnresolved 1.4.9

This inventory intentionally excludes documentation links opened by a user, such as Discord invites, help pages and source links. It also excludes endpoints belonging only to unrelated Windows processes in the sandbox.

04 / Process attribution

A packet is not automatically Luczystrap.

The sandbox recorded network activity from several processes. Counting every DNS request on the virtual machine as Luczystrap behavior would falsely assign Windows activation, certificate checks and search traffic to the app.

Use the process column. A domain list without process ownership, workflow timing and a clean baseline is not an endpoint audit.

Luczystrap.exe

Three hosts shown in the public connection table

Roblox deployment CDN, GitHub API and Roblox client-settings CDN.

In scope
svchost.exe

Microsoft certificate-revocation traffic

crl.microsoft.com belonged to Windows service activity, not the Luczystrap process.

OS background
slui.exe

Windows activation traffic

The Microsoft activation route was associated with the Windows activation client.

OS background
SearchApp.exe

Windows search traffic

Bing traffic belonged to the Windows Search application in the sandbox.

OS background
Unknown / shared

DNS or connection without useful attribution

Keep it unassigned until a repeatable workflow and process owner establish the source.

Do not guess

05 / Allow or block

Control features, not just domains.

A firewall is useful for testing, but a static allowlist can age quickly. Start by disabling the feature that creates the route, then use a temporary network rule to confirm the result.

Functional routes

Expect Roblox and update traffic.

Deployment CDN and client-version services support installing and updating Roblox. GitHub supplies Luczystrap release metadata. Blocking these routes can trade privacy for broken updates or launches.

Optional routes

Disable the feature first.

Server location, uptime, Discord presence, Account Switcher, plugins and custom integrations have separate data surfaces. Leave each off unless its benefit is intentional.

Unresolved route

Do not normalize the unknown.

The reported embedded webhook needs an owner explanation, field list, trigger, consent rule and retention statement. A static detection is not proof of use, but it is not an allowlist entry either.

06 / Reproduce on Windows

Capture one workflow at a time.

Use Windows Packet Monitor for the packet record and Microsoft Sysinternals TCPView for process ownership. Test a clean startup first, then repeat separately for install/update, launch, Discord, location, uptime and any plugin.

Keep raw captures private. A system-wide PCAP can include unrelated domains, IP addresses, query parameters and session material. Share a redacted host-and-purpose table, not the original capture.

Prepare the baseline

Close browsers, launchers and chat clients you are not testing. Verify the EXE hash and note the exact settings state. Open TCPView and filter for Luczystrap.exe.

Start the built-in packet capture

Open Terminal as Administrator. Full packets are useful for analysis but increase sensitivity.

pktmon start --capture --pkt-size 0 --file-name C:\Temp\luczystrap.etl

Run exactly one action

For example: open Luczystrap and wait 60 seconds. Do not install, join a game and enable Discord in the same run. A narrow workflow makes each connection explainable.

Stop and convert the recording

pktmon stop
pktmon etl2pcap C:\Temp\luczystrap.etl --out C:\Temp\luczystrap.pcapng

Attribute, compare and redact

Match TCPView’s process-owned connections to the capture time. Compare against the idle baseline. Record host, method, path category, trigger and control; remove tokens, cookies, user IDs, job IDs and unrelated traffic.

07 / FAQ

Network answers by evidence level.

The short answer is rarely “allow” or “block.” The route, process, workflow, transmitted field and current version all matter.

08 / Inspectable evidence

Routes, code and capture.

Current runtime observation and historical code answer different questions. Both are linked. Third-party service documentation explains the mechanics without inventing Luczystrap behavior.

Checked August 6, 2026. The latest official GitHub release remained 1.4.9, published November 5, 2025. The current app source was still unavailable, so this page does not claim that the historical list is identical to the current binary or that a single sandbox run exercised every route. The reported webhook credential is omitted to avoid redistributing a secret.