3535.tokyo is registered with whois.nic.tokyo and is hosted on AS7506 in Japan. Its SSL certificate from Let's Encrypt expired on 9 Sept 2025, and the site does not support HTTP/3.
What security vendors and the WOT community say about this domain.
Is 3535.tokyo’s name taken on other extensions?
Every IP address 3535.tokyo resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| 3535.tokyo | 157.7.107.96 | 3600 |
| Host | Mail server | TTL |
|---|---|---|
| 3535.tokyo | 50 mx01.lolipop.jp | 3600 |
| Host | Name server | TTL |
|---|---|---|
| 3535.tokyo | dns01.muumuu-domain.com | 3600 |
| 3535.tokyo | dns02.muumuu-domain.com | 3600 |
| Host | Text | TTL |
|---|---|---|
| 3535.tokyo | "v=spf1 include:_spf.lolipop.jp ~all" | 3600 |
| Host | Start of authority | TTL |
|---|---|---|
| 3535.tokyo | dns01.muumuu-domain.com postmaster.3535.tokyo 1718395876 3600 1800 604800 3600 | 3600 |
Other domains served from 157.7.107.96. Normal for shared hosting and CDNs.
No reviews yet. Used 3535.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.
3535.tokyo has no community safety rating yet. Its SSL certificate expired on 9 Sept 2025. See Security →
3535.tokyo is registered through whois.nic.tokyo. See WHOIS →
3535.tokyo is served from 1 IP address, mainly on AS7506 in Japan. See Hosting →
Raw registry data for 3535.tokyo. May be redacted by privacy services.
Server is busy now, please try again later.
The first response from http://www.3535.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 3535.tokyo. Data is collected independently from public sources and some figures are estimates, provided for information only.