google.hr was registered with Sayber d.o.o. on 20 Sept 2011 and is hosted on AS15169 Google LLC in Japan. 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 (94/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.hr’s name taken on other extensions?
Estimated visitors and engagement.
| Top countries | Share | Visits | Desktop | Mobile |
|---|---|---|---|---|
| Croatia | 89.9% | — | — | — |
| Bosnia & Herzegovina | 2.3% | — | — | — |
| Germany | 2.1% | — | — | — |
| United States | 1.2% | — | — | — |
| Austria | 1.1% | — | — | — |
Every IP address google.hr resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| google.hr | 172.217.166.195 | 300 |
| Host | IPv6 address | TTL |
|---|---|---|
| google.hr | 2404:6800:4002:808::2003 | 300 |
| Host | Mail server | TTL |
|---|---|---|
| google.hr | 0 smtp.google.com | 300 |
| Host | Name server | TTL |
|---|---|---|
| google.hr | ns1.google.com | 21600 |
| google.hr | ns2.google.com | 21600 |
| google.hr | ns3.google.com | 21600 |
| google.hr | ns4.google.com | 21600 |
| Host | Text | TTL |
|---|---|---|
| google.hr | "v=spf1 -all" | 300 |
| Host | Policy | TTL |
|---|---|---|
| google.hr | 0 issue pki.goog | 21600 |
| Host | Start of authority | TTL |
|---|---|---|
| google.hr | ns1.google.com dns-admin.google.com 590880111 900 900 1800 60 | 60 |
Other domains served from 172.217.166.195. Normal for shared hosting and CDNs.
No reviews yet. Used google.hr? 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.hr excellent for safety (94/100). Its SSL certificate expired on 12 Feb 2024. See Security →
google.hr is registered through Sayber d.o.o. The public WHOIS record shows the registrant’s details. See WHOIS →
The registration expired on 20 Sept 2024. See Overview →
google.hr was registered on 20 Sept 2011, making it 15 years old. See Overview →
google.hr is served from 1 IP address, mainly on AS15169 Google LLC in Japan. See Hosting →
Raw registry data for google.hr. May be redacted by privacy services.
% % From May 25, 2018, it is mandatory to apply the provisions of the % General Data Protection Regulation (EU) 2016/679. The basic purpose of % the regulation is greater control for individuals over their personal % information. % % In accordance with the provisions of the General Data Protection % Regulation (EU) 2016/679, we inform you that the personal data of the % domain holder and the contact persons under the domain holder are no % longer publicly available through the domain search engine. % % If you believe that there is a legitimate reason for which you need to % be provided with the data about the domain holder please fill in the % Request form for personal data disclosure : % https://domene.hr/portal/files/Request_personal_data_disclosure.pdf % Domain Name: google.hr Registrar WHOIS Server: whois.dns.hr Registrar URL: http://whois.dns.hr Updated Date: 2021-11-18T23:00:00Z Creation Date: 2011-09-20T22:00:00Z Registrar Registration Expiration Date: 2024-09-20T22:00:00Z Registrar: Sayber d.o.o. Registrant Name: Google Hrvatska d.o.o. Registrant Street: Savska cesta 32 Registrant City: Zagreb Registrant State/Province: HR Registrant Postal Code: 10000 Registrant Email: [email protected] Name Server: ns1.google.com Name Server: ns2.google.com
The first response from http://www.google.hr, 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.hr. 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.