Custom Domains
Your identity, your domain - true ownership of your fediverse presence

dns Own Your Identity

With Holos, you can use your own domain for your fediverse identity. Instead of being @you@holos.social, become @you@yourdomain.com. Your identity travels with you, even if you change relays.

badge
Your domain, your identity. Change relays without losing followers.
Default
@alice@holos.social
arrow_forward
Custom
@alice@alice.com

stars Benefits

badge
True Ownership
Your identity belongs to you, not a server. @you@yourdomain.com is yours forever.
swap_horiz
Full Portability
Change relays without losing followers. Your domain stays constant.

link_off Relay Independence

With a custom domain, you gain complete independence from any specific relay. This is the key advantage over traditional fediverse accounts.

verified_user
Zero Dependency on Your Old Relay
If you need to change relays, just sign up on a new one and update your CNAME. Your identity remains the same - no Move activity needed, no dependency on the old relay—online or not.
speed Relay too slow? Switch to a faster one.
cloud_off Relay is down? Move to another, keep your identity.
block Relay closing? Your identity survives.

settings Setup Process

Setting up a custom domain takes just a few minutes. Here's how it works:

1
Add your domain in the Holos app settings
2
Configure DNS records (TXT for verification, CNAME for routing)
3
Verify domain ownership in the app
4
Activate - a Move activity notifies your followers of the change

dns DNS Configuration

Two DNS records are required to verify ownership and route traffic:

TXT Ownership verification
_holos-verify.yourdomain.com holos-verify=abc123...
CNAME Traffic routing
yourdomain.com holos.social
info DNS propagation can take up to 48 hours, but usually completes within minutes.

swap_horiz The Move Activity

When you activate your custom domain, Holos sends a Move activity to all your followers. This is the standard ActivityPub way to handle account migrations.

Old Identity
@alice@holos.social
swap_vert Move Activity
Your Followers
notifications Receive Move notification
person_add Auto-follow new identity (Mastodon, etc.)
swap_vert alsoKnownAs
New Identity
@alice@alice.com

data_object ActivityPub Move Format

The Move activity follows the ActivityPub specification. Here's what gets sent to your followers:

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Move",
  "actor": "https://holos.social/users/alice",
  "object": "https://holos.social/users/alice",
  "target": "https://alice.com/users/alice"
}
actor The account sending the Move (your old identity)
object The account being moved (same as actor)
target The new identity (your custom domain)

manage_search How Lookups Work

When someone searches for @alice@alice.com, here's what happens:

cloud Remote Server
WebFinger
language Your Domain
CNAME
hub Holos Relay
1
WebFinger Request
Remote server queries alice.com/.well-known/webfinger
2
CNAME Resolution
DNS resolves alice.com → holos.social (via your CNAME record)
3
Relay Response
The relay returns your actor profile with inbox URL

move_to_inbox How Activities Reach You

When someone follows, likes, or replies to @alice@alice.com:

1
Activity Created
A user on mastodon.social likes your post or follows you
2
Inbox Lookup
Their server fetches your actor to find your inbox URL
3
CNAME Routing
The activity is sent to alice.com/inbox → routed to holos.social via CNAME
4
Relay Receives
The relay validates the signature and processes the activity
5
Delivered to App
Your phone receives the activity via WebSocket or sync

sync_alt Changing Relays

When you switch to a new relay with your custom domain, here's what happens:

1
Sign up on the new relay with your existing account keys
2
Update your domain's CNAME to point to the new relay
3
The new relay verifies your domain ownership via DNS TXT
4
Your identity continues working - same @user@yourdomain.com
verified What You Keep
badge Your fediverse identity (@you@yourdomain.com)
group Your followers (they already follow your domain)
key Your cryptographic keys (stored on your phone)
history Your post history (synced from your phone)
info No Move activity is needed because your identity never changed - only the relay serving it did.

security Security

Multiple layers of verification ensure only you can claim your domain:

verified
DNS Verification
A unique TXT record proves you control the domain. Only the domain owner can add DNS records.
link
alsoKnownAs Validation
Both old and new identities must reference each other. Prevents unauthorized moves.
vpn_key
HTTP Signatures
All activities are signed with your private key. The key never leaves your phone.

code Technology

ActivityPub Move WebFinger DNS TXT CNAME HTTP Signatures alsoKnownAs