tokyomotion.net
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200Family DNS blockedSSL: 90 days left11 years oldTranco #1525
55
tokyomotion.net was registered on 31 Aug 2015 via GoDaddy.com, LLC and the registry expiry is 31 Aug 2027. WHOIS data came from RDAP at https://rdap.verisign.com/net/v1/domain/tokyomotion.net.
tokyomotion.net publishes 2 nameservers. DNSSEC is not signed.
tokyomotion.net has 1 IPv4 address (64.187.150.214). The geolocation database places 64.187.150.214 in Fremont (East Industrial), United States.
The TLS certificate from GoDaddy TLS Intermediate CA DV - R1v1 is valid and has 90 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Apache HTTP Server, Bootstrap, Google Analytics, Google Hosted Libraries and jQuery. The fingerprints ran on the homepage that was already downloaded.
Domain · RDAP/WHOIS
tokyomotion.net was registered on 31 Aug 2015 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://rdap.verisign.com/net/v1/domain/tokyomotion.net.
| Registered | since 31 Aug 2015 |
|---|---|
| Created | 31 August 2015 |
| Updated | 1 September 2026 |
| Expires | 31 August 2027 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | ns1.tokyomotion.net, ns2.tokyomotion.net |
| DNSSEC | no |
| Source | https://rdap.verisign.com/net/v1/domain/tokyomotion.net |
tokyomotion.net carries the status "client delete prohibited". The registrar has asked the registry to refuse a delete. This is an EPP status on the domain object. It does not say the website is safe, and it does not name the person who registered it.
tokyomotion.net carries the status "client renew prohibited". The registrar has asked the registry to refuse a renewal. The expiry date still stands until a different status is set.
tokyomotion.net carries the status "client transfer prohibited". The registrar has asked the registry to refuse a transfer to another registrar. The status is a lock on the domain object. It is not evidence about the content of the site.
tokyomotion.net carries the status "client update prohibited". The registrar has asked the registry to refuse updates to the domain object. Contact and nameserver changes wait until the lock is lifted by the registrar of record.
Nameserver ns1.tokyomotion.net is published for tokyomotion.net in the registration record from https://rdap.verisign.com/net/v1/domain/tokyomotion.net.
Nameserver ns2.tokyomotion.net is published for tokyomotion.net in the registration record from https://rdap.verisign.com/net/v1/domain/tokyomotion.net.
DNS
tokyomotion.net has 1 address record, 2 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 64.187.150.214 |
|---|---|
| AAAA | — |
| NS | ns1.tokyomotion.net, ns2.tokyomotion.net |
| MX | mail.protonmail.ch (10) Proton, mailsec.protonmail.ch (20) Proton |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at tokyomotion.net is "v=spf1 a:manage.tokyomotion.net a:www.tokyomotion.net ip4:64.187.150.94 ip4:64.187.150.93 include:_spf.protonmail.ch ~all".
IPv4 address 64.187.150.214 answers for tokyomotion.net at resolver 1.1.1.1:53.
Mail exchanger mail.protonmail.ch has preference 10. The host is recognised as Proton.
Mail exchanger mailsec.protonmail.ch has preference 20. The host is recognised as Proton.
Hosting and geo
tokyomotion.net is placed in Fremont (East Industrial), United States by the local geolocation database (db-ip).
| Address | 64.187.150.214 |
|---|---|
| Country | United States |
| City | Fremont (East Industrial) |
| Source | db-ip |
SSL/TLS
The certificate for tokyomotion.net is valid, with 90 days left and 2 subject alternative names. Source: tls:443.
| Issuer | GoDaddy TLS Intermediate CA DV - R1v1 |
|---|---|
| Subject | *.tokyomotion.net |
| Valid from | 16 July 2026 |
| Valid until | 30 January 2027 |
| Days left | 90 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.tokyomotion.net, tokyomotion.net.
Tech stack
Tech detection checked the fetched homepage and named 5 products. Source: wappalyzergo.
- Apache HTTP Server · Web servers
- Bootstrap · UI frameworks
- Google Analytics · Analytics
- Google Hosted Libraries · CDN
- jQuery · JavaScript libraries
Apache HTTP Server is filed under Web servers.
Bootstrap is filed under UI frameworks.
Google Analytics is filed under Analytics.
Google Hosted Libraries is filed under CDN.
jQuery is filed under JavaScript libraries.
On-page checks
The homepage returned HTTP 200 in 150 ms. The target title is 31 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 150 ms |
| Title length | 31 yes |
| Quoted title | "Free Porn Videos - TOKYO Motion" |
| Meta description | "Free Japanese Porn Videos" yes |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | index, follow |
| Canonical | https%3A%2F%2Fwww.tokyomotion.net |
| Language | en |
| Links | 130 |
| Images | 25 |
| Favicon | yes |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Security
Family DNS for tokyomotion.net is blocked, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | blocked |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Cloudflare family DNS returned a block for tokyomotion.net. That resolver covers adult and malware names.
Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.
Score breakdown
Availability 25 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 20 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 5 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 0 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.
Safety lists 0 of 15. Points only when the checks ran and came back clean. Unknown is not clean.
Domain age 5 of 5. Five points at one year, two points at 30 days.
Change history
- October 2026: geo city changed from empty to Fremont (East Industrial).
- October 2026: geo country changed from empty to United States.
Questions
Is tokyomotion.net safe?
Cloudflare family DNS returned a block for tokyomotion.net. That resolver covers adult and malware names.
Who hosts tokyomotion.net?
tokyomotion.net is placed in Fremont (East Industrial), United States.
When does tokyomotion.net expire?
tokyomotion.net expires on 31 August 2027 according to https://rdap.verisign.com/net/v1/domain/tokyomotion.net.
Who owns tokyomotion.net?
The registry did not return a person or a company for tokyomotion.net. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://rdap.verisign.com/net/v1/domain/tokyomotion.net at 2026-10-30T14:56:08Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:56:08Z
- TLS source tls:443 at 2026-10-30T14:56:08Z
- HTTP source https://tokyomotion.net/ at 2026-10-30T14:56:08Z
- Tech source wappalyzergo at 2026-10-30T14:56:08Z
- Geo source db-ip at 2026-10-30T14:56:08Z
- Safety source family DNS and local lists at 2026-10-30T14:56:08Z
Related reports
No other indexable reports share this TLD, host, or registrar yet.
Owner of this site?
Ask for a correction or for the report to be removed from search. Public DNS facts stay on the page. An optional badge is not inserted for you.
How to read this report
The sentences under each heading are filled from the latest snapshot. If a collector had nothing to say, that sentence is left out. The target site's own title and meta description, when shown, are quoted as measurements. They are not this page's title. Change history only lists a difference between two snapshots, so the first check starts the clock and later edits are the history. A malware blocklist is the only reason the homepage body is skipped. That fact stays on the report. It does not by itself drop the page from the sitemap or from related-report links.