google.co.uk is registered with Markmonitor Inc. [Tag = MARKMONITOR] and is hosted on AS15169 Google LLC in United States of America. Its SSL certificate from Google Trust Services LLC expired on 12 Feb 2024, and the site does not support HTTP/3. WOT's community rates its safety excellent (93/100).
What security vendors and the WOT community say about this domain.
What loads and tracks visitors when the homepage opens.
Running a full browser scan of the homepage… This takes about a minute.
Is google.co.uk’s name taken on other extensions?
Estimated visitors and engagement.
| Top countries | Share | Visits | Desktop | Mobile |
|---|---|---|---|---|
| United Kingdom | 85% | — | — | — |
| United States | 1.3% | — | — | — |
| South Korea | 1.2% | — | — | — |
| Spain | 0.6% | — | — | — |
| Thailand | 0.6% | — | — | — |
Every IP address google.co.uk resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| google.co.uk | 142.250.206.163 | 300 |
| Host | IPv6 address | TTL |
|---|---|---|
| google.co.uk | 2404:6800:4002:82d::2003 | 300 |
| Host | Mail server | TTL |
|---|---|---|
| google.co.uk | 0 smtp.google.com | 300 |
| Host | Name server | TTL |
|---|---|---|
| google.co.uk | ns1.google.com | 21600 |
| google.co.uk | ns2.google.com | 21600 |
| google.co.uk | ns3.google.com | 21600 |
| google.co.uk | ns4.google.com | 21600 |
| Host | Text | TTL |
|---|---|---|
| google.co.uk | "v=spf1 -all" | 300 |
| Host | Policy | TTL |
|---|---|---|
| google.co.uk | 0 issue pki.goog | 21600 |
| Host | Start of authority | TTL |
|---|---|---|
| google.co.uk | ns1.google.com dns-admin.google.com 590880111 900 900 1800 60 | 60 |
Other domains served from 142.250.206.163. Normal for shared hosting and CDNs.
No reviews yet. Used google.co.uk? Be the first to say how it went.
Reviews are from CubDomain users and are separate from the security verdicts above.
Common questions, answered from this report's data.
WOT's community rates google.co.uk excellent for safety (93/100). Its SSL certificate expired on 12 Feb 2024. See Security →
google.co.uk is registered through Markmonitor Inc. [Tag = MARKMONITOR]. See WHOIS →
google.co.uk is served from 1 IP address, mainly on AS15169 Google LLC in United States of America. See Hosting →
Raw registry data for google.co.uk. May be redacted by privacy services.
Domain name:
google.co.uk
Data validation:
Nominet was able to match the registrant's name and address against a 3rd party data source on 24-May-2021
Registrar:
Markmonitor Inc. [Tag = MARKMONITOR]
URL: https://www.markmonitor.com
Relevant dates:
Registered on: 14-Feb-1999
Expiry date: 14-Feb-2024
Last updated: 13-Jan-2023
Registration status:
Registered until expiry date.
Name servers:
ns1.google.com
ns2.google.com
ns3.google.com
ns4.google.com
WHOIS lookup made at 07:07:59 15-Dec-2023
--
This WHOIS information is provided for free by Nominet UK the central registry
for .uk domain names. This information and the .uk WHOIS are:
Copyright Nominet UK 1996 - 2023.
You may not access the .uk WHOIS or use any data from it except as permitted
by the terms of use available in full at https://www.nominet.uk/whoisterms,
which includes restrictions on: (A) use of the data for advertising, or its
repackaging, recompilation, redistribution or reuse (B) obscuring, removing
or hiding any or all of this notice and (C) exceeding query rate or volume
limits. The data is provided on an 'as-is' basis and may lag behind the
register. Access may be withdrawn or restricted at any time.The first response from http://www.google.co.uk, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with google.co.uk. Data is collected independently from public sources and some figures are estimates, provided for information only.
Spam and malware blocklists for the site's IP and mail servers.
When the site first appeared, and what has changed since.
We record what changes from the next time this report is refreshed.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.