Alternatives to blcloud.jp
Matched automatically on description, category and technology. Only sites that pass our safety checks are shown. · Report a wrong match
blcloud.jp was registered with whois.jprs.jp on 5 Aug 1986. 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 blcloud.jp. Refresh the analysis to check again.
74 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| bicloud.uz | Look-alike characters | 15 Oct 2026 | Checking… | Report → |
| glcloud.site | Typo | 13 Nov 2026 | Checking… | Report → |
| nlcloud.online | Typo | 7 Nov 2026 | Checking… | Report → |
| bpcloud.ru | Typo | 23 Oct 2026 | Checking… | Report → |
| bkcloud.cyou | Typo | 6 Oct 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is blcloud.jp’s name taken on other extensions?
Estimated visitors and engagement.
| Top countries | Share | Visits | Desktop | Mobile |
|---|---|---|---|---|
| Japan | 1% | — | — | — |
| Host | Name server | TTL |
|---|---|---|
| blcloud.jp | ns-cloud-b1.googledomains.com | 21600 |
| blcloud.jp | ns-cloud-b2.googledomains.com | 21600 |
| blcloud.jp | ns-cloud-b3.googledomains.com | 21600 |
| blcloud.jp | ns-cloud-b4.googledomains.com | 21600 |
| Host | Start of authority | TTL |
|---|---|---|
| blcloud.jp | ns-cloud-b1.googledomains.com cloud-dns-hostmaster.google.com 1 21600 3600 259200 300 | 21600 |
No reviews yet. Used blcloud.jp? 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.
blcloud.jp has no community safety rating yet. We couldn't read an SSL certificate on it when we last analysed it. See Security →
blcloud.jp is registered through whois.jprs.jp. See WHOIS →
blcloud.jp was registered on 5 Aug 1986, making it 40 years old. See Overview →
Raw registry data for blcloud.jp. 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: whois.jprs.jp domain: JP organisation: Japan Registry Services Co., Ltd. address: Chiyoda First Bldg. East 13F address: 3-8-1 Nishi-Kanda address: Chiyoda-ku Tokyo 101-0065 address: Japan contact: administrative name: Koki Higashida organisation: Japan Registry Services Co., Ltd. address: Chiyoda First Bldg. East 13F address: 3-8-1 Nishi-Kanda address: Chiyoda-ku Tokyo 101-0065 address: Japan phone: +81 3 5215 8451 fax-no: +81 3 5215 8452 e-mail: higashida@jprs.co.jp contact: technical name: Koki Higashida organisation: Japan Registry Services Co., Ltd. address: Chiyoda First Bldg. East 13F address: 3-8-1 Nishi-Kanda address: Chiyoda-ku Tokyo 101-0065 address: Japan phone: +81 3 5215 8480 fax-no: +81 3 5215 8452 e-mail: tech-admin@jprs.jp nserver: A.DNS.JP 2001:dc4:0:0:0:0:0:1 203.119.1.1 nserver: B.DNS.JP 2001:dc2:0:0:0:0:0:1 202.12.30.131 nserver: C.DNS.JP 156.154.100.5 2001:502:ad09:0:0:0:0:5 nserver: D.DNS.JP 2001:240:0:0:0:0:0:53 210.138.175.244 nserver: E.DNS.JP 192.50.43.53 2001:200:c000:0:0:0:0:35 nserver: F.DNS.JP 150.100.6.8 2001:2f8:0:100:0:0:0:153 nserver: G.DNS.JP 203.119.40.1 nserver: H.DNS.JP 161.232.72.25 2a01:8840:1bc:0:0:0:0:25 ds-rdata: 39916 8 2 b36b524989bf0625efd9b0877e74e77f052248fde965b6e3c327d9c06af1d080 whois: whois.jprs.jp status: ACTIVE remarks: Registration information: https://jprs.jp/ created: 1986-08-05 changed: 2022-11-09 source: IANA
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with blcloud.jp. 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.