Server locations

Your site lives on a real server in a real place. And where that place is matters more than you'd think.

What are server locations?

Server locations are the places the servers behind your domain appear to be. DomainDash plots them on a world map — worked out from your site's DNS records — so you can see your global footprint at a glance and understand what visitors in different parts of the world will experience. You don't need to give us hosting access or set anything up on your end.

You'll find this map in two places. On the site overview (and the uptime page) it's the Global reach card, where it also marks the locations DomainDash checks your site from. On the Routing sub-page it appears as the Server locations map, below the DNS records. Either way it updates automatically whenever we run a DNS check. See DNS health for the rest of the Routing page.

What the map shows

The map plots server pins — where the IPs behind your domain appear to live. If a site has more than one server in the same city, they're grouped into a single pin; hover it to see how many. Above the map, a short summary tells you how many IPs were found and across how many countries or cities. On the Global reach view you'll also see markers for the locations DomainDash checks from, so your servers and our check points sit on the same map.

A couple of things worth knowing about the pin locations:

• They're approximate. We estimate server locations from public IP address data. That's accurate at the country and city level, but we can't pinpoint the exact data centre or building.
• If you use a CDN, you'll see the CDN's location, not your origin. When your site is behind something like Cloudflare, Fastly, or CloudFront, the pins show the CDN's edge nodes, not the server where your site actually lives. This is usually a good sign: it means visitors in that area are already getting a cached copy close to home.

To see how your site actually performs from different places, add a second check location (available on paid plans) — a separate setting that measures response time from where your visitors are, so you can tell whether distance is costing them speed.

Why server location matters

Data moves through the internet at roughly the speed of light, along undersea fibre cables. That's fast, but not instant.

A request from London to a server in Sydney has to travel about 17,000 km each way. Even at the speed of light, that's around a 270ms round trip just for the wire, before your server has done any actual work. Add the usual overheads (connecting, securing the connection, your server thinking about the response, the response travelling back), and a distant visitor can wait noticeably longer than a local one.

Rough real-world numbers to put that in perspective:

Visitor in	Server in	Minimum round trip
London	London	~10ms
London	New York	~75ms
London	Sydney	~270ms

The closer your server is to your customer, the less waiting they do. It's as simple as that.

What your map is telling you

There are four common patterns. See which one looks like your map.

One pin, close to your customers

You're in a good place. Most of your visitors get a quick experience by default, and there's nothing to worry about.

One pin, a long way from your customers

Your server is far from where your visitors are. They're probably noticing the wait, especially on slower connections or mobile networks.

Measure it for yourself

Want to see how your site actually performs from where your customers are? You can add a second check location in your site settings, and DomainDash will start measuring from there too. See check locations for how to set that up.

Multiple pins across different parts of the world

You're using multiple servers, or a CDN, to serve your site from several places at once. Your site is likely already set up for global reach. Good work.

The pins show a CDN edge

We're showing your CDN's nodes, not your origin server. That's usually a good sign. Visitors in those areas are already getting a cached copy close to home, and your real server is shielded behind the CDN.

How to improve your global reach

If your map is telling you some of your visitors are a long way from your server, there are a few things you can do about it.

Measure from more places

The first step is knowing whether the distance is causing a problem. Add a second check location that's closer to your customers, and you'll see their real experience side-by-side with yours.

Start with check locations

Check locations walks through adding a second location and comparing the results.

Put your content closer with a CDN

A content delivery network (CDN) stores copies of your site on servers all around the world. When someone visits your site, they get served from the nearest CDN node rather than travelling all the way to your origin server. That can be the difference between a snappy site and a sluggish one for distant visitors.

Popular CDNs include Cloudflare, Fastly, AWS CloudFront, and Bunny.net. Most of them have a generous free tier and are straightforward to set up.

Frequently asked questions

How does DomainDash know where my servers are?

DomainDash works it out from your site's DNS records — specifically the IP addresses your domain resolves to. Public IP address databases map those addresses to country and city. You don't need to give DomainDash hosting access or configure anything; it's all derived from public DNS data and updated whenever we run a DNS check.

Why does the map show my CDN location instead of my origin?

When your site is behind a CDN like Cloudflare, Fastly, or AWS CloudFront, the IP address you serve points at the CDN's edge nodes, not your origin server. DomainDash shows what visitors actually connect to, which is the CDN. This is normally a good sign — it means your content is being served from somewhere close to your visitors.

How accurate is the server location?

Locations are accurate at the country and city level, but DomainDash can't pinpoint the exact data centre or building. Server pins are derived from public IP-geolocation databases that map IP ranges to physical addresses with city-level precision.

Can I add more server locations?

DomainDash shows whatever your DNS records point to. To get more global coverage, add a CDN (Cloudflare, Fastly, AWS CloudFront, Bunny.net) — most have generous free tiers. The CDN's edge nodes will then appear on the map automatically.

Related

• DNS health for the Routing sub-page the map lives on
• Check locations for comparing performance between two locations
• Uptime checks for how uptime checks work in general
• How incidents work for what happens when a check fails