How long does the custom domain setup take?

The setup only takes 5 minutes : 1. Add domain (30 seconds) 2. Set CNAME records (2 minutes) 3. Automatic SSL creation (5–10 min.) No technical knowledge required — everything is automatic.

Which DNS records do I need?

For the event domain, you need a CNAME record pointing to the target value displayed by Quick Event. You can find the exact value in the settings area once you have entered the domain. For email sender domains, a TXT record (SPF) and a DKIM record are also required—Quick Event displays both automatically. Recommended TTL: 300 seconds.

Do attendees see Quick Event branding?

No. Your participants will only see your domain in the address bar, your favicon in the browser tab, your sender name in emails, and your own Open Graph images when sharing. Quick Event is not visible in the finished event.

How do email sender domains work?

Emails come from events@your-company.de instead of quick-event.com. • SendGrid integration, SPF and DKIM automatically configured • Improved deliverability and fewer spam markings • Automatically set up during domain setup

Can I use multiple custom domains?

Custom domains are an agency and white-label feature available on request. When enabled, the setup supports different domains per event series, separate branding and email settings per domain, and central management in the dashboard. Contact us to discuss your requirements.

Can I use my own domain for an event registration page?

Yes. With Quick Event's custom domain feature you can host your entire event registration experience under a domain you control — for example, events.your-company.de — instead of the default quick-event.com subdomain. Visitors only ever see your URL in the browser address bar. The feature is available on request for agencies and larger organizations.

Does the event page work without a custom domain?

Absolutely. Every Quick Event account automatically receives a free quick-event.com subdomain and full white-label branding — your logo, colors, and favicon are already shown to attendees without any additional setup. A custom domain is the optional next step for teams that want their own URL in the address bar as well.

Do I need to buy an SSL certificate for my event domain?

No. Quick Event obtains a certificate from Let’s Encrypt automatically, during the first secure connection to your domain, as soon as the domain is verified — there is nothing to purchase, no CSR to generate, and no manual renewal. Connections use TLS 1.3, and the certificate is renewed in the background before it expires, with zero downtime.

What happens to old event links after I switch to a custom domain?

Existing links under quick-event.com continue to work. Once your custom domain is verified and active, Quick Event automatically redirects traffic from the old subdomain to your new domain, so bookmarked links and any previously shared URLs remain functional for attendees.

Is a custom domain suitable for event agencies managing multiple clients?

Yes — multi-domain support is designed specifically for agencies and white-label setups. You can run different event series under separate branded domains (for example, konferenz.client-a.de and akademie.client-b.de), each with its own SSL certificate, email settings, and event assignments, all managed from a single Quick Event dashboard. Contact Quick Event to enable this for your account.

How does performance compare between a custom domain and the default subdomain?

Custom domains are served by the same infrastructure as the platform itself, in German data centres — there is no performance penalty for using your own domain. Static files (images, stylesheets, PDFs) are delivered from the same object storage as everything else, and images are resized on the fly to the size actually needed instead of being sent at full resolution.

Custom Domains for Events

Hosting your events on your own branded domain is a planned agency and white-label capability in Quick Event — it is not part of the standard offering today and is available on request for agencies and larger organizations, so talk to us if you need it. What every plan already includes is full white-label branding on a free quick-event.com subdomain: your logo, your colors, and your favicon appear throughout the attendee experience, with no Quick Event branding forced onto your pages. When the custom-domain integration is enabled for your account, you point your own domain (for example events.yourcompany.com) at Quick Event with a DNS record, SSL is provisioned automatically, and you can also send participant emails from your own sending domain for a fully owned experience. Multiple domains can be mapped for organizations that run several brands or client accounts from one workspace.

Overview

Custom domains are an agency and white-label feature available on request. When enabled for your account, they turn Quick Event into an invisible backend behind your brand. Instead of quick-event.com/ihr-event , your guests see events.ihre-firma.de — with its own SSL certificate, favicon, and browser tab title. The entire event experience runs under your domain, without Quick Event being visible anywhere.

There are three ways in, and you pick whichever your DNS allows: a free subdomain of ours, your own subdomain via a CNAME record, or your own root domain via an A record — ihre-firma.de itself, with no www and no detour. The certificate is issued and renewed automatically once the domain is verified; you do not have to do anything for it.

