Alternatives to datingchat.co
Matched automatically on description, category and technology. Only sites that pass our safety checks are shown. · Report a wrong match
datingchat.co was registered with Name.com, Inc. on 18 Feb 2020. Its SSL certificate from Let's Encrypt expired on 20 Mar 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.
7 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| datingchat.store | Other extension | 26 Oct 2026 | Checking… | Report → |
| ratingchat.app | Typo | 3 Oct 2026 | Checking… | Report → |
| eatingchat.xyz | Typo | 23 Aug 2026 | Checking… | Report → |
| dotingchat.xyz | Typo | 25 Aug 2026 | Checking… | Report → |
| batingchat.xyz | Typo | 22 Aug 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is datingchat.co’s name taken on other extensions?
Estimated visitors and engagement.
| Top countries | Share | Visits | Desktop | Mobile |
|---|---|---|---|---|
| United States | 28% | — | — | — |
| Germany | 20.4% | — | — | — |
| Spain | 11.5% | — | — | — |
| Poland | 6.3% | — | — | — |
| Italy | 6.2% | — | — | — |
Every IP address datingchat.co resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| datingchat.co | 104.21.63.248 | 300 |
| datingchat.co | 172.67.173.99 | 300 |
| Host | IPv6 address | TTL |
|---|---|---|
| datingchat.co | 2606:4700:3031::ac43:ad63 | 300 |
| datingchat.co | 2606:4700:3035::6815:3ff8 | 300 |
| Host | Name server | TTL |
|---|---|---|
| datingchat.co | lou.ns.cloudflare.com | 21600 |
| datingchat.co | mia.ns.cloudflare.com | 21600 |
| Host | Start of authority | TTL |
|---|---|---|
| datingchat.co | lou.ns.cloudflare.com dns.cloudflare.com 2328928571 10000 2400 604800 1800 | 1800 |
Other domains served from 104.21.63.248. Normal for shared hosting and CDNs.
No reviews yet. Used datingchat.co? 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 datingchat.co excellent for safety (80/100). Its SSL certificate expired on 20 Mar 2024. See Security →
datingchat.co is registered through Name.com, Inc. The owner's details are hidden by a privacy service in the public WHOIS record. See WHOIS →
The registration expired on 18 Feb 2025. See Overview →
datingchat.co was registered on 18 Feb 2020, making it 6 years old. See Overview →
datingchat.co is served from 2 IP addresses, mainly on AS13335. See Hosting →
Raw registry data for datingchat.co. May be redacted by privacy services.
Domain Name: datingchat.co Registry Domain ID: DC9066216183E49BA911BB09C0F42A207-NSR Registrar WHOIS Server: Registrar URL: www.name.com Updated Date: 2024-02-13T13:28:10Z Creation Date: 2020-02-18T10:26:28Z Registry Expiry Date: 2025-02-18T10:26:28Z Registrar: Name.com, Inc. Registrar IANA ID: 625 Registrar Abuse Contact Email: abuse@name.com Registrar Abuse Contact Phone: +1.7203101849 Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Registry Registrant ID: REDACTED FOR PRIVACY Registrant Name: REDACTED FOR PRIVACY Registrant Organization: Domain Protection Services, Inc. Registrant Street: REDACTED FOR PRIVACY Registrant Street: REDACTED FOR PRIVACY Registrant Street: REDACTED FOR PRIVACY Registrant City: REDACTED FOR PRIVACY Registrant State/Province: CO Registrant Postal Code: REDACTED FOR PRIVACY Registrant Country: US Registrant Phone: REDACTED FOR PRIVACY Registrant Phone Ext: REDACTED FOR PRIVACY Registrant Fax: REDACTED FOR PRIVACY Registrant Fax Ext: REDACTED FOR PRIVACY 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. Registry Admin ID: REDACTED FOR PRIVACY Admin Name: REDACTED FOR PRIVACY Admin Organization: REDACTED FOR PRIVACY Admin Street: REDACTED FOR PRIVACY Admin Street: REDACTED FOR PRIVACY Admin Street: REDACTED FOR PRIVACY Admin City: REDACTED FOR PRIVACY Admin State/Province: REDACTED FOR PRIVACY Admin Postal Code: REDACTED FOR PRIVACY Admin Country: REDACTED FOR PRIVACY Admin Phone: REDACTED FOR PRIVACY Admin Phone Ext: REDACTED FOR PRIVACY Admin Fax: REDACTED FOR PRIVACY Admin Fax Ext: REDACTED FOR PRIVACY 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. Registry Tech ID: REDACTED FOR PRIVACY Tech Name: REDACTED FOR PRIVACY Tech Organization: REDACTED FOR PRIVACY Tech Street: REDACTED FOR PRIVACY Tech Street: REDACTED FOR PRIVACY Tech Street: REDACTED FOR PRIVACY Tech City: REDACTED FOR PRIVACY Tech State/Province: REDACTED FOR PRIVACY Tech Postal Code: REDACTED FOR PRIVACY Tech Country: REDACTED FOR PRIVACY Tech Phone: REDACTED FOR PRIVACY Tech Phone Ext: REDACTED FOR PRIVACY Tech Fax: REDACTED FOR PRIVACY Tech Fax Ext: REDACTED FOR PRIVACY 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: lou.ns.cloudflare.com Name Server: mia.ns.cloudflare.com DNSSEC: unsigned URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/ >>> Last update of WHOIS database: 2024-02-15T09:03:25Z <<< For more information on Whois status codes, please visit https://icann.org/epp The above WHOIS results have been redacted to remove potential personal data. The full WHOIS output may be available to individuals and organisations with a legitimate interest in accessing this data not outweighed by the fundamental privacy rights of the data subject. To find out more, or to make a request for access, please visit: RDDSrequest.nic.co. .CO Internet, S.A.S., the Administrator for .CO, has collected this information for the WHOIS database through Accredited Registrars. This information is provided to you for informational purposes only and is designed to assist persons in determining contents of a domain name registration record in the .CO Internet registry database. .CO Internet makes this information available to you "as is" and does not guarantee its accuracy. By submitting a WHOIS query, you agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data: (1) to allow, enable, or otherwise support the transmission of mass unsolicited, commercial advertising or solicitations via direct mail, electronic mail, or by telephone; (2) in contravention of any applicable data and privacy protection laws; or (3) to enable high volume, automated, electronic processes that apply to the registry (or its systems). Compilation, repackaging, dissemination, or other use of the WHOIS database in its entirety, or of a substantial portion thereof, is not allowed without .CO Internet's prior written permission. .CO Internet reserves the right to modify or change these conditions at any time without prior or subsequent notification of any kind. By executing this query, in any manner whatsoever, you agree to abide by these terms. In some limited cases, domains that might appear as available in whois might not actually be available as they could be already registered and the whois not yet updated and/or they could be part of the Restricted list. In this cases, performing a check through your Registrar's (EPP check) will give you the actual status of the domain. Additionally, domains currently or previously used as extensions in 3rd level domains will not be available for registration in the 2nd level. For example, org.co, mil.co, edu.co, com.co, net.co, nom.co, arts.co, firm.co, info.co, int.co, web.co, rec.co, co.co. NOTE: FAILURE TO LOCATE A RECORD IN THE WHOIS DATABASE IS NOT INDICATIVE OF THE AVAILABILITY OF A DOMAIN NAME. All domain names are subject to certain additional domain name registration rules. For details, please visit our site at www.cointernet.co <http://www.cointernet.co>.
The first response from http://www.datingchat.co, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with datingchat.co. 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.