optimizer.tokyo was registered with whois.nic.tokyo on 16 Jan 2014 and is hosted on AS7506 in Japan. 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 optimizer.tokyo. Refresh the analysis to check again.
664 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| optimizer.ad | Other extension | 9 Nov 2026 | Checking… | Report → |
| optimizer.ninja | Other extension | 23 Oct 2026 | Checking… | Report → |
| otpimizer.ru | Typo | 23 Oct 2026 | Checking… | Report → |
| otpimizer.pro | Typo | 21 Oct 2026 | Checking… | Report → |
| optimizer.tools | Other extension | 12 Oct 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is optimizer.tokyo’s name taken on other extensions?
Every IP address optimizer.tokyo resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| optimizer.tokyo | 150.95.255.38 | 300 |
| Host | Mail server | TTL |
|---|---|---|
| optimizer.tokyo | 0 | 300 |
| Host | Name server | TTL |
|---|---|---|
| optimizer.tokyo | dns1.onamae.com | 300 |
| optimizer.tokyo | dns2.onamae.com | 300 |
| Host | Text | TTL |
|---|---|---|
| optimizer.tokyo | "v=spf1 -all" | 300 |
| Host | Start of authority | TTL |
|---|---|---|
| optimizer.tokyo | dns1.onamae.com hostmaster.onamae.com 16777216 3600 600 86400 300 | 300 |
Other domains served from 150.95.255.38. Normal for shared hosting and CDNs.
No reviews yet. Used optimizer.tokyo? 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.
optimizer.tokyo has no community safety rating yet. We couldn't read an SSL certificate on it when we last analysed it. See Security →
optimizer.tokyo is registered through whois.nic.tokyo. See WHOIS →
optimizer.tokyo was registered on 16 Jan 2014, making it 12 years old. See Overview →
optimizer.tokyo is served from 1 IP address, mainly on AS7506 in Japan. See Hosting →
Raw registry data for optimizer.tokyo. 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.nic.tokyo domain: TOKYO 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: +81 354561601 fax-no: +81 337805239 e-mail: newgtld@gmoregistry.com 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: +81 354561601 fax-no: +81 337805239 e-mail: newgtld@gmoregistry.com 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: 34775 8 2 009538d854dc2b09a147c657b496a8cd5151bc2fbadd83cf0c322f625fa5a7ce whois: whois.nic.tokyo status: ACTIVE remarks: Registration information: remarks: http://www.gmo-registry.com/en/ created: 2014-01-16 changed: 2019-08-20 source: IANA
The first response from http://www.optimizer.tokyo, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with optimizer.tokyo. 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.