singlecell.shop was registered with whois.nic.shop on 5 May 2016. 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 singlecell.shop. Refresh the analysis to check again.
12 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| s1nglecell.com | Look-alike characters | 8 Oct 2026 | Checking… | Report → |
| singlecell.click | Other extension | 22 Oct 2026 | Checking… | Report → |
| singlecell.to | Other extension | 5 Oct 2026 | Checking… | Report → |
| singlecell.dev | Other extension | 22 Sept 2026 | Checking… | Report → |
| singlecell.co | Other extension | 19 Sept 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is singlecell.shop’s name taken on other extensions?
Every IP address singlecell.shop resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| singlecell.shop | 104.21.95.146 | 300 |
| singlecell.shop | 172.67.170.121 | 300 |
| Host | IPv6 address | TTL |
|---|---|---|
| singlecell.shop | 2606:4700:3036::6815:5f92 | 300 |
| singlecell.shop | 2606:4700:3036::ac43:aa79 | 300 |
| Host | Name server | TTL |
|---|---|---|
| singlecell.shop | zahir.ns.cloudflare.com | 21600 |
| singlecell.shop | zara.ns.cloudflare.com | 21600 |
| Host | Start of authority | TTL |
|---|---|---|
| singlecell.shop | zahir.ns.cloudflare.com dns.cloudflare.com 2323711324 10000 2400 604800 1800 | 1800 |
Other domains served from 104.21.95.146. Normal for shared hosting and CDNs.
No reviews yet. Used singlecell.shop? 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.
singlecell.shop has no community safety rating yet. We couldn't read an SSL certificate on it when we last analysed it. See Security →
singlecell.shop is registered through whois.nic.shop. See WHOIS →
singlecell.shop was registered on 5 May 2016, making it 10 years old. See Overview →
singlecell.shop is served from 2 IP addresses, mainly on AS13335. See Hosting →
Raw registry data for singlecell.shop. May be redacted by privacy services.
% IANA WHOIS server % for more information on IANA, visit http://www.iana.org % This query returned 1 object domain: SHOP organisation: GMO Registry, Inc. address: 26-1 Sakuragaoka-cho address: Shibuya-ku Tokyo address: Japan contact: administrative name: Representative Director and CEO organisation: GMO Registry, Inc. address: Cerulean Tower address: 26-1 Sakuragaoka-cho address: Shibuya-ku Tokyo 150-8512 address: Japan phone: +81354561601 fax-no: +81337805239 e-mail: [email protected] contact: technical name: Director organisation: GMO Registry, Inc. address: Cerulean Tower address: 26-1 Sakuragaoka-cho address: Shibuya-ku Tokyo 150-8512 address: Japan phone: +81354561601 fax-no: +81337805239 e-mail: [email protected] nserver: A.GMOREGISTRY.NET 2001:dcd:1:0:0:0:0:4 37.209.192.4 nserver: B.GMOREGISTRY.NET 2001:dcd:2:0:0:0:0:4 37.209.194.4 nserver: K.GMOREGISTRY.NET 37.209.196.4 nserver: L.GMOREGISTRY.NET 2001:dcd:4:0:0:0:0:4 37.209.198.4 ds-rdata: 50701 8 2 30f44f9e79f1119aebed349d3ec34f7aedd83a58f1e706d8303c3bbfe83bc7ec whois: whois.nic.shop status: ACTIVE remarks: Registration information: http://www.gmoregistry.com/en/ created: 2016-05-05 changed: 2019-08-20 source: IANA
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with singlecell.shop. 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.
When the site first appeared, and what has changed since.
We record what changes from the next time this report is refreshed.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.