Alternatives to claropay.com
Matched automatically on description, category and technology. Only sites that pass our safety checks are shown. · Report a wrong match
claropay.com was registered on 21 Feb 2013 and is hosted on AS14618 Amazon.com Inc. in United States of America. Its SSL certificate from DigiCert Inc expired on 2 Nov 2024, and the site does not support HTTP/3.
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.
11 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| claripay.io | Typo | 26 Aug 2026 | Checking… | Report → |
| claropax.com | Typo | 11 Oct 2026 | Checking… | Report → |
| clyropay.digital | Typo | 27 Oct 2026 | Checking… | Report → |
| claroway.info | Typo | 22 Oct 2026 | Checking… | Report → |
| claroday.app | Typo | 9 Oct 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is claropay.com’s name taken on other extensions?
Estimated visitors and engagement.
| Top countries | Share | Visits | Desktop | Mobile |
|---|---|---|---|---|
| Mexico | 91.5% | — | — | — |
| Colombia | 3.1% | — | — | — |
| Argentina | 2.4% | — | — | — |
| United States | 1.6% | — | — | — |
| United Kingdom | 1.4% | — | — | — |
Every IP address claropay.com resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| claropay.com | 54.152.34.44 | 300 |
| Host | Mail server | TTL |
|---|---|---|
| claropay.com | 0 claropay-com.mail.protection.outlook.com | 3600 |
| Host | Name server | TTL |
|---|---|---|
| claropay.com | ns1.dlatv.net | 300 |
| claropay.com | ns2.dlatv.net | 300 |
| Host | Text | TTL |
|---|---|---|
| claropay.com | "amazonses:MzXyfit1Y2opRQvdH8kdF+TzZCGwJ7t/QXj48K+G8nA=" | 3600 |
| claropay.com | "ck1m7g1bl0ncpr4fgxxkbhd7q9j3zbv1" | 3600 |
| claropay.com | "dd3qz6zcr3g3s4smpdkmm7gp995kc09m" | 3600 |
| claropay.com | "ee67d2cd31b14800972ef6c43ab66501" | 3600 |
| claropay.com | "google-site-verification=fWbpyJ5fs-BpnqFi_D4k86PcSoHGY-g_5pNJrV0IX9s" | 3600 |
| claropay.com | "google-site-verification=mNk6JcUqsGvyKyC3MSjjMKvFwVB-qHnRF79S7Lu8BCQ" | 3600 |
| claropay.com | "google-site-verification=W8OEC1v3r6EUPzxMbmaoi3drVCl-7HV0pEHSeQGgCZc" | 3600 |
| claropay.com | "h9m6snv4zqcfpt87b1hsxkf4ysqx8m7y" | 3600 |
| claropay.com | "MS=ms92643470" | 3600 |
| claropay.com | "v=spf1 include:_spf.mlsend.com include:_spf.mlsend.com include:spf.protection.outlook.com -all" | 3600 |
| Host | Start of authority | TTL |
|---|---|---|
| claropay.com | ns1.dlatv.net dnsmaster.elsitio.com.ar 2023110606 3600 1800 604800 300 | 300 |
No reviews yet. Used claropay.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.
claropay.com has no community safety rating yet. Its SSL certificate expired on 2 Nov 2024. See Security →
The registration expired on 21 Feb 2024. See Overview →
claropay.com was registered on 21 Feb 2013, making it 13 years old. See Overview →
claropay.com is served from 1 IP address, mainly on AS14618 Amazon.com Inc. in United States of America. See Hosting →
Raw registry data for claropay.com. May be redacted by privacy services.
{"objectClassName":"domain","handle":"1781816670_DOMAIN_COM-VRSN","ldhName":"CLAROPAY.COM","links":[{"value":"https:\/\/rdap.verisign.com\/com\/v1\/domain\/CLAROPAY.COM","rel":"self","href":"https:\/\/rdap.verisign.com\/com\/v1\/domain\/CLAROPAY.COM","type":"application\/rdap+json"},{"value":"https:\/\/apis.cscglobal.com\/dbs\/rdap-api\/v1\/domain\/CLAROPAY.COM","rel":"related","href":"https:\/\/apis.cscglobal.com\/dbs\/rdap-api\/v1\/domain\/CLAROPAY.COM","type":"application\/rdap+json"}],"status":["client transfer prohibited"],"entities":[{"objectClassName":"entity","handle":"299","roles":["registrar"],"publicIds":[{"type":"IANA Registrar ID","identifier":"299"}],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text","CSC Corporate Domains, Inc."]]],"entities":[{"objectClassName":"entity","roles":["abuse"],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text",""],["tel",{"type":"voice"},"uri","tel:8887802723"],["email",{},"text","domainabuse@cscglobal.com"]]]}]}],"events":[{"eventAction":"registration","eventDate":"2013-02-21T17:24:14Z"},{"eventAction":"expiration","eventDate":"2024-02-21T17:24:14Z"},{"eventAction":"last changed","eventDate":"2023-02-17T06:11:56Z"},{"eventAction":"last update of RDAP database","eventDate":"2023-07-10T01:49:15Z"}],"secureDNS":{"delegationSigned":false},"nameservers":[{"objectClassName":"nameserver","ldhName":"NS1.DLATV.NET"},{"objectClassName":"nameserver","ldhName":"NS2.DLATV.NET"},{"objectClassName":"nameserver","ldhName":"NS5.DLATV.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.claropay.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 claropay.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.
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.