google.com — domain analysis
AdvantageBizMarketing Editorial
October 5, 2026
·
0 min read
google.com is a live website, registered in 1997, served from New Haven, United States. It has a valid HTTPS certificate, 1 of 6 common security headers.
Does google.com publish the usual trust pages?
Found: about. Not found at the usual addresses:
contact, privacy, terms.
These were checked at conventional paths only, so a site using different URLs may
publish them elsewhere.
How does google.com compare with other domains analysed here?
Measured against the 74 domains in this index. This is a
small, self-selected sample — the domains people happened to look up — not a
representative sample of the web.
| Response time | Faster than 72% of them (median 486ms) |
|---|---|
| Security headers | More than 47% of them |
| Domain age | Older than 80% of them |
Related domains in this index
Other analysed domains served from the same country:
When was google.com registered?
google.com was registered on 15 September 1997, which makes it about 29 years old.
A registration this old means the domain has been renewed repeatedly, which costs money every year and is not something abandoned or disposable projects tend to do.
The registrar of record is MarkMonitor Inc..
Registration runs until 14 September 2028.
The domain carries 6 registry locks, which blocks unauthorised transfer or deletion.
| Registered | 15 September 1997 |
|---|---|
| Expires | 14 September 2028 |
| Registrar | MarkMonitor Inc. |
| Registry status | client delete prohibited, client transfer prohibited, client update prohibited, server delete prohibited, server transfer prohibited, server update prohibited |
Where is google.com hosted?
The first address resolves to infrastructure in New Haven, United States.
The network is operated by Google LLC (AS15169 Google LLC).
Hosting location describes where the responding server sits, not where the business is. A CDN will report its nearest edge rather than the origin.
What is google.com running on?
No platform, framework or analytics fingerprints were found in the homepage markup of google.com. That usually means hand-written HTML, an uncommon stack, or a page assembled entirely at the edge.
No recognisable platform, framework or analytics fingerprints were found in the homepage markup.
How does the homepage respond?
The server answered with HTTP 200 over
HTTPS.
At 199ms to first byte this response is fast for a homepage measured from a single European location.
The HTML weighs 82KB, which is ordinary for a homepage.
The HTML is compressed with gzip.
| Server header | gws |
|---|---|
| Compression | gzip |
| Page size | 84,238 bytes |
| Declared language | de |
| Mobile viewport | not declared |
What does the homepage say about itself?
The title is only 6 characters, which is short enough that it probably is not describing the page so much as naming it.
There is no meta description, so the snippet shown in search results is assembled by the search engine from whatever text it considers relevant.
No H1 heading was found, so the page offers no single top-level statement of what it is.
All 1 images on the homepage have alt attributes.
No viewport meta tag is declared, so mobile browsers will render the page at desktop width and scale it down.
| Title | Google (6 chars) |
|---|---|
| Meta description | — none — (0 chars) |
| H1 | — none — (0 on the page) |
| Canonical | not set |
| Open Graph title | not set |
| Headings / images | 0 H2s, 1 images (0 without alt text) |
Is google.com served over a valid certificate?
The HTTPS certificate is issued by Google Trust Services and is
valid until 2026-12-11, which is 67 days from the date of this check. It covers
65 hostnames.
- *.google.com
- *.appengine.google.com
- *.bdn.dev
- *.origin-test.bdn.dev
- *.cloud.google.com
- *.crowdsource.google.com
- *.datacompute.google.com
- *.google.ca
- *.google.cl
- *.google.co.in
- *.google.co.jp
- *.google.co.uk
The certificate has 67 days left to run.
It covers 65 hostnames, which is characteristic of a shared or platform-issued certificate rather than one bought for this domain alone.
Which security headers does it set?
1 of 6 are set (X-Frame-Options). Absent: HSTS, Content Security Policy, X-Content-Type-Options, Referrer-Policy, Permissions-Policy.
Without HSTS, a browser that has never visited before will try HTTP first, which is the window a network attacker needs.
With no Content Security Policy, any script that reaches the page — including one injected through a compromised third-party dependency — runs with full access to it.
| Header | Set | Value |
|---|---|---|
| HSTS | no | — |
| Content Security Policy | no | — |
| X-Content-Type-Options | no | — |
| X-Frame-Options | yes | SAMEORIGIN |
| Referrer-Policy | no | — |
| Permissions-Policy | no | — |
How is DNS configured for google.com?
| IP addresses | 142.251.14.138, 142.251.14.101, 142.251.14.102, 142.251.14.139, 142.251.14.113, 142.251.14.100, 2a00:1450:4001:c13::65, 2a00:1450:4001:c13::8b, 2a00:1450:4001:c13::64, 2a00:1450:4001:c13::71 |
|---|---|
| Reverse DNS | pm-in-f138.1e100.net, pm-in-f101.1e100.net |
| Name servers | ns3.google.com, ns1.google.com, ns2.google.com, ns4.google.com |
| Mail (MX) | smtp.google.com (pri 10) |
| SPF | v=spf1 include:_spf.google.com ~all |
| TXT records | 17 |
google.com resolves to 10 addresses, which indicates load balancing or a CDN rather than a single origin server.
Mail is handled by 1 exchanger.
An SPF record is published, giving receiving servers a rule for which hosts may send as this domain.
Reverse DNS resolves to pm-in-f138.1e100.net, pm-in-f101.1e100.net, which usually names the hosting provider.
Who runs DNS and mail for google.com?
DNS is operated by Google rather than self-hosted name servers.
Mail is handled by Google Workspace.
The domain publishes AAAA records and accepts connections over IPv6.
Can google.com be spoofed in email?
DMARC is set to reject, the strictest setting: mail that fails authentication is refused outright. This is the configuration that actually stops domain spoofing.
CAA records restrict certificate issuance to 1 named authority (issue pki.goog), so no other CA should be able to issue for this domain.
The zone is not DNSSEC-signed. That is still the norm for most domains, but it means DNS answers cannot be cryptographically verified.
What else does google.com publish?
A security.txt file is published, giving security researchers a documented way to report vulnerabilities. Very few sites bother.
What does robots.txt allow?
robots.txt is 6,624 bytes and names
5 user-agent groups.
It does not blanket-disallow general crawlers.
Sitemaps declared:
- https://www.google.com/sitemap.xml
AI crawler policy
robots.txt names no AI crawlers specifically, so they fall under whatever rule
applies to User-agent: *.
What structured data does the homepage publish?
- WebPage
The homepage publishes 1 structured data type: WebPage.
What does google.com load from third parties?
The homepage loads no resources from third-party hosts at all, which is rare and means visiting it tells no other company that you did.
3 cookies are set before any interaction (SOCS, AEC, __Secure-ENID).
| Cookie | Secure | HttpOnly | SameSite |
|---|---|---|---|
| SOCS | yes | no | lax |
| AEC | yes | yes | lax |
| __Secure-ENID | yes | yes | lax |
Does google.com settle on one address?
Both google.com and www.google.com answer with 200 and neither redirects to the other. Search engines therefore see two complete copies of the site, and link equity is split between them unless a canonical tag resolves it.
How easily can google.com be crawled?
A sitemap index is served at https://www.google.com/sitemap.xml listing 22 entries.
A deliberately invalid URL correctly returns HTTP 404, so missing pages will not be indexed.
What tracking does google.com run?
No analytics or advertising trackers were detected on the homepage of google.com, which is unusual for a commercial site.
How does google.com look when shared?
No Open Graph or Twitter Card tags are present. Links shared to social platforms will fall back to whatever the platform can scrape, usually just a bare URL.
How are images, fonts and scripts handled?
1 image on the homepage, 0 of them lazy-loaded (0%).
All image references use JPEG, PNG or GIF. WebP or AVIF typically cut image weight substantially at the same visual quality.
No srcset attributes are used, so every device is served the same image size regardless of screen.
The page pulls 1 external stylesheet and 0 external scripts, with 0 carrying defer or async.
Is google.com accessible and current?
The page uses 0 landmark elements and 6 ARIA attributes.
There are 10 form inputs but only 0 label elements, so some fields may be unlabelled for screen readers.
No skip-to-content link was found, which keyboard users rely on to bypass navigation.
1 deprecated HTML element is still in use (center, font, marquee or blink).
Can search engines index google.com?
Nothing on the homepage prevents indexing: no noindex is set in the robots meta tag or the X-Robots-Tag header.
No canonical URL is declared, which leaves duplicate addresses of this page to be resolved by the search engine.
The homepage carries 10 internal and 1 external link across 1 outside host.
Visible text is only 0.2% of the HTML, which indicates the page is assembled in the browser rather than served as content.
How is google.com delivered?
The HTML is served with Cache-Control: private, max-age=0.
HTTP/3 is advertised via alt-svc, so modern browsers will upgrade to QUIC after the first visit.
No favicon is declared in the markup.
The TLS certificate also covers 4 subdomains: appengine.google.com, cloud.google.com, crowdsource.google.com, datacompute.google.com.
- appengine.google.com
- cloud.google.com
- crowdsource.google.com
- datacompute.google.com
Frequently asked questions
Does google.com set the usual HTTP security headers?
It sets 1 of 6. The ones not present are: HSTS, Content Security Policy, X-Content-Type-Options, Referrer-Policy, Permissions-Policy.
Does google.com allow AI crawlers?
robots.txt names no AI crawler specifically, so they fall under the wildcard rule, which does not disallow them.
Where does this data come from?
Every figure was measured by our own server on 5 October 2026: DNS lookups, one HTTPS request to the homepage, a TLS handshake and a request for robots.txt. No third-party SEO API is involved.
Is any of this traffic or authority data?
No. Traffic, authority and ranking figures cannot be measured by inspecting a domain, only modelled. Everything here is a direct observation.
I own google.com and want this page removed.
Ask through the contact page on this site, from an address at the domain, and the report will be taken down. It only ever shows what the domain already serves publicly.
Analysed 5 October 2026.
Analyse another domain →
AdvantageBizMarketing Editorial
SEO strategist and content editor at AdvantageBizMarketing.