tokyo-yy.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
HTTP 403SafeSSL: 64 days left7 years oldTranco #220273
65
tokyo-yy.com was registered on 5 Jul 2019 via Cloudflare, Inc. and the registry expiry is 5 Jul 2035. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/tokyo-yy.com.
tokyo-yy.com publishes 2 nameservers. DNSSEC is signed.
tokyo-yy.com has 2 IPv4 addresses (104.21.70.147, 172.67.136.190) and 2 IPv6 addresses (2606:4700:3030::6815:4693, 2606:4700:3036::ac43:88be). The geolocation database places 104.21.70.147 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 64 days left (TLS 1.3).
Tech detection named Cloudflare and HTTP/3. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for tokyo-yy.com in the checks that ran.
Domain · RDAP/WHOIS
tokyo-yy.com was registered on 5 Jul 2019 via Cloudflare, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/tokyo-yy.com.
| Registered | since 5 Jul 2019 |
|---|---|
| Created | 5 July 2019 |
| Updated | 9 June 2026 |
| Expires | 5 July 2035 |
| Registrar | Cloudflare, Inc. |
| Status | client transfer prohibited |
| Nameservers | melody.ns.cloudflare.com, stan.ns.cloudflare.com |
| DNSSEC | yes |
| Source | https://rdap.verisign.com/com/v1/domain/tokyo-yy.com |
tokyo-yy.com 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.
Nameserver melody.ns.cloudflare.com is published for tokyo-yy.com in the registration record from https://rdap.verisign.com/com/v1/domain/tokyo-yy.com.
Nameserver stan.ns.cloudflare.com is published for tokyo-yy.com in the registration record from https://rdap.verisign.com/com/v1/domain/tokyo-yy.com.
DNS
tokyo-yy.com has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.70.147, 172.67.136.190 |
|---|---|
| AAAA | 2606:4700:3030::6815:4693, 2606:4700:3036::ac43:88be |
| NS | melody.ns.cloudflare.com, stan.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 104.21.70.147 answers for tokyo-yy.com at resolver 1.1.1.1:53.
IPv4 address 172.67.136.190 answers for tokyo-yy.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3030::6815:4693 answers for tokyo-yy.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3036::ac43:88be answers for tokyo-yy.com at resolver 1.1.1.1:53.
Hosting and geo
tokyo-yy.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.70.147 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for tokyo-yy.com is valid, with 64 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | tokyo-yy.com |
| Valid from | 5 October 2026 |
| Valid until | 3 January 2027 |
| Days left | 64 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.tokyo-yy.com, tokyo-yy.com.
Tech stack
Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.
- Cloudflare · CDN
- HTTP/3 · Miscellaneous
Cloudflare is filed under CDN.
HTTP/3 is filed under Miscellaneous.
On-page checks
The homepage returned HTTP 403 in 20 ms. The target title is 16 characters and the page has 0 H1 headings.
| Status | 403 |
|---|---|
| TTFB | 20 ms |
| Title length | 16 yes |
| Quoted title | "Just a moment..." |
| Meta description | none no |
| H1 count | 0 |
| HSTS | no no |
| CSP | yes |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | noindex,nofollow |
| Canonical | — |
| Language | en-US |
| Links | 0 |
| Images | 0 |
| Favicon | no |
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 tokyo-yy.com is clear, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | clear |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | yes |
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 10 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 10 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.
Safety lists 15 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
First checked on 30 October 2026; changes will appear here.
Questions
Is tokyo-yy.com safe?
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
Who hosts tokyo-yy.com?
tokyo-yy.com is placed in Toronto, Canada.
When does tokyo-yy.com expire?
tokyo-yy.com expires on 5 July 2035 according to https://rdap.verisign.com/com/v1/domain/tokyo-yy.com.
Who owns tokyo-yy.com?
The registry did not return a person or a company for tokyo-yy.com. RDAP often redacts the registrant. The registrar on file is Cloudflare, Inc..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/tokyo-yy.com at 2026-10-30T14:17:22Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:17:22Z
- TLS source tls:443 at 2026-10-30T14:17:22Z
- HTTP source https://tokyo-yy.com/ at 2026-10-30T14:17:22Z
- Tech source wappalyzergo at 2026-10-30T14:17:22Z
- Geo source db-ip at 2026-10-30T14:17:22Z
- Safety source family DNS and local lists at 2026-10-30T14:17:22Z
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.