Hostinger CDN: How to Check It Works & What It Speeds Up

To check if Hostinger’s CDN is working, run a traceroute or use an online CDN detection tool—if the response comes from a Hostinger edge server (typically in a data center near you), it’s active. The CDN speeds up delivery of static assets like images, CSS, and JavaScript by caching them on servers closer to your visitors, which reduces load times and bandwidth usage on your origin server.

What Hostinger’s CDN Actually Does

Hostinger includes a free CDN (Content Delivery Network) with most hosting plans. When you enable it, your site’s static files—images, stylesheets, scripts, and sometimes videos—are copied to a network of edge servers located in multiple cities worldwide. When a visitor requests your site, the CDN serves those files from the nearest edge server instead of your original hosting server. This cuts the physical distance data travels, lowering latency and speeding up page load times, especially for audiences far from your server’s location.

The CDN also offloads traffic from your origin server. Since static files are served by edge nodes, your hosting server handles fewer requests, which can improve performance during traffic spikes and reduce the load on your server’s CPU and memory.

How to Verify It’s Working

There are several ways to check whether Hostinger’s CDN is active for your site. The most direct method is to inspect the response headers of a static asset, like an image or a CSS file.

1. Use your browser’s developer tools (F12 on Windows, Cmd+Option+I on Mac). Go to the Network tab, reload your site, and click on a static file (e.g., a .png or .css file). Look for the Server or Via header. If it mentions “cdn” or a Hostinger edge server name, the CDN is handling that request.
2. Run a traceroute to your domain. On Windows use tracert yourdomain.com, on macOS/Linux use traceroute yourdomain.com. If the IP addresses in the route belong to Hostinger’s CDN network (you can check with an IP lookup tool), the CDN is serving your content.
3. Use an online CDN detection tool like CDNPerf or IsItWP’s CDN checker. Enter your domain and it will tell you if a CDN is detected and which provider it is.
4. Check the response time from different locations using a global speed test tool like Pingdom or GTmetrix. If load times are consistently fast from multiple geographic regions, the CDN is likely working.

If you’ve enabled the CDN in hPanel but still see your origin server’s IP in headers, try clearing your browser cache and performing a hard refresh. Sometimes the CDN takes a few minutes to propagate.

What It Speeds Up (and What It Doesn’t)

The CDN accelerates delivery of static content—files that don’t change per user. This includes:

• Images (JPEG, PNG, WebP, etc.)
• CSS and JavaScript files
• Fonts and icons
• Videos and audio files (if you host them yourself)

However, it does not speed up dynamic content—pages that are generated on the fly based on user input, like PHP scripts, database queries, or personalized pages. Those still require a round trip to your origin server. The CDN also won’t help if your site’s bottleneck is server-side processing or database queries. For dynamic pages, you’d need additional caching or optimization.

How to Enable and Configure It

Hostinger’s CDN is managed through hPanel, the hosting control panel. Here’s how to turn it on:

1. Log into hPanel and go to Websites.
2. Click Manage next to your domain.
3. In the left sidebar, find Performance and click CDN.
4. Toggle the CDN switch to On. It may take a few minutes to activate.
5. Once active, you can optionally enable the “Cache Static Content” option and set a cache expiration time (e.g., 1 week).

You don’t need to change your DNS settings—Hostinger does that automatically. If you’re using a third-party DNS, you may need to point your domain to Hostinger’s CDN IPs, but that’s rare for Hostinger-hosted sites.

Common Issues and Troubleshooting

Sometimes the CDN doesn’t seem to work. Here are typical problems and fixes:

• Old cached content: If you update a file but visitors still see the old version, the edge server has a cached copy. Purge the cache from hPanel (under CDN settings) or wait for the TTL to expire.
• SSL certificate issues: Ensure your SSL is active. Hostinger’s CDN works with Let’s Encrypt, but if you have a custom certificate, you may need to configure it in hPanel.
• CDN not serving all files: By default, the CDN only caches static files. If you have very large files or specific extensions, you may need to adjust the cache rules in the CDN settings.
• Mixed content warnings: If your site loads some resources over HTTP while the CDN is HTTPS, browsers may block them. Make sure all URLs use HTTPS.

If you’ve tried these and still have issues, check Hostinger’s status page or contact support—they can verify if the CDN is properly configured on their end.

CDN vs. Other Speed Optimizations

The CDN is just one piece of site speed. Hostinger also offers other performance features that work alongside it:

• LiteSpeed Cache: This plugin caches dynamic pages and optimizes CSS/JS. It complements the CDN by handling server-side caching.
• HTTP/2 and HTTP/3: These protocols reduce latency and are enabled by default on Hostinger servers.
• GZIP compression: Compresses files before sending them to the browser. The CDN can also serve compressed versions.
• Image optimization: Tools like Imagify or ShortPixel reduce image file sizes, which the CDN then delivers even faster.

For best results, enable both the CDN and LiteSpeed Cache. The CDN handles static assets globally, while LiteSpeed handles dynamic content and server-level caching.

Frequently Asked Questions

Does Hostinger’s CDN cost extra?

No, it’s included free with all hosting plans (shared, cloud, VPS, and WordPress). There’s no limit on bandwidth or requests, though fair use policies apply.

Will the CDN work with a custom domain?

Yes, as long as your domain is pointed to Hostinger’s nameservers or you configure the DNS records as instructed. The CDN automatically handles custom domains.

Can I exclude certain files from being cached?

Yes, you can set up cache exclusions in the CDN settings. For example, you might exclude files that change frequently or are user-specific, like session cookies or dynamic scripts.

How long does it take for the CDN to start working?

Usually within 5–10 minutes after enabling it. DNS propagation might take up to 24 hours if you’ve changed nameservers recently, but in most cases it’s much faster.

Does the CDN affect my SEO?

Indirectly, yes. Faster load times improve user experience and can positively impact search rankings. Google has confirmed that page speed is a ranking factor, and a CDN helps with that.

What if my site is already fast without a CDN?

If your audience is geographically close to your server, the benefit may be minimal. But if you have visitors from multiple continents, a CDN can significantly reduce latency and improve consistency.

Related

• Registrar APIs vs DNS Interfaces: Tenant Migration
• Corrupted Flash Drive Repair: Recover Files
• Meta VR Glasses Storage: Can You Add More?