tooth-hack.tokyo is registered with whois.nic.tokyo and is hosted on AS37907 Digirock Inc. in Japan. Its SSL certificate from Let's Encrypt expired on 26 Nov 2024, and the site does not support HTTP/3.
What security vendors and the WOT community say about this domain.
Is tooth-hack.tokyo’s name taken on other extensions?
Every IP address tooth-hack.tokyo resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| tooth-hack.tokyo | 183.90.183.141 | 3600 |
| Host | Mail server | TTL |
|---|---|---|
| tooth-hack.tokyo | 10 tooth-hack.tokyo | 3600 |
| Host | Name server | TTL |
|---|---|---|
| tooth-hack.tokyo | ns1.rakko.zone | 14400 |
| tooth-hack.tokyo | ns2.rakko.zone | 14400 |
| Host | Text | TTL |
|---|---|---|
| tooth-hack.tokyo | "v=spf1 +a +mx +ip4:183.90.183.141 ~all" | 3600 |
| Host | Start of authority | TTL |
|---|---|---|
| tooth-hack.tokyo | ns1.rakko.zone hostmaster.tooth-hack.tokyo 2024012001 10380 3600 604800 3600 | 3600 |
Other domains served from 183.90.183.141. Normal for shared hosting and CDNs.
No reviews yet. Used tooth-hack.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.
tooth-hack.tokyo has no community safety rating yet. Its SSL certificate expired on 26 Nov 2024. See Security →
tooth-hack.tokyo is registered through whois.nic.tokyo. See WHOIS →
tooth-hack.tokyo is served from 1 IP address, mainly on AS37907 Digirock Inc. in Japan. See Hosting →
Raw registry data for tooth-hack.tokyo. May be redacted by privacy services.
Server is busy now, please try again later.
The first response from http://www.tooth-hack.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 tooth-hack.tokyo. Data is collected independently from public sources and some figures are estimates, provided for information only.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.