dash.tokyo - robtex.com

dash.tokyo

DNSSEC⚠️ Not signed
A13.159.75.227πŸ‡ΊπŸ‡Έ Amazon13.158.0.0/15 EC2 NRT prefix
PTRec2-13-159-75-227.ap-northeast-1.compute.amazonaws.com
A18.177.100.204πŸ‡―πŸ‡΅ Amazon18.176.0.0/15 EC2 NRT prefix
NSns-534.awsdns-02.net ⭐
A2600:9000:5302:1600::1πŸ‡ΊπŸ‡Έ Amazon2600:9000:5302::/48 - CloudFront
PTRns-534.awsdns-02.net
A205.251.194.22πŸ‡ΊπŸ‡Έ Amazon205.251.194.0/24 prefix
PTRns-534.awsdns-02.net
NSns-1404.awsdns-47.org
A2600:9000:5305:7c00::1πŸ‡ΊπŸ‡Έ Amazon2600:9000:5305::/48 - CloudFront
PTRns-1404.awsdns-47.org
A205.251.197.124πŸ‡ΊπŸ‡Έ Amazon205.251.197.0/24 prefix
PTRns-1404.awsdns-47.org
NSns-1716.awsdns-22.co.uk
A2600:9000:5306:b400::1πŸ‡ΊπŸ‡Έ Amazon2600:9000:5306::/48 - CloudFront
PTRns-1716.awsdns-22.co.uk
A205.251.198.180πŸ‡ΊπŸ‡Έ Amazon205.251.198.0/24 prefix
PTRns-1716.awsdns-22.co.uk
NSns-333.awsdns-41.com
A2600:9000:5301:4d00::1πŸ‡ΊπŸ‡Έ Amazon2600:9000:5301::/48 - CloudFront
PTRns-333.awsdns-41.com
A205.251.193.77πŸ‡ΊπŸ‡Έ Amazon205.251.193.0/24 prefix
PTRns-333.awsdns-41.com
MXcab0.mx.cloud-mail.jp ⭐
A59.157.130.3πŸ‡―πŸ‡΅ FBDC59.157.128.0/18 FreeBit CIDR X-Keiro:nic-noc@FreeBit.NET
PTRmail0.cloud-mail.jp
MXcab0.mx2.cloud-mail.jp(200)
A202.210.185.137πŸ‡―πŸ‡΅ BEKKOAME202.210.128.0/18 INTERNET INC.
TXTv=spf1 +ip4:54.249.106.12/32 +ip4:54.249.83.183/32 +a:cab0.spf.cloud-mail.jp ...
SOAns-534.awsdns-02.netawsdns-hostmaster@amazon.com serial=1

tokyo

DNSSECπŸ”’ Signed (DS record present)
NSa.gmoregistry.net ⭐
NSb.gmoregistry.net
NSk.gmoregistry.net
NSl.gmoregistry.net
SOAa.gmoregistry.netnoc@gmoregistry.net serial=1772247088

Same first word

Similar names

DNS History

12 records (8 active, 4 former)

20192020202120222023202420252026NSns-1404.awsdns-47.orgns-1716.awsdns-22.co.ukns-333.awsdns-41.comns-534.awsdns-02.netdns0.heteml.jpdns1.heteml.jpMXcab0.mx.cloud-mail.jpcab0.mx2.cloud-mail.jpmx.hetemail.jpA13.159.75.22718.177.100.204157.7.44.172
β—‹NSdns0.heteml.jp2018-07-29 β†’ 2018-07-29 Β· 2 obs
● 2018-07-29 09:08:06
β—‹ 2026-02-28 03:21:12
β—‹NSdns1.heteml.jp2018-07-29 β†’ 2018-07-29 Β· 2 obs
● 2018-07-29 09:08:06
β—‹ 2026-02-28 03:21:12
●NSns-1404.awsdns-47.org2026-02-28 β†’ 2026-02-28 Β· 2 obs
β—‹ 2018-07-29 09:08:06
● 2026-02-28 03:21:12
●NSns-1716.awsdns-22.co.uk2026-02-28 β†’ 2026-02-28 Β· 2 obs
β—‹ 2018-07-29 09:08:06
● 2026-02-28 03:21:12
●NSns-333.awsdns-41.com2026-02-28 β†’ 2026-02-28 Β· 2 obs
β—‹ 2018-07-29 09:08:06
● 2026-02-28 03:21:12
●NSns-534.awsdns-02.net2026-02-28 β†’ 2026-02-28 Β· 2 obs
β—‹ 2018-07-29 09:08:06
● 2026-02-28 03:21:12
●MXcab0.mx.cloud-mail.jp2026-02-28 β†’ 2026-02-28 Β· 2 obs
β—‹ 2018-07-29 09:08:06
● 2026-02-28 03:21:12
●MXcab0.mx2.cloud-mail.jp2026-02-28 β†’ 2026-02-28 Β· 2 obs
β—‹ 2018-07-29 09:08:06
● 2026-02-28 03:21:12
β—‹MXmx.hetemail.jp2018-07-29 β†’ 2018-07-29 Β· 2 obs
● 2018-07-29 09:08:06
β—‹ 2026-02-28 03:21:12
●A13.159.75.2272026-02-28 β†’ 2026-02-28 Β· 2 obs
β—‹ 2018-07-29 09:08:06
● 2026-02-28 03:21:12
β—‹A157.7.44.1722018-07-29 β†’ 2018-07-29 Β· 2 obs
● 2018-07-29 09:08:06
β—‹ 2026-02-28 03:21:12
●A18.177.100.2042026-02-28 β†’ 2026-02-28 Β· 2 obs
β—‹ 2018-07-29 09:08:06
● 2026-02-28 03:21:12

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
tokyoa.gmoregistry.net, b.gmoregistry.net, k.gmoregistry.net, l.gmoregistry.net7 records
dash.tokyons-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

TypeCountSample Data
A218.177.100.204, 13.159.75.227
NS4ns-1404.awsdns-47.org, ns-1716.awsdns-22.co.uk...
MX2cab0.mx.cloud-mail.jp (pri: 100), cab0.mx2.cloud-mail.jp (pri: 200)
TXT1v=spf1 +ip4:54.249.106.12/32 +ip4:54.249
SOA1ns-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.