Authoritative DNS you manage in the panel
When you delegate your domain's nameservers to cdn.com.tr, the platform becomes the authoritative source for your zone and the panel becomes your record editor. You add and change A, AAAA, CNAME, MX, TXT, and other record types directly, which keeps website routing, email delivery, and third-party verifications in one place. Because DNS is the very first lookup any visitor makes, hosting it alongside your edge delivery means routing changes and new subdomains take effect through a single control surface instead of a separate registrar dashboard.
Auto SSL: certificates without the busywork
Traditional TLS setup means generating a key and CSR, validating domain ownership, buying or requesting a certificate, installing it on the server, and remembering to repeat it before expiry. cdn.com.tr collapses all of that into an automatic flow: once your domain points at the edge, ownership is validated and a free certificate is issued and installed for you. You never touch a .crt or .key file, and the certificate lives at the edge where TLS is terminated, so your origin does not need its own certificate management either.
The apex versus www problem, solved
A subtle source of broken HTTPS is that example.com and www.example.com are separate names that each need their own DNS record and certificate coverage, and the apex cannot use a plain CNAME under standard DNS rules. cdn.com.tr handles this for you: when DNS is delegated, the apex is routed to the edge correctly and both names are validated and secured together. The panel shows each variant's status independently so you can confirm a visitor is covered whether they type the bare domain or the www form.
Renewal that never lapses
An expired certificate throws a browser warning that scares visitors away and can take a site offline in practice even though the server is running fine. Because Auto SSL renewal is automated and happens ahead of expiry, this common outage simply does not occur on cdn.com.tr; there is no reminder to miss and no manual reinstall step to forget. The platform tracks the certificate lifecycle for you and shows its status, turning what is usually a recurring operational chore into something you never think about.
GeoDNS and intelligent routing
Hosting authoritative DNS at the platform opens the door to routing decisions made at resolution time, so visitors can be directed toward the nearest or most appropriate edge rather than a single fixed address. This GeoDNS behavior shortens the network path for geographically spread audiences and complements the edge cache by getting requests to the right place before content is even served. Managing it in the same panel as your delivery keeps routing policy and caching policy aligned instead of split across separate systems.
Migrating a live domain with low downtime
Moving a production domain is nerve-wracking because a mistake can drop traffic or break email, so the platform is built to make the cutover gradual and verifiable. You import your existing records first, confirm they resolve correctly, provision the certificate, and only then switch nameservers or the CNAME, so HTTPS is ready before traffic arrives at the edge. Checking apex and www state independently before and after the switch lets you catch a missed record early rather than discovering it from an angry visitor.
How to set it up, step by step
Add your domain to the account
Enter your domain in the panel. You then choose how to connect it: delegate full DNS to cdn.com.tr by changing your nameservers, or keep DNS where it is and add a CNAME that points the hostname at the edge. Full delegation unlocks apex handling and GeoDNS; CNAME is quicker for a single subdomain.
Create your DNS records
If you delegate DNS, the panel becomes your zone editor: add A, AAAA, CNAME, MX, TXT, and other records so mail, verification, and subdomains keep working. Import your existing records first so nothing is lost when the nameservers switch over.
Let Auto SSL issue the certificate
As soon as the domain resolves to the edge, the platform validates ownership and issues a free TLS certificate for the hostname, covering apex and www where applicable. There is no CSR to generate and no certificate file to upload; provisioning happens automatically in the background.
Verify apex and www separately
Because apex (example.com) and www (www.example.com) are technically different names, the panel checks each one's DNS and certificate state independently. Confirm both show as verified and secured so visitors reach HTTPS whichever form they type.
Force HTTPS
Enable HTTPS redirection so any HTTP request is upgraded to the secure version at the edge. With the certificate in place this closes the gap where a visitor might otherwise land on an unencrypted page.
Leave renewal alone
Certificates renew automatically before they expire, so you do not diarize expiry dates or scramble to reinstall. The panel surfaces certificate status so you can confirm health at a glance, but the renewal itself needs no action from you.
Example scenarios
A team registers a domain, delegates DNS to cdn.com.tr, and has both apex and www resolving to the edge with a valid HTTPS certificate before the site even goes public, all from one panel.
An existing site imports its DNS records, provisions the certificate at the edge ahead of time, and switches nameservers, so visitors experience a secure, uninterrupted move instead of a certificate error during cutover.
An agency manages dozens of client domains where certificates renew automatically, eliminating the expiry-tracking spreadsheet that used to cause the occasional embarrassing lapse.
Frequently asked questions
Do I have to pay for the SSL certificate?
No. Auto SSL issues a free TLS certificate for your domain and installs it at the edge automatically once the domain resolves there. There is no separate certificate purchase and no per-renewal cost to manage.
Can I keep my current DNS provider and still use this?
Yes, for a hostname. You can leave DNS where it is and add a CNAME pointing the subdomain at the edge, which is enough for delivery and certificate issuance on that name. Delegating full DNS to cdn.com.tr additionally enables clean apex handling and GeoDNS routing.
Why do apex and www need to be handled separately?
They are distinct DNS names, and standard DNS does not allow a plain CNAME on the apex the way it does on www. cdn.com.tr routes the apex to the edge correctly and secures both names together, and the panel shows each one's verification and certificate status independently.
What happens when the certificate is about to expire?
Nothing you need to do. Renewal is automatic and runs ahead of the expiry date, so the certificate stays continuously valid without any reinstallation. The panel displays certificate status if you want to confirm, but the lifecycle is managed for you.
Does my origin server also need a certificate?
TLS is terminated at the edge, so visitors get a valid HTTPS connection to cdn.com.tr regardless of your origin's own certificate state. You can still secure the edge-to-origin hop, but you no longer have to manage a public-facing certificate on the origin itself.
Will moving DNS here break my email?
Only if records are not carried over. That is why you import your existing zone, including MX and TXT records like SPF and DKIM, before switching nameservers. With those records recreated in the panel, mail routing continues exactly as before through the cutover.