levent.tokyo is hosted on AS7506 Interq Gmo Internet Group Inc. 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 levent.tokyo. Refresh the analysis to check again.
Is levent.tokyo’s name taken on other extensions?
Every IP address levent.tokyo resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| levent.tokyo | 160.251.71.22 | 600 |
| Host | Mail server | TTL |
|---|---|---|
| levent.tokyo | 10 mail86.onamae.ne.jp | 600 |
| Host | Name server | TTL |
|---|---|---|
| levent.tokyo | ns-rs1.gmoserver.jp | 600 |
| levent.tokyo | ns-rs2.gmoserver.jp | 600 |
| Host | Text | TTL |
|---|---|---|
| levent.tokyo | "v=spf1 include:_spf.onamae.ne.jp ~all" | 600 |
| Host | Start of authority | TTL |
|---|---|---|
| levent.tokyo | ns-rs1.gmoserver.jp hostmaster.gmoserver.jp 1730791309 3600 900 604800 600 | 600 |
Other domains served from 160.251.71.22. Normal for shared hosting and CDNs.
No reviews yet. Used levent.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.
levent.tokyo has no community safety rating yet. We couldn't read an SSL certificate on it when we last analysed it. See Security →
levent.tokyo is served from 1 IP address, mainly on AS7506 Interq Gmo Internet Group Inc. in Japan. See Hosting →
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with levent.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.
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.