What Google Front End is
Google Front End is the reverse proxy layer that terminates connections for Google's own properties and for customer applications on Google Cloud, including App Engine, Cloud Run and the external HTTP load balancer. It handles TLS termination and routes requests into Google's internal network.
How DNSTrace.dev detects it
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.
server: Google Frontend— The most common identifying value.server: gws— Used by some Google web properties.AS15169— The Google autonomous system announcing most of these addresses.CNAME targets under googleusercontent.com or ghs.googlehosted.com— Common for hosted application mappings.
What a detection proves
The connection terminated on Google infrastructure.
What it does not prove
Which Google product is behind it. App Engine, Cloud Run, Firebase Hosting and a plain load balancer can all present the same front end, and the header does not distinguish them.
Common questions
Can DNSTrace.dev tell Cloud Run from App Engine?
No. They share the same front end and the same server header, so DNSTrace.dev reports the edge layer only and does not guess the product behind it.
Compare with
Amazon CloudFrontAmazon Web Services, Inc.
Global load balancer and CDN
Azure Front DoorMicrosoft Corporation
CDN, reverse proxy and WAF
CloudflareCloudflare, Inc.
Edge cloud and CDN
FastlyFastly, Inc.
Check a domain
Run a full lookup to see the delivery layer, the detected application stack, live TLS and the announcing network side by side.