Alternatives to cip.cc
Matched automatically on description, category and technology. Only sites that pass our safety checks are shown. · Report a wrong match
cip.cc was registered on 14 Dec 2012 and is hosted on AS55990 HWCSNET Huawei Cloud Service data center in China. We couldn't read an SSL certificate for it when we last analysed it.
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 cip.cc. Refresh the analysis to check again.
728 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| clp.photography | Look-alike characters | 29 Oct 2026 | Checking… | Report → |
| clp.work | Look-alike characters | 28 Oct 2026 | Checking… | Report → |
| c1p.pics | Look-alike characters | 14 Oct 2026 | Checking… | Report → |
| clp.partners | Look-alike characters | 3 Oct 2026 | Checking… | Report → |
| c1p.net | Look-alike characters | 25 Sept 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is cip.cc’s name taken on other extensions?
Estimated visitors and engagement.
| Top countries | Share | Visits | Desktop | Mobile |
|---|---|---|---|---|
| China | 64.3% | — | — | — |
| United States | 8.9% | — | — | — |
| Taiwan | 6.6% | — | — | — |
| Japan | 5.4% | — | — | — |
| Hong Kong SAR China | 4% | — | — | — |
Every IP address cip.cc resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| cip.cc | 124.70.129.64 | 588 |
| Host | Name server | TTL |
|---|---|---|
| cip.cc | f1g1ns1.dnspod.net | 86400 |
| cip.cc | f1g1ns2.dnspod.net | 86400 |
| Host | Start of authority | TTL |
|---|---|---|
| cip.cc | f1g1ns1.dnspod.net freednsadmin.dnspod.com 1671887552 3600 180 1209600 180 | 180 |
No reviews yet. Used cip.cc? 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.
cip.cc has no community safety rating yet. We couldn't read an SSL certificate on it when we last analysed it. See Security →
The registration expired on 14 Dec 2023. See Overview →
cip.cc was registered on 14 Dec 2012, making it 13 years old. See Overview →
cip.cc is served from 1 IP address, mainly on AS55990 HWCSNET Huawei Cloud Service data center in China. See Hosting →
Raw registry data for cip.cc. May be redacted by privacy services.
{"objectClassName":"domain","handle":"102635443_DOMAIN_CC-VRSN","ldhName":"CIP.CC","links":[{"value":"https:\/\/tld-rdap.verisign.com\/cc\/v1\/domain\/CIP.CC","rel":"self","href":"https:\/\/tld-rdap.verisign.com\/cc\/v1\/domain\/CIP.CC","type":"application\/rdap+json"},{"value":"https:\/\/rdap.bizcn.com\/rdap\/domain\/CIP.CC","rel":"related","href":"https:\/\/rdap.bizcn.com\/rdap\/domain\/CIP.CC","type":"application\/rdap+json"}],"status":["client transfer prohibited"],"entities":[{"objectClassName":"entity","handle":"471","roles":["registrar"],"publicIds":[{"type":"IANA Registrar ID","identifier":"471"}],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text","Bizcn.com, Inc."]]],"entities":[{"objectClassName":"entity","roles":["abuse"],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text",""],["tel",{"type":"voice"},"uri",""],["email",{},"text",""]]]}]}],"events":[{"eventAction":"registration","eventDate":"2012-12-14T11:57:46Z"},{"eventAction":"expiration","eventDate":"2023-12-14T11:57:46Z"},{"eventAction":"last changed","eventDate":"2020-11-19T07:08:54Z"},{"eventAction":"last update of RDAP database","eventDate":"2023-07-09T23:31:54Z"}],"secureDNS":{"delegationSigned":false},"nameservers":[{"objectClassName":"nameserver","ldhName":"F1G1NS1.DNSPOD.NET"},{"objectClassName":"nameserver","ldhName":"F1G1NS2.DNSPOD.NET"}],"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.cip.cc, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with cip.cc. 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.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.
When the site first appeared, and what has changed since.
We record what changes from the next time this report is refreshed.