[ DOMAIN ]
cri.st
#564,185Top 56.4%▼ 31,384
Overview
30-day trend
Last 6 frozen daily snapshots. See rank history for full detail.
- First seen
- Wed Jul 15 2026 00:38:21 GM
- TLD
- .st
- 24h change
- ▼ 31,384
- 7d change
- ▼ 31,384
- Score
- 1.00
- Snapshot
- 1970-01-01
Registered with ST Registry since , expires .
Technologies
Contacts
| Type | Value | Source | Last seen |
|---|---|---|---|
| [email protected] | text | 2026-07-15 00:44:09.508338+00 | |
| phone | 007813 34 | text | 2026-07-15 00:44:09.537221+00 |
| phone | 0 23.227.792 24 | text | 2026-07-15 00:44:09.511941+00 |
| phone | 109375 22 | text | 2026-07-15 00:44:09.531342+00 |
| phone | 1.205.084 1 | text | 2026-07-15 00:44:09.514122+00 |
| phone | 1.523.105-3 | text | 2026-07-15 00:44:09.520714+00 |
| phone | 16.082031 20 |
Rank history
6 daily snapshots tracked. Lower rank numbers indicate higher composite score.
Whois — cri.st
- Registrar
- ST Registry
- Created
- Expires
Full whois record
Whois Server Version 3.3.2 Domain Name: cri.st Registrar: ST Registry Name Server: jill.ns.cloudflare.com Name Server: seth.ns.cloudflare.com Status: clientTransferProhibited Updated Date: 2026-02-28 Creation Date: 2016-03-28 Expiration Date: 2027-03-28 >>> Last update of whois database: 2026-07-18T10:54:58Z <<< The data in the WHOIS database is protected by copyright. By submitting a WHOIS query, you agree that you will use this data only for lawful purposes according with the terms and policy that is publicly available on https://www.nic.st/terms-of-service and that, under no circumstances will you use this data to allow, enable, or otherwise support the transmission of mass unsolicited, commercial advertising or solicitations via direct mail, electronic mail, or by telephone; in contravention of any applicable data and privacy protection laws; or 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 ST Registry prior written permission. 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. ST Registry reserves the right to modify or change these conditions at any time without prior or subsequent notification of any kind. DOMAIN: cri.st REGISTRATION-SERVICE-PROVIDER: ST Registry URL: www.nic.st created-date: 2016-03-28 00:51:41 updated-date: 2026-02-28 03:14:02 expiration-date: 2027-03-28 00:51:41 registrant-organization: Tripl3Click registrant-name: Crist (STR56F8801D0EA0A) registrant-street: Espana 2274 registrant-city: Buenos Aires registrant-state: registrant-zip: 1888 registrant-country: AR registrant-phone: registrant-fax: registrant-email: [email protected] admin-organization: Tripl3Click admin-name: Crist (STR56F8801CBEE32) admin-street: Espana 2274 admin-city: Buenos Aires admin-state: admin-zip: 1888 admin-country: AR admin-phone: admin-fax: admin-email: [email protected] tech-organization: Tripl3Click tech-name: Crist (STR56F8801CD6DE5) tech-street: Espana 2274 tech-city: Buenos Aires tech-state: tech-zip: 1888 tech-country: AR tech-phone: tech-fax: tech-email: [email protected] billing-organization: Tripl3Click billing-name: Crist (STR56F8801CECC19) billing-street: Espana 2274 billing-city: Buenos Aires billing-state: billing-zip: 1888 billing-country: AR billing-phone: billing-fax: billing-email: [email protected] nameserver: jill.ns.cloudflare.com nameserver: seth.ns.cloudflare.com
Registration expiry lifecycle
Upcoming
- Expected expiry
- 2027-03-28
- Registrar
- ST Registry
- Next verification
- 2026-12-28
- Checks completed
- 0
This is the latest registration state. DNS is supporting evidence; only an explicit registry or WHOIS not-found response confirms expiration.