hey.car was registered with Gandi SAS on 4 May 2017 and is hosted on AS16509 Amazon.com Inc. in India. Its SSL certificate from Amazon expired on 11 Jul 2024, and the site does not support HTTP/3. WOT's community rates its safety excellent (80/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 hey.car’s name taken on other extensions?
Estimated visitors and engagement.
| Top countries | Share | Visits | Desktop | Mobile |
|---|---|---|---|---|
| Germany | 80.7% | 387,386 | 34.7% | 65.3% |
| Romania | 7.9% | 37,875 | 100% | 0% |
| Netherlands | 4.4% | 21,121 | 62% | 99.4% |
| Austria | 1.8% | 8,404 | 10.7% | 89.3% |
| Türkiye | 1.6% | 7,670 | 0% | 100% |
Every IP address hey.car resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| hey.car | 99.86.47.11 | 60 |
| hey.car | 99.86.47.116 | 60 |
| hey.car | 99.86.47.119 | 60 |
| hey.car | 99.86.47.125 | 60 |
| Host | Mail server | TTL |
|---|---|---|
| hey.car | 0 hey-car.mail.protection.outlook.com | 300 |
| Host | Name server | TTL |
|---|---|---|
| hey.car | ns-1334.awsdns-38.org | 21600 |
| hey.car | ns-1915.awsdns-47.co.uk | 21600 |
| hey.car | ns-404.awsdns-50.com | 21600 |
| hey.car | ns-730.awsdns-27.net | 21600 |
| Host | Text | TTL |
|---|---|---|
| hey.car | "apple-domain-verification=ezfCO1uzKyAMxyYI" | 300 |
| hey.car | "atlassian-domain-verification=ZotQzMdVzab5+jvQgBmVe48W9fthN2TJlhTNbGOu0M5CLam4A8Soqmho3Mr9PPaZ" | 300 |
| hey.car | "ciscocidomainverification=1d94d6acd0ac2ea42bff3005c820378a2982acd8dbed966d986484817f96b611" | 300 |
| hey.car | "facebook-domain-verification=tzz4zne64sno6ve5qwe51dqb0vsh5l" | 300 |
| hey.car | "google-site-verification=eNpS8sroE0IfIz9mt8GFwqnfmZ-qFzQuedDvk927jXc" | 300 |
| hey.car | "miro-verification=77b6f3bb579bba4a334717cd4144d5c5c3b1b0cd" | 300 |
| hey.car | "MS=ms12879533" | 300 |
| hey.car | "v=spf1 include:spf.protection.outlook.com include:spf.mtasv.net include:_spf.salesforce.com -all" | 300 |
| hey.car | "ZOOM_verify_V_sAnSbeQpCUGDqIMLB9rA" | 300 |
| Host | Start of authority | TTL |
|---|---|---|
| hey.car | ns-1334.awsdns-38.org awsdns-hostmaster.amazon.com 1 7200 900 1209600 86400 | 900 |
Other domains served from 99.86.47.125. Normal for shared hosting and CDNs.
No reviews yet. Used hey.car? 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 hey.car excellent for safety (80/100). Its SSL certificate expired on 11 Jul 2024. See Security →
hey.car is registered through Gandi SAS. The public WHOIS record shows the registrant’s details. See WHOIS →
The registration expired on 4 May 2025. See Overview →
hey.car was registered on 4 May 2017, making it 9 years old. See Overview →
hey.car is served from 4 IP addresses, mainly on AS16509 Amazon.com Inc. in India. See Hosting →
Raw registry data for hey.car. May be redacted by privacy services.
Domain Name: HEY.CAR Registry Domain ID: D211469508-CNIC Registrar WHOIS Server: whois.gandi.net Registrar URL: http://www.gandi.net/ Updated Date: 2024-04-12T08:27:33.0Z Creation Date: 2017-05-04T16:03:09.0Z Registry Expiry Date: 2025-05-04T23:59:59.0Z Registrar: Gandi SAS Registrar IANA ID: 81 Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Registrant Organization: Mobility Trader GmbH Registrant State/Province: Registrant Country: DE Registrant Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. Name Server: NS-1334.AWSDNS-38.ORG Name Server: NS-730.AWSDNS-27.NET Name Server: NS-404.AWSDNS-50.COM Name Server: NS-1915.AWSDNS-47.CO.UK DNSSEC: unsigned Billing Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. Registrar Abuse Contact Email: [email protected] Registrar Abuse Contact Phone: +33.170377661 URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/ >>> Last update of WHOIS database: 2024-05-23T20:24:14.0Z <<< For more information on Whois status codes, please visit https://icann.org/epp >>> IMPORTANT INFORMATION ABOUT THE DEPLOYMENT OF RDAP: please visit https://www.centralnic.com/support/rdap <<< The Whois and RDAP services are provided by CentralNic, and contain information pertaining to Internet domain names registered by our our customers. By using this service you are agreeing (1) not to use any information presented here for any purpose other than determining ownership of domain names, (2) not to store or reproduce this data in any way, (3) not to use any high-volume, automated, electronic processes to obtain data from this service. Abuse of this service is monitored and actions in contravention of these terms will result in being permanently blacklisted. All data is (c) CentralNic Ltd (https://www.centralnic.com) Access to the Whois and RDAP services is rate limited. For more information, visit https://registrar-console.centralnic.com/pub/whois_guidance.
The first response from http://www.hey.car, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with hey.car. 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.