To determine which server or region a client’s Webflow-hosted website is using, you’ll need to investigate DNS resolution and IP address routing, as Webflow does not publicly expose server details by default.
1. Check the Domain’s DNS Records
- Use a DNS lookup tool like DNSChecker.org or the nslookup command.
- Look up the domain’s A records.
- If the site is properly pointed to Webflow, the IP addresses should be:
- (a) 75.2.70.75, and
- (b) 99.83.190.102
These are Amazon Web Services (AWS) Elastic Load Balancer IPs. Webflow uses AWS infrastructure globally.
2. Perform a Trace Route to the Domain
- Use traceroute (Mac/Linux) or tracert (Windows) from your location to the domain (e.g.,
traceroute clientsite.com
). - This will show the path your request takes to reach the Webflow server, including geographic hops.
- The final IP should match one of Webflow’s A records.
- Sites like geoiplookup.net or ipinfo.io will give you a rough geographic location of the IP address.
- Input the A record IPs (75.2.70.75 or 99.83.190.102) to see where they geographically resolve — typically pointing to AWS regions.
4. Understand Webflow’s Hosting Setup
- Webflow uses AWS Cloudfront and Global CDN via Fastly for fast global delivery.
- Clients accessing their site will connect to the nearest edge server, meaning website content is served based on the user's location, not a fixed “server”.
5. Confirm Hosting via Webflow Dashboard
- Go to Webflow Project → Hosting Tab.
- Confirm that the domain is properly connected with the correct A records and CNAME for the root and www versions.
Summary
You can’t pinpoint a single Webflow “server” for a site because Webflow uses cloud-based global delivery via AWS and CDN providers. Instead, determine the domain’s resolved A records and trace routes, which reveal Webflow’s load-balanced endpoints (75.2.70.75 and 99.83.190.102) and the closest delivery node based on the client’s location.