⛔ Urgent: Request for a completely generic, unbranded CNAME target for White-Label Agencies
NAG OC
Hi Team,
I’m currently using your Agency white-label tier, but I’ve run into a major brand isolation issue that makes it easy for clients and competitors to spot our white-label setup. You’ve done an awesome job white-labeling the API and documentation, but I think this is a more pressing priority right now.
⚠️ The Problem: AI & Search Traceability
Currently, agencies are instructed to point custom subdomains to ns.digitalwallet.cards. While this domain is meant to be a generic "ghost" address, it is not fully isolated:
👣 Public Footprint:
The domain currently hosts your official API v2.0 documentation (docs.digitalwallet.cards) and active marketplace apps (e.g., lightspeed.apps.digitalwallet.cards).
🧑🏻💻 Instant AI Detection:
Because these public, indexable endpoints live on the exact same domain, I discovered the connection to your brand instantly simply by asking Gemini who owns ns.digitalwallet.cards. The AI immediately identified it as Boomerangme infrastructure.
Since tech-savvy clients and competitors regularly use AI assistants and DNS lookups for research, this public link completely breaks the white-label illusion we are paying for.
🟢 The Requested Solution
To fix this loophole, we need a truly anonymous routing path. Could the development team implement the following:
A Pure "Ghost" CNAME Target: Provide a completely separate, generic domain (e.g., ns.customercards.net or route.loyaltyrouting.com) dedicated solely to traffic routing.
🌐 Zero Web Presence:
Ensure this new domain has absolutely no public web presence, no indexable developer documentation, and no branded subdomains. If visited directly, it should just return a blank page or a 404 error.
Could you please let me know if moving to a completely unbranded routing domain is on your immediate roadmap, or if there is an alternative generic target we can use in the meantime?
Thank you,
Photo Viewer
View photos in a modal
Robert
support this
Armando
totally support this
s
sleepyhead
I second this. It should be fixed as soon as possible!
NAG OC
◀️ Another issue:
I've connected my custom domains for API and while reviewing it I spotted two small things:
- Backend domain showing in page source:
The
<redoc>
tag has a spec-url
attribute pointing to https://api.digitalwallet.cards/api/v2/docs/json
. Can you set up a simple proxy on the doc site's domain to serve the spec from there instead, then update the spec-url
to point to it? This is related to my original post above.- Boomerang" in the ReDoc JS bundle:
The string
pmc-adm-boomerang-pub-div
is buried inside redoc.standalone.js
. It's part of an internal ad-filter list, totally invisible to users but would be nice to change.Thanks!