Date: 2026-04-30 (UTC)
Author: marketing-strategist
Supersedes: docs/marketing/social-media-handles-2026-04-29.md
Status: Ready for operator action — manual signups required
The 2026-04-29 research recommended @getraxx as the canonical handle. Two blockers emerged:
@getraxx turned out to be taken on X/Twitter (confirmed post-research by Kristerpher).@raxxapp due to a prior adult-entertainment business registered under "Racks to Riches LLC" — active in registration paperwork, cached SEO, and dormant social handles, even though raxxapp.com is currently NXDOMAIN.Kristerpher selected raxxhq (2026-04-30) as the new canonical. This doc covers full availability research, domain status, SEO sanity, trademark notes, and the signup playbook for @raxxhq.
api.github.com/users/<handle> — authoritative, no anti-scrape. 404 = available.com.atproto.identity.resolveHandle endpoint — authoritative. "Unable to resolve handle" = available.publish.twitter.com/oembed with handle URL — returned full 404 error page ("Nothing to see here / this page doesn't exist") = handle not taken.subreddits/search.json?q=<name> = subreddit does not exist (available). 403 = exists but private.accounts/login/?next=... regardless of whether the profile exists (confirmed via baseline probe of a known-nonexistent handle). Cannot determine availability via HTTP. Needs manual app check.dns-query, RFC 8484). Status 3 = NXDOMAIN = domain has no A record / is not actively hosted. Certificate transparency logs (crt.sh) used to assess prior activity.@raxxhq| Platform | Handle | Probe Result | Status | Notes |
|---|---|---|---|---|
| X / Twitter | @raxxhq |
oEmbed → 404 "Nothing to see here" | AVAILABLE | Confirmed not taken. Register with priority. |
| LinkedIn (company) | raxxhq |
404 | AVAILABLE | |
| GitHub (org) | raxxhq |
API 404 | AVAILABLE | |
| Bluesky | @raxxhq.bsky.social |
ATP "Unable to resolve handle" | AVAILABLE | ATP-authoritative, no false negatives |
| Mastodon.social | @raxxhq |
404 | AVAILABLE | |
| Substack | raxxhq.substack.com |
404 | AVAILABLE | |
r/raxxhq |
Redirects to subreddit search | AVAILABLE | Subreddit does not exist | |
| TikTok | @raxxhq |
Body: "Couldn't find this account" | AVAILABLE | |
| YouTube | @RaxxHQ |
200 + "Raxx HQ" channel title, 39 subscribers | TAKEN | See note below |
@raxxhq |
Login-wall redirect (universal IG behavior) | NEEDS MANUAL CHECK | IG redirects unauthenticated requests regardless of profile existence | |
| Threads | @raxxhq |
Login-wall redirect (universal Threads behavior) | NEEDS MANUAL CHECK | Same behavior for both existing and nonexistent handles |
@RaxxHQA YouTube channel with the display name "Raxx HQ" exists at youtube.com/@raxxhq.
UCZAuPt-9g6ieesK7gpdVjiQThis is a low-activity channel (39 subscribers, no visible content, empty description) registered under a name that directly parallels our brand. It is plausibly a dormant squatter or an unrelated coincidence.
Recommended path: After creating the YouTube channel, attempt to claim @raxxhq via YouTube's standard handle claim process. YouTube allows channel owners to request handle transfers for trademark conflicts. If the claim fails at launch:
- Fallback handle: @raxxhq_official or @raxxhq_app (both unclaimed at time of research — verify before use)
- Flag to Crosby at next IP check-in: YouTube channel ID UCZAuPt-9g6ieesK7gpdVjiQ, 39 subscribers, display name "Raxx HQ", no content, empty description. Trademark-based handle transfer request is viable once Class 42/9 registration issues.
The prior research explored a "raxxapp-support" model. Adapted to raxxhq naming convention:
| Platform | Handle | Convention | Status |
|---|---|---|---|
| GitHub | raxxhq-support |
Hyphen (GitHub allows hyphens in org/user names) | AVAILABLE (API 404) |
| GitHub | raxxhq-status |
Hyphen | AVAILABLE (API 404) |
| Bluesky | raxxhqsupport.bsky.social |
No separator (Bluesky subdomain labels) | AVAILABLE (ATP confirmed) |
| Mastodon.social | @raxxhq_support |
Underscore | AVAILABLE (404) |
| Mastodon.social | @raxxhqsupport |
No separator | AVAILABLE (404) |
raxxhq-support |
Hyphen | AVAILABLE (404) |
Decision required on whether per-purpose handles are part of the ops plan. See "Decisions Needed."
raxxhq.com| Signal | Result |
|---|---|
| DNS (Cloudflare DoH) | Status 3 = NXDOMAIN — no A record, no hosting |
| HTTPS probe | Connection refused |
| SSL certificate transparency (crt.sh) | No certificates ever issued for raxxhq.com |
Interpretation: raxxhq.com has never been registered or hosted. This is the cleanest possible domain status — no prior use, no cached SEO, no certificate history, no trademark baggage.
Recommendation: Acquire raxxhq.com defensively. The primary product domain is raxx.app. raxxhq.com should be acquired as a defensive redirect to raxx.app. Cost is ~$10/year at any major registrar. This prevents a third party from registering it to capitalize on the @raxxhq social presence once established.
For contrast — raxxapp.com status:
| Signal | Result |
|---|---|
| DNS (Cloudflare DoH) | Status 3 = NXDOMAIN — currently not hosted |
| SSL certificate transparency (crt.sh) | Certificates issued (Let's Encrypt + Google Trust Services) — domain was actively hosted at some point |
This confirms the prior BLR research: raxxapp.com was live (certificates prove real HTTPS hosting), is now dark (NXDOMAIN), but carries SEO, registration, and trademark history. The raxxhq pivot correctly sidesteps this.
DuckDuckGo search for "raxxhq": no indexed results (zero results page).
Certificate transparency search for raxxhq.com: no certificates found — domain has never been used to serve HTTPS traffic.
Assessment: raxxhq is a term with near-zero existing search index footprint. Ideal — the brand registers the term from a clean slate. No confusion risk, no negative association, no SEO cleanup required.
"raxxhq" reads as RAXX + HQ (headquarters / company shorthand — a common brand suffix pattern).
Effect on pending RAXX mark (Class 42 + 9):
- "HQ" is a generic, non-distinctive suffix. It does not add or subtract from the distinctiveness of "RAXX" as the protectable element.
- Using @raxxhq as a social handle does not create a new trademark. The mark being prosecuted is RAXX, not RAXXHQ.
- The @raxxhq handle registrations are consistent with the RAXX trademark prosecution and do not create a new filing obligation.
- The YouTube channel "Raxx HQ" (UCZAuPt-9g6ieesK7gpdVjiQ) should be noted to Crosby as a potential third-party use of a confusingly similar name. Even at 39 subscribers, it is a fact pattern to preserve in the prosecution record.
Flag to Crosby: YouTube channel ID UCZAuPt-9g6ieesK7gpdVjiQ ("Raxx HQ", 39 subscribers, empty content, empty description, at @raxxhq). Note in prosecution record. When Class 42/9 registration issues, YouTube trademark handle transfer is available.
@getraxx| Dimension | @getraxx (prior) |
@raxxhq (current) |
|---|---|---|
| X/Twitter | TAKEN (post-research discovery) | AVAILABLE (oEmbed-confirmed 404) |
| Available | Available | |
| GitHub | Available | Available |
| Bluesky | Available | Available |
| YouTube | Ambiguous (200 response in prior research) | TAKEN ("Raxx HQ", 39 subs) — handle transfer path exists |
| TikTok | TAKEN | AVAILABLE |
| Trademark distance from "Racks to Riches LLC" prior use | At risk (getraxx.com is live as our domain — adjacent association possible) | Clean (zero prior use anywhere) |
Domain raxxhq.com |
N/A | NXDOMAIN, no prior certs — acquire defensively |
| SEO baggage | getraxx.com is already live (fine) | Zero — virgin term |
@raxxhq is the stronger canonical across every relevant dimension except YouTube, which has a clear reclamation path.
| Platform | Handle | Signup URL | Priority reason |
|---|---|---|---|
| X / Twitter | @raxxhq |
https://x.com/i/flow/signup | Confirmed available; largest fintech discussion surface; trademark defense |
| LinkedIn (company) | raxxhq |
https://www.linkedin.com/company/setup/new/ | B2B credibility, recruiter/partner discovery |
| GitHub (org) | raxxhq |
https://github.com/organizations/plan | Dev credibility; OSS presence for Raptor/Antlers |
@raxxhq |
https://www.instagram.com/accounts/emailsignup/ | Verify manually in-app first; retail options traders under 40 skew Instagram | |
| YouTube | @raxxhq |
https://studio.youtube.com/ | Create channel, attempt handle claim; pursue trademark transfer if blocked |
| Platform | Handle | Signup URL | Priority reason |
|---|---|---|---|
| Bluesky | @raxxhq.bsky.social |
https://bsky.app/ | ATP-confirmed available; fediverse credibility |
| Mastodon.social | @raxxhq |
https://mastodon.social/auth/sign_up | Available; fediverse defensive registration |
| Substack | raxxhq |
https://substack.com/ | Available; use if newsletter strategy confirmed |
| Threads | @raxxhq |
https://www.threads.net/ | Tied to Instagram account; create after Tier 1 Instagram signup |
r/raxxhq |
https://www.reddit.com/subreddits/create | Available; create as private to start, flip public at launch |
| Platform | Handle | Notes |
|---|---|---|
| TikTok | @raxxhq |
Available (confirmed). Defer until short-form video content strategy is confirmed. |
| Discord | raxxhq (server name) |
Not probeable via HTTP; create server when community size justifies moderation overhead. |
| Platform | Reason |
|---|---|
| Fintech audience mismatch | |
| Snapchat | No B2B/fintech traction |
| Medium | Low priority; Substack preferred if newsletter route is confirmed |
Execute in this order to unblock dependencies (Threads requires Instagram account):
social-media-team@raxx.app GWS group (unblocks all signup verification emails)@raxxhq) — highest-priority; confirmed available; trademark defenseraxxhq) — professional identity anchorraxxhq) — OSS credibility; needed before any code repos move under the org@raxxhq) — verify in-app first; blocks Threads@raxxhq) — create channel; attempt handle claim in YouTube Studio@raxxhq) — after Instagram (shares account)@raxxhq.bsky.social) — ATP-confirmed available; low effort@raxxhq) — 5 minutesr/raxxhq) — create private; go public at launchRaxx
Your entry, credit, and exit — locked in before the trade. Structure for retail options traders.
Alternate bio (160-character constraint — X, TikTok):
Lock in your structure before the trade. Options discipline for retail traders. raxx.app
LinkedIn company bio (extended, 2000-character limit):
Raxx is an automation platform for retail options traders who have intuitively correct ideas but lack the system to lock them in before the trade.
Most trading losses aren't skill problems. They're structure problems — entry isn't quantified, credit isn't benchmarked, exit isn't predefined. Mid-trade, the question becomes: "What's the plan now?" Raxx eliminates that question. Your structure is on the screen before the position opens.
Raxx enforces the entry/credit/exit structure you already decided on, before emotion gets a vote.
https://raxx.app/
social-media-team@raxx.app
Export the SVG wordmark to PNG at 400x400 (dark background, #0A0A0A) and 512x512 (square) before any platform signup. See prior research doc for wordmark source path.
The prior "raxxapp-support" model maps to raxxhq-support (hyphen) or raxxhqsupport (no separator). Both are available on GitHub, Bluesky, and Mastodon.
Option A — Hyphen (raxxhq-support): Readable. Works on GitHub, LinkedIn, Mastodon.
Option B — No separator (raxxhqsupport): Works everywhere. Slightly harder to read.
Option C — Underscore (raxxhq_support): Works on Mastodon; inconsistent on many platforms.
Recommendation: Option A as primary, Option B as fallback where hyphens are rejected. The per-purpose handle model is only worth implementing if a dedicated support/status social presence is part of the ops plan — see "Decisions Needed."
| Platform | Handle | Channel ID | Subscribers | Content | Action |
|---|---|---|---|---|---|
| YouTube | @RaxxHQ |
UCZAuPt-9g6ieesK7gpdVjiQ |
39 | None visible / "Not available" | Notify Crosby. Request handle transfer via YouTube trademark process once Class 42/9 issues. |
YouTube @raxxhq is TAKEN. Channel "Raxx HQ" exists with 39 subscribers and no content. Decision: (a) attempt YouTube trademark handle transfer now via self-service, (b) wait until trademark registration issues and file formal claim, or (c) register under fallback @raxxhq_official immediately and pursue transfer later. Recommendation: attempt self-service claim first (free, low effort), then escalate to Crosby if rejected.
Instagram / Threads availability unknown. Both platforms redirect all unauthenticated requests to login regardless of profile existence — no HTTP probe can determine status. Kristerpher must verify @raxxhq availability in the Instagram app before signup. Threads depends on Instagram.
Per-purpose handles: yes or no? The raxxhq-support model requires a decision on whether a separate support social presence is part of the ops plan. If yes, Option A (raxxhq-support) is the naming convention. If no, skip and route support via support@raxx.app only.
raxxhq.com defensive acquisition. Domain is unregistered, no prior use, ~$10/year. Recommendation: acquire via Cloudflare Registrar for consolidation with raxx.app. Set up a redirect to raxx.app immediately.
social-media-team@raxx.app GWS group. Prerequisite for all signups. Not yet provisioned. Provision before any signup session begins.
product-managersocial-media-team@raxx.app as a Google Workspace Group (size:s, area:devops) — confirm if already open from prior researchraxxhq.com at Cloudflare Registrar + configure redirect to raxx.app (size:xs, area:devops)@raxxhq on X, LinkedIn, GitHub, Instagram, YouTube) — umbrella card linking this doc