Gcore: Cloud, AI, CDN & Security

Gcore’s CDN, cloud infrastructure, GPU and AI services, FastEdge, security and streaming products explained beyond the delivery-layer fingerprint.

Updated 8 September 2026

What Gcore CDN delivers

Gcore’s CDN distributes web content, application responses and other HTTP resources. A CDN resource describes the delivery configuration and the origins it retrieves from. Gcore documents controls for caching, HTTP headers, cross-origin access, image delivery and large files.

For a software publisher, the application website and installation packages may need different delivery policies. Downloads should preserve the expected file contents and access rules, while website pages may change much more frequently.

Origins, purging and prefetching

Origin groups specify where the CDN can obtain content. Purging clears cached objects; prefetching loads content onto CDN servers ahead of ordinary requests. Gcore also offers reports and logs for examining delivery behaviour.

A release workflow might upload a package, verify it at the source, and then prepare its delivery before announcing the download. That workflow should include a check of the public URL, not just confirmation that the origin upload succeeded.

Cloud infrastructure and AI workloads

Gcore also offers cloud infrastructure and AI services. Its portfolio includes compute, storage and networking alongside GPU Cloud and AI Inference. These address running workloads and models, whereas the CDN addresses delivery. A public site served by Gcore need not run its application or AI models on Gcore infrastructure.

Security, edge applications and media

Gcore’s wider platform includes application protection, DDoS protection, edge compute through FastEdge and streaming services. These support different needs: filtering public requests, running edge logic and delivering media. A product team can combine those capabilities with its existing origin rather than treating the CDN as a complete backend.

Evaluating a Gcore configuration

Compare the cacheable share of traffic with the requests that must reach the application. A low cache hit rate may be entirely appropriate for private account endpoints and a problem for reusable media. Interpret the metric against the resource’s purpose.

Check the certificate and origin settings for every public hostname. If you add FastEdge or another edge product, document which layer now owns routing and response transformation so that later changes do not conflict.

How DNSTrace.dev detects Gcore

Detection correlates independent public signals. A single match is reported as strong evidence; agreement between a response header and the announcing network is reported as confirmed.

x-gcdn-cache — Cache outcome at the Gcore edge.
server containing gcore — The Gcore edge software.
CNAME targets under gcdn.co — The standard Gcore mapping.

What a detection proves

The response was served from a Gcore edge node.

What it does not prove

The origin behind the cache, or which Gcore region answered unless the response names it.

Common questions about Gcore

What is the difference between purging and prefetching in Gcore?

Purging clears cached content so it can be retrieved again. Prefetching requests content ahead of visitor traffic to prepare the CDN cache. They serve different roles in a publication workflow.

Does Gcore publish its edge ranges?

Gcore documents its network publicly, but DNSTrace.dev reports Gcore from response headers and CNAME targets rather than range matching.

CDN