Despite repeated requests, Mojang does not make their API available with a CORS header. This makes using their API difficult in browsers, and additionally the absurdly low rate limits make the username API functionally useless for even moderately sized use-cases.
CORSjang fixes both of these issues — it is a frontend to Mojang's APIs on bunny.net's CDN. A CORS header is added to all responses, allowing usage from browsers, and the CDN's variety of IPs and caching makes more APIs actually usable as a bonus.
api.mojang.comcorsjangapi.b-cdn.netapi.minecraftservices.comcorsjangservices.b-cdn.netsessionserver.mojang.comcorsjangsessionserver.b-cdn.nettextures.minecraft.net supplies CORS and so is not included.
authserver.mojang.com is not included for security. Also I don't
think that server does anything useful anymore after the migration? I dunno dude-Dminecraft.api.services.host=https://corsjangservices.b-cdn.net
-Dminecraft.api.account.host=https://corsjangapi.b-cdn.net
-Dminecraft.api.session.host=https://corsjangsessionserver.b-cdn.net
-Dminecraft.api.auth.host=https://authserver.mojang.com
as JVM arguments, as of... some version! 1.7? Which should fix the username lookup whitelisting errors.
Worth noting that CORSjang is used by multiple production services.
Request logs are not enabled, only aggregate statistics. IPs are not stored, they're replaced with 0.0.0.0 by bunny.net. I even go out of my way to erase your IP and user agent from the request made to Mojang.