SkinsRestorer LogoSkinsRestorer

Network hosts and services

Identify outbound HTTPS requests by the feature that uses them.

SkinsRestorer 15.12.6All platformsReviewed

SkinsRestorer uses outbound connections. It does not require a new inbound port for skin APIs. Permit DNS through your configured resolver and HTTPS response traffic for established connections.

Feature-specific hosts

FeatureHostNotes
Account UUID lookupapi.mojang.com, api.minecraftservices.com, eclipse.skinsrestorer.netAccount lookup and fallback routes
Account profile lookupsessionserver.mojang.com, eclipse.skinsrestorer.netSigned account textures
URL skin generationapi.mineskin.orgServer generation and website queue requests
Website and cape-aware generationaxolotl.skinsrestorer.netWebsite route and generated URL resolution
Recommended skinscool-skins.skinsrestorer.netRandom skins and recommended menu entries
Diagnostic uploadbytebin.lucko.me/sr dump report upload
Update checks and downloadsapi.github.com, github.comDownloads can redirect to GitHub asset hosts
Optional Ely.by account sourceaccount.ely.by, skinsystem.ely.byOnly with api.elyByEnabled
Client texture downloadtextures.minecraft.netJava clients fetch the skin image

HTTPS uses port 443. DNS transport follows your host's resolver configuration. Do not assume one static IP per API host.

The exact request list depends on enabled features and the release. GitHub downloads can involve additional redirected asset hosts. Inspect the failed request instead of opening every domain indiscriminately.

Status check scope

/sr status exercises account UUID and profile services. It does not check MineSkin, Axolotl uploads, recommendations, or database access.

The website's MineSkin availability indicator also does not prove every cape or upload route works.

Sources

For connection diagnosis and backend protection, use the firewall guide.

Did this page help?

Last updated on

On this page