Alternatives to caloga.com
Matched automatically on description, category and technology. Only sites that pass our safety checks are shown. · Report a wrong match
caloga.com was registered on 4 Oct 1999 and is hosted on AS12876 Scaleway S.A.S. in France. We couldn't read an SSL certificate for it when we last analysed it. WOT's community rates its safety unsatisfactory (46/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.
We couldn't read an SSL certificate on port 443 when we last analysed caloga.com. Refresh the analysis to check again.
38 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| caliga.biz | Typo | 29 Oct 2026 | Checking… | Report → |
| daloga.cn | Typo | 7 Oct 2026 | Checking… | Report → |
| daloga.sk | Typo | 3 Oct 2026 | Checking… | Report → |
| caloba.app | Typo | 10 Sept 2026 | Checking… | Report → |
| calga.org | Typo | 11 Nov 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is caloga.com’s name taken on other extensions?
Estimated visitors and engagement.
Every IP address caloga.com resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| caloga.com | 62.210.164.229 | 3594 |
| Host | Mail server | TTL |
|---|---|---|
| caloga.com | 100 caloga-pub.caloga.com | 3600 |
| Host | Name server | TTL |
|---|---|---|
| caloga.com | ns1.caloga.com | 3600 |
| caloga.com | ns2.caloga.com | 3600 |
| Host | Text | TTL |
|---|---|---|
| caloga.com | "google-site-verification=04CkhI4pW5p64dU4tOdg3OaTReSL_OCTXnjaUYwOHd8" | 3600 |
| caloga.com | "google-site-verification=9LZAFdfyqgpn2D-oS67KM1XdgJpM_YbgrZXhEpc1StQ" | 3600 |
| caloga.com | "google-site-verification=dbo6ZOswAvbVe5xuYL5GwPz68jgutF7AAzw11YUDRTI" | 3600 |
| caloga.com | "google-site-verification=Dsr1Wi7jClD82g5I4K9z9oXcbyxA1YqVGNvck6vhrWM" | 3600 |
| caloga.com | "google-site-verification=EK8gJFqngDElkHcksgfxz-ZMFQhrVIWRpeS8h1NUHLU" | 3600 |
| caloga.com | "google-site-verification=h0fo6WbbX9hifFnG0CAkbPuFf8Mn8QgO6VykHR77uF8" | 3600 |
| caloga.com | "google-site-verification=soSaE0OvzQ6QyoYwC0HNanFQFoazCOks31_5toZ5Bkk" | 3600 |
| caloga.com | "google-site-verification=UEImXroioCNx2vmIs5A9bDc4izHYUXj8TbQHYb5UbUg" | 3600 |
| caloga.com | "v=spf1 ip4:62.210.164.224/28 ip4:195.154.149.64/27 ip4:62.210.118.192/27 ip4:154.44.178.0/23 ip4:154.56.82.0/23 include:cmailsys.com ~all" | 3600 |
| Host | Start of authority | TTL |
|---|---|---|
| caloga.com | ns1.caloga.com postmaster.caloga.com 2022071201 28800 7200 2419200 3600 | 3600 |
Other domains served from 62.210.164.229. Normal for shared hosting and CDNs.
No reviews yet. Used caloga.com? 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 caloga.com unsatisfactory for safety (46/100). We couldn't read an SSL certificate on it when we last analysed it. See Security →
The registration expired on 4 Oct 2024. See Overview →
caloga.com was registered on 4 Oct 1999, making it 27 years old. See Overview →
caloga.com is served from 1 IP address, mainly on AS12876 Scaleway S.A.S. in France. See Hosting →
Raw registry data for caloga.com. May be redacted by privacy services.
{"objectClassName":"domain","handle":"10956795_DOMAIN_COM-VRSN","ldhName":"CALOGA.COM","links":[{"value":"https:\/\/rdap.verisign.com\/com\/v1\/domain\/CALOGA.COM","rel":"self","href":"https:\/\/rdap.verisign.com\/com\/v1\/domain\/CALOGA.COM","type":"application\/rdap+json"},{"value":"https:\/\/rdap.networksolutions.com\/rdap\/domain\/CALOGA.COM","rel":"related","href":"https:\/\/rdap.networksolutions.com\/rdap\/domain\/CALOGA.COM","type":"application\/rdap+json"}],"status":["client transfer prohibited"],"entities":[{"objectClassName":"entity","handle":"2","roles":["registrar"],"publicIds":[{"type":"IANA Registrar ID","identifier":"2"}],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text","Network Solutions, LLC"]]],"entities":[{"objectClassName":"entity","roles":["abuse"],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text",""],["tel",{"type":"voice"},"uri","tel:+1.8003337680"],["email",{},"text","abuse@web.com"]]]}]}],"events":[{"eventAction":"registration","eventDate":"1999-10-04T15:04:14Z"},{"eventAction":"expiration","eventDate":"2024-10-04T15:04:14Z"},{"eventAction":"last changed","eventDate":"2023-06-26T16:45:40Z"},{"eventAction":"last update of RDAP database","eventDate":"2023-07-08T09:09:57Z"}],"secureDNS":{"delegationSigned":false},"nameservers":[{"objectClassName":"nameserver","ldhName":"NS1.CALOGA.COM"},{"objectClassName":"nameserver","ldhName":"NS2.CALOGA.COM"}],"rdapConformance":["rdap_level_0","icann_rdap_technical_implementation_guide_0","icann_rdap_response_profile_0"],"notices":[{"title":"Terms of Use","description":["Service subject to Terms of Use."],"links":[{"href":"https:\/\/www.verisign.com\/domain-names\/registration-data-access-protocol\/terms-service\/index.xhtml","type":"text\/html"}]},{"title":"Status Codes","description":["For more information on domain status codes, please visit https:\/\/icann.org\/epp"],"links":[{"href":"https:\/\/icann.org\/epp","type":"text\/html"}]},{"title":"RDDS Inaccuracy Complaint Form","description":["URL of the ICANN RDDS Inaccuracy Complaint Form: https:\/\/icann.org\/wicf"],"links":[{"href":"https:\/\/icann.org\/wicf","type":"text\/html"}]}]}The first response from http://www.caloga.com, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with caloga.com. 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.