Buy or assign a package
Use package and cart screens to unlock account capacity before API, cdnctl, or AI-agent work starts.
CDN.com.tr Help
The most common questions about contract-based Türkiye-only processing: where your traffic is processed, DNS options, origin protection and logs.
Billing, packages, and invoices
The most common questions about contract-based Türkiye-only processing: where your traffic is processed, DNS options, origin protection and logs.
A company whose data must not leave Türkiye under KVKK wants answers to its technical and contractual questions before choosing a CDN and WAF provider.
No. The cluster has no edge server abroad and traffic is not rerouted to points outside Türkiye; this is written in Data Processing Agreement clauses 9.2 and 9.7.
The Order Form shows the Türkiye-only setting switched on. Data Processing Agreement clause 9.2 and Annex 4 state in detail that traffic is processed only in Türkiye.
No. While Türkiye-only is on, global delivery, foreign clusters and foreign edge servers cannot be switched on (Data Processing Agreement Annex 4); the only sub-processors used are data centre operators in Türkiye.
Yes. A records to our edge addresses for the root domain, and an A record or a CNAME target of your own for www, are enough; only our name servers in Türkiye answer for the CNAME target. If you prefer, import your DNS in the panel and switch your name servers to ours in Türkiye (atlas.ns.cdn.com.tr, iris.ns.cdn.com.tr).
60 seconds by default; it can be set per path from 1 to 3600 seconds.
X-CDN-Client-IP; the source port comes in X-CDN-Client-Port. Our edge writes these headers itself on every request, and headers of the same name sent by the visitor are ignored.
The addresses our edge servers use to connect to your origin are listed in your written Activation Notice; allow those addresses on your server. In addition, you can define a secret header (for example X-CDN-Auth) in your rules in the panel, which our edges add to every request, and reject requests without it.
No. The JavaScript challenge runs on our own edge servers; the geolocation database is local to the edges too, and no IP is sent out.
No. Request bodies are not kept in any log; text sent through forms and file attachments never enter the logs. If you want, Logpush delivers a log of requests to you; these logs are kept in our storage in Türkiye for 30 days, and they are not created unless you turn Logpush on.
Contract-based Türkiye-only processing is part of the Enterprise plan: monthly, with no commitment. Instead of a trial, we test your site through our edges together before you change DNS.
Yes. In the panel you switch the WAF to log-only for the whole site or for the paths you choose; the WAF writes the requests it would have blocked to the logs as "would have blocked" and blocks none of them. The mode returns to blocking by itself at the end of the period you pick (7, 14 or 30 days). IP, country and network lists, rate limits and the JavaScript challenge keep blocking in this mode.
Use package and cart screens to unlock account capacity before API, cdnctl, or AI-agent work starts.
Recover failed payment and confirm billing records.
Standard packages come with a 15-day risk-free trial. Your site is not cut off when the quota runs out. This page explains what counts toward the quota and what happens when it runs out.
On the Enterprise package the service comes with a signed contract package: Order Form, Terms of Service, Data Processing Agreement, SLA, Sub-processors and Security Measures. The Türkiye-only processing setting is also offered with this package.
Your object storage, your application's disks and your managed databases sit on servers in Türkiye, and your application runs on Turkish nodes. On request we also serve your traffic from Turkish PoPs only.