dash.tokyo - robtex.com
dash.tokyo
tokyo
| DNSSEC | π Signed (DS record present) | ||||||
| NS | a.gmoregistry.net β | ||||||
| NS | b.gmoregistry.net | ||||||
| NS | k.gmoregistry.net | ||||||
| NS | l.gmoregistry.net | ||||||
| SOA | a.gmoregistry.netnoc@gmoregistry.net serial=1772247088 | ||||||
Same first word
Similar names
DNS History
12 records (8 active, 4 former)
βNSns-1404.awsdns-47.org2026-02-28 β 2026-02-28 Β· 2 obs
β 2026-02-28 03:21:12
βNSns-1716.awsdns-22.co.uk2026-02-28 β 2026-02-28 Β· 2 obs
β 2026-02-28 03:21:12
βNSns-333.awsdns-41.com2026-02-28 β 2026-02-28 Β· 2 obs
β 2026-02-28 03:21:12
βNSns-534.awsdns-02.net2026-02-28 β 2026-02-28 Β· 2 obs
β 2026-02-28 03:21:12
βMXcab0.mx.cloud-mail.jp2026-02-28 β 2026-02-28 Β· 2 obs
β 2026-02-28 03:21:12
βMXcab0.mx2.cloud-mail.jp2026-02-28 β 2026-02-28 Β· 2 obs
β 2026-02-28 03:21:12
βMXmx.hetemail.jp2018-07-29 β 2018-07-29 Β· 2 obs
β 2026-02-28 03:21:12
βA13.159.75.2272026-02-28 β 2026-02-28 Β· 2 obs
β 2026-02-28 03:21:12
βA157.7.44.1722018-07-29 β 2018-07-29 Β· 2 obs
β 2026-02-28 03:21:12
βA18.177.100.2042026-02-28 β 2026-02-28 Β· 2 obs
β 2026-02-28 03:21:12
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| tokyo | a.gmoregistry.net, b.gmoregistry.net, k.gmoregistry.net, l.gmoregistry.net | 7 records |
| dash.tokyo | ns-1404.awsdns-47.org, ns-333.awsdns-41.com, ns-534.awsdns-02.net, ns-1716.awsdns-22.co.uk | - |
β Authoritative Response
Server: 205.251.194.22
NS records: ns-1404.awsdns-47.org, ns-333.awsdns-41.com, ns-534.awsdns-02.net, ns-1716.awsdns-22.co.uk
π DNSSEC Status
β οΈ Insecure (no DNSSEC)
No DS record for dash.tokyo (unsigned zone)
β±οΈ Timing
Total: 616ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 18.177.100.204, 13.159.75.227 |
| NS | 4 | ns-1404.awsdns-47.org, ns-1716.awsdns-22.co.uk... |
| MX | 2 | cab0.mx.cloud-mail.jp (pri: 100), cab0.mx2.cloud-mail.jp (pri: 200) |
| TXT | 1 | v=spf1 +ip4:54.249.106.12/32 +ip4:54.249 |
| SOA | 1 | ns-534.awsdns-02.net awsdns-hostmaster.a |
π Glue Records Collected
Total: 7
Out-of-bailiwick: 7 (a.gmoregistry.net, b.gmoregistry.net, k.gmoregistry.net...)
AI analysis
dash.tokyo points to two IP numbers: 13.159.75.227 and 18.177.100.204.
Other host names such as recruit-ssdental.jp, www.sata-ko.com, www.gaiajp.net, ryokkaen.info and noble-microendo.jp share IP numbers with dash.tokyo.
dash.tokyo is delegated to four name servers: ns-333.awsdns-41.com, ns-534.awsdns-02.net, ns-1404.awsdns-47.org and ns-1716.awsdns-22.co.uk.
At least part of the name servers for dash.tokyo are shared with other domains, for instance snowflake.net, dmaengineers.com.au, reful-yachting.com, backhandsmash.nu and develop.ats.hrtech.rikunabi.com.
These name servers are commonly used with ns-204.awsdns-25.com, ns-761.awsdns-31.net, ns-1306.awsdns-35.org and ns-1424.awsdns-50.org.
Host names with two IP numbers:
ns-333.awsdns-41.com points to: 2600:9000:5301:4d00::1 and 205.251.193.77
ns-534.awsdns-02.net points to: 2600:9000:5302:1600::1 and 205.251.194.22
ns-1404.awsdns-47.org points to: 2600:9000:5305:7c00::1 and 205.251.197.124
ns-1716.awsdns-22.co.uk points to: 2600:9000:5306:b400::1 and 205.251.198.180
dash.tokyo is handled by two mail servers: cab0.mx.cloud-mail.jp and cab0.mx2.cloud-mail.jp.
dash.tokyo uses the same mail server setup as other domains, for instance result.tokyo, h-lig.com, ringring.bz, nagai-dc.com and cis2002.com.
dash.tokyo shares at least some mail servers with other domains, for example zeitetsuzuki.jp, kamakurayama-encuentro.com, star-souzoku-soudan.jp, aoba-jiyuujizai.co.jp and tsurumi-shinkyuu.com.
Hostnames with a single IP
cab0.mx.cloud-mail.jp resolves to: 59.157.130.3.
cab0.mx2.cloud-mail.jp resolves to: 202.210.185.137.