Custom Domains
Instead of oksyon.com/e/your-event, you can use your own domain like ourwedding.com. This is a paid feature available on a per-event basis.
How it works
When you set up a custom domain:
- Your event page loads at
yourdomain.com(no path needed) - Menu page is at
yourdomain.com/menu - Registry page is at
yourdomain.com/registry - Invite links become
yourdomain.com/invite/CODE - All pages use your chosen theme
The oksyon.com/e/... URL continues to work alongside your custom domain.
Setting up a custom domain
Step 1: Buy a domain
Purchase a domain from any registrar (Cloudflare, Namecheap, GoDaddy, etc.). Short, memorable names work best for events — e.g., ben-and-bella.com.
Step 2: Enable custom domain in Oksyon
- Go to your event’s Details page
- Find the Custom Domain section
- Enter your domain name (e.g.,
ourwedding.com) - You’ll see DNS instructions to follow
Step 3: Configure DNS
Add a CNAME record at your domain registrar pointing to Oksyon:
| Type | Name | Target |
|---|---|---|
| CNAME | @ or yourdomain.com | custom.oksyon.com |
Note: Some registrars don’t support CNAME on the root domain (@). In that case, use a subdomain like www.ourwedding.com or switch your DNS to Cloudflare (which supports CNAME flattening).
Step 4: Wait for verification
After updating DNS, Oksyon will automatically:
- Detect the DNS change (usually within minutes)
- Issue an SSL certificate for your domain
- Mark the domain as Active
You can check the status on your event’s Details page.
SSL / HTTPS
All custom domains get a free SSL certificate automatically. Your guests will always see a secure https:// connection.
Troubleshooting
Domain shows “Pending”
DNS changes can take up to 48 hours to propagate, though most complete within 30 minutes. Check that your CNAME record is correctly set.
Domain shows “Error”
This usually means the CNAME record is missing or pointing to the wrong target. Double-check that it points to custom.oksyon.com.
”Not secure” warning in browser
The SSL certificate takes a few minutes to issue after DNS verification. Wait 5-10 minutes and try again.