Note: a custom domain is not required to run events under your brand. Every account already includes a free quick-event.com subdomain and full white-label branding.

Setup process

Setting up a custom domain typically takes less than five minutes. The process consists of four steps, two of which are automated.

Step 1: Add domain

In the settings, navigate to the "Custom Domains" section and enter your desired domain — for example, events.ihre-firma.de or konferenz.ihr-verband.org . Quick Event will then generate the necessary DNS records, which you will need to enter with your domain provider in the next step.

Step 2: Configure DNS

Set the displayed CNAME records with your domain provider. In most cases, a single record is sufficient. With common providers like IONOS, Strato, Hetzner, or All-Inkl, this process takes less than two minutes.

Step 3: Automatic verification

Once the DNS records have propagated, Quick Event automatically detects the change. The system verifies the domain and requests a certificate from Let’s Encrypt. This step takes between five and ten minutes—and up to an hour with some DNS providers if DNS propagation takes longer.

Step 4: Domain active

Once verification is successful, your domain is ready for immediate use. All events for your organization will be accessible under the new domain from this moment on. Existing links via quick-event.com will continue to work and redirect as needed.

DNS configuration

To connect your domain, you need a CNAME record that points to the target value displayed by Quick Event. CNAME records are the cleanest technical solution because they don't hardcode IP addresses and remain automatically correct even with infrastructure changes. Quick Event will show you the exact value in the settings area once you've entered the domain.

Set the TTL (Time to Live) to 300 seconds. A low TTL ensures that changes take effect quickly. After successful verification, you can optionally increase the TTL.

SSL/TLS encryption

Every custom domain automatically receives a certificate from Let’s Encrypt. It is requested during the first secure connection to your domain, as soon as the domain is verified — you do not need to buy a certificate, create a CSR, or schedule a renewal.

Connections use TLS 1.3 . HSTS (HTTP Strict Transport Security) is enabled by default, so browsers enforce the encrypted connection, and plain HTTP is redirected rather than served.

Certificates are renewed automatically before they expire. There is no manual step and no downtime during renewal.

Email sender domains

In addition to the event domain, you can also customize the sender address of your emails . Instead of noreply@quick-event.com you can send confirmation and follow-up emails from events@ihre-firma.de — or any other address within your domain.

Email integration is based on SendGrid. Two DNS records are required for authentication:

SPF record (TXT): v=spf1 include:sendgrid.net ~all — authorizes SendGrid to send emails on your behalf
DKIM record : Automatically provided and cryptographically signs outgoing emails so that recipient servers can verify their authenticity.

Correctly configured SPF and DKIM records significantly improve deliverability . Emails are less likely to end up in the spam folder and are classified as trustworthy by recipient servers.

Complete in-house branding

Custom domains are the final piece of the puzzle to ensure your events fully reflect your brand. Together with the design editor, you control every aspect of the visual appearance.

URL and domain : Your participants will only see your domain in the address bar.
Favicon and tab title : Custom icon and title in the browser tab
Email sender : All emails come from your domain.
No Quick Event Branding : No logos, watermarks, or other indications of the platform used.
Custom meta tags : Open Graph preview images and descriptions under your control

For agencies, this means: their clients experience the event entirely under the brand of their agency or the respective client — from the URL to the confirmation email.

Multi-domain support

For agencies and white-label setups, multiple custom domains can be enabled per organization. This is especially useful if you run different event series under different brands—for example, a conference series at konferenz.firma.de and a training program at akademie.firma.de .

All domains are managed centrally in the dashboard. Each domain has its own SSL certificate status, email settings, and can be individually assigned events. Contact us to set this up for your account.

Safety and performance

A custom domain runs on exactly the same infrastructure as the rest of the platform — nothing about it is a side entrance:

Encrypted throughout : TLS 1.3 with HSTS; plain HTTP is redirected, never served.
German data centres : the application, the database, and uploaded files are hosted in Germany, and backups are kept at a second German site.
Rate limits and bot defence on the login and registration endpoints, counted across all instances so they cannot be bypassed by load balancing.
Images resized on delivery : a logo or header is delivered in the size the page actually needs, not at full resolution.
Monitoring of availability and certificate validity, with alerts to the operations team.

These measures apply to every custom domain without additional configuration, from the moment the domain is verified.

Your Event, Your Domain — Zero Quick Event Branding