rokki.studio was registered on 25 Jun 2015 and is hosted on AS47846 in Germany. 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 rokki.studio. Refresh the analysis to check again.
132 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| rokki.space | Other extension | 30 Oct 2026 | Checking… | Report → |
| rokki.fi | Other extension | 19 Oct 2026 | Checking… | Report → |
| tokki.casino | Typo | 15 Nov 2026 | Checking… | Report → |
| dokki.io | Typo | 8 Nov 2026 | Checking… | Report → |
| rokko.es | Typo | 8 Nov 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is rokki.studio’s name taken on other extensions?
Every IP address rokki.studio resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| rokki.studio | 91.195.240.94 | 300 |
| Host | Name server | TTL |
|---|---|---|
| rokki.studio | ns1bqx.name.com | 300 |
| rokki.studio | ns2dqx.name.com | 300 |
| rokki.studio | ns3qty.name.com | 300 |
| rokki.studio | ns4ghm.name.com | 300 |
| Host | Start of authority | TTL |
|---|---|---|
| rokki.studio | ns1.name.com hostmaster.nsone.net 1794890626 43200 7200 1209600 3600 | 3600 |
Other domains served from 91.195.240.94. Normal for shared hosting and CDNs.
No reviews yet. Used rokki.studio? 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.
rokki.studio has no community safety rating yet. We couldn't read an SSL certificate on it when we last analysed it. See Security →
rokki.studio was registered on 25 Jun 2015, making it 11 years old. See Overview →
rokki.studio is served from 1 IP address, mainly on AS47846 in Germany. See Hosting →
Raw registry data for rokki.studio. May be redacted by privacy services.
% IANA WHOIS server % for more information on IANA, visit http://www.iana.org % This query returned 1 object refer: domain: STUDIO organisation: Dog Beach, LLC address: c/o Identity Digital Inc. address: 10500 NE 8th Street, Suite 750 address: Bellevue WA 98004 address: United States of America (the) contact: administrative name: Vice President, Engineering organisation: Identity Digital Inc. address: 10500 NE 8th Street, Suite 750 address: Bellevue WA 98004 address: United States of America (the) phone: +1.425.298.2200 fax-no: +1.425.671.0020 e-mail: tldadmin@identity.digital contact: technical name: Senior Director, DNS Infrastructure Group organisation: Identity Digital Limited address: c/o Identity Digital Inc. address: 10500 NE 8th Street, Suite 750 address: Bellevue WA 98004 address: United States of America (the) phone: +1.425.298.2200 fax-no: +1.425.671.0020 e-mail: tldtech@identity.digital nserver: V0N0.NIC.STUDIO 2a01:8840:1e:0:0:0:0:3 65.22.28.3 nserver: V0N1.NIC.STUDIO 2a01:8840:1f:0:0:0:0:3 65.22.29.3 nserver: V0N2.NIC.STUDIO 2a01:8840:20:0:0:0:0:3 65.22.30.3 nserver: V0N3.NIC.STUDIO 161.232.14.3 2a01:8840:f8:0:0:0:0:3 nserver: V2N0.NIC.STUDIO 2a01:8840:21:0:0:0:0:3 65.22.31.3 nserver: V2N1.NIC.STUDIO 161.232.15.3 2a01:8840:f9:0:0:0:0:3 ds-rdata: 1354 8 2 d4289b105c9cb81d1ea631fe723a7dd3e9a52fb649b4a0a40c4890a9faa62846 ds-rdata: 35741 8 2 ea396815305687a68d5df9bac421daba8dad24ddf1d2e3d61ccdb0908dc93e7a whois: status: ACTIVE remarks: Registration information: https://www.identity.digital/ created: 2015-06-25 changed: 2026-11-10 source: IANA
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with rokki.studio. 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.
No changes seen since we started recording on 19 Nov 2026.