tokyoactivity.com - robtex.com

tokyoactivity.com

DNSSEC⚠️ Not signed
A172.233.76.4πŸ‡―πŸ‡΅ AKAMAI-LINODE-AP172.233.64.0/19 Akamai Technologies
PTRfantail2.metroworks.co.jp
NSns1.metroworks.co.jp ⭐
A172.105.171.172πŸ‡¦πŸ‡Ί AKAMAI-LINODE-AP172.105.160.0/19 Akamai Technologies
PTRtoggle1.metroworks.co.jp
NSns1.japantravel.com
A172.105.171.172πŸ‡¦πŸ‡Ί AKAMAI-LINODE-AP172.105.160.0/19 Akamai Technologies
PTRtoggle1.metroworks.co.jp
NSns2.japantravel.com
A78.47.19.216πŸ‡©πŸ‡ͺ Hetzner78.46.0.0/15 HETZNER-RZ-NBG-BLK5
PTRwarbler.metroworks.co.jp
NSns2.metroworks.co.jp
A78.47.19.216πŸ‡©πŸ‡ͺ Hetzner78.46.0.0/15 HETZNER-RZ-NBG-BLK5
PTRwarbler.metroworks.co.jp
MXaspmx.l.google.com ⭐
A2607:f8b0:4023:c0b::1bπŸ‡ΊπŸ‡Έ Google2607:f8b0::/32
PTRdd-in-f27.1e100.net
A142.250.141.26πŸ‡ΊπŸ‡Έ Google142.250.141.0/24
PTRdd-in-f26.1e100.net
MXalt1.aspmx.l.google.com(5)
A2607:f8b0:4023:2801::1bπŸ‡ΊπŸ‡Έ Google2607:f8b0::/32
PTRlcausi-in-f27.1e100.net
A192.178.128.26πŸ‡ΊπŸ‡Έ Google192.178.128.0/24
PTRlcausi-in-f26.1e100.net
MXalt2.aspmx.l.google.com(5)
A2607:f8b0:4023:1015::1aπŸ‡ΊπŸ‡Έ Google2607:f8b0::/32
PTRyudfwta-in-f26.1e100.net
A172.253.135.27πŸ‡ΊπŸ‡Έ Google172.253.135.0/24
PTRyudfwta-in-f27.1e100.net
MXalt3.aspmx.l.google.com(10)
A2a00:1450:4009:c0f::1aπŸ‡¬πŸ‡§ Google2a00:1450:4009::/48
PTRyulhrs-in-f26.1e100.net
A192.178.223.26πŸ‡ΊπŸ‡Έ Google192.178.223.0/24
PTRyulhrs-in-f26.1e100.net
MXalt4.aspmx.l.google.com(10)
A2607:f8b0:4003:c4a::1bπŸ‡ΊπŸ‡Έ Google2607:f8b0:4003::/48
PTRyutulth-in-f27.1e100.net
A142.251.96.26πŸ‡ΊπŸ‡Έ Google142.250.0.0/15
PTRyutulth-in-f26.1e100.net
TXTv=spf1 ip4:172.233.76.4 ip6:2400:8905::f03c:94ff:fe05:4e13 include:_spf.googl...
TXTgoogle-site-verification=DUCjwXtMqM9zTdqIs8YbhgAkwvn0NaSVrxfVxXqC-WA
SOAns1.metroworks.co.jpit@metroworks.co.jp 2025-05-22 #2

com

Same first word

DNS History

13 records (10 active, 3 former)

2017201820192020202120222023202420252026NSns1.japantravel.comns1.metroworks.co.jpns2.japantravel.comns2.metroworks.co.jpns1.metropolis.co.jpns2.metropolis.co.jpMXalt1.aspmx.l.google.comalt2.aspmx.l.google.comalt3.aspmx.l.google.comalt4.aspmx.l.google.comaspmx.l.google.comA172.233.76.450.97.216.30
●NSns1.japantravel.com2026-02-22 β†’ 2026-03-25 Β· 3 obs
β—‹ 2018-01-29 05:54:28
● 2026-02-22 23:17:52
● 2026-03-25 09:55:16
β—‹NSns1.metropolis.co.jp2016-12-15 β†’ 2018-01-29 Β· 4 obs
● 2016-12-15 15:39:16
● 2018-01-29 05:54:28
β—‹ 2026-02-22 23:17:52
β—‹ 2026-03-25 09:55:16
●NSns1.metroworks.co.jp2026-02-22 β†’ 2026-03-25 Β· 3 obs
β—‹ 2018-01-29 05:54:28
● 2026-02-22 23:17:52
● 2026-03-25 09:55:16
●NSns2.japantravel.com2026-02-22 β†’ 2026-03-25 Β· 3 obs
β—‹ 2018-01-29 05:54:28
● 2026-02-22 23:17:52
● 2026-03-25 09:55:16
β—‹NSns2.metropolis.co.jp2016-12-15 β†’ 2018-01-29 Β· 4 obs
● 2016-12-15 15:39:16
● 2018-01-29 05:54:28
β—‹ 2026-02-22 23:17:52
β—‹ 2026-03-25 09:55:16
●NSns2.metroworks.co.jp2026-02-22 β†’ 2026-03-25 Β· 3 obs
β—‹ 2018-01-29 05:54:28
● 2026-02-22 23:17:52
● 2026-03-25 09:55:16
●MXalt1.aspmx.l.google.com2016-12-15 β†’ 2026-03-25 Β· 2 obs
● 2016-12-15 15:39:16
● 2026-03-25 09:55:16
●MXalt2.aspmx.l.google.com2016-12-15 β†’ 2026-03-25 Β· 2 obs
● 2016-12-15 15:39:16
● 2026-03-25 09:55:16
●MXalt3.aspmx.l.google.com2016-12-15 β†’ 2026-03-25 Β· 2 obs
● 2016-12-15 15:39:16
● 2026-03-25 09:55:16
●MXalt4.aspmx.l.google.com2016-12-15 β†’ 2026-03-25 Β· 2 obs
● 2016-12-15 15:39:16
● 2026-03-25 09:55:16
●MXaspmx.l.google.com2016-12-15 β†’ 2026-03-25 Β· 2 obs
● 2016-12-15 15:39:16
● 2026-03-25 09:55:16
●A172.233.76.42026-02-22 β†’ 2026-03-25 Β· 3 obs
β—‹ 2018-01-29 05:54:28
● 2026-02-22 23:17:52
● 2026-03-25 09:55:16
β—‹A50.97.216.302016-12-15 β†’ 2018-01-29 Β· 4 obs
● 2016-12-15 15:39:16
● 2018-01-29 05:54:28
β—‹ 2026-02-22 23:17:52
β—‹ 2026-03-25 09:55:16

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
tokyoactivity.comns1.metroworks.co.jp, ns2.metroworks.co.jp, ns1.japantravel.com, ns2.japantravel.com2 records

βœ… Authoritative Response

Server:78.47.19.216

NS records: ns1.metroworks.co.jp, ns2.metroworks.co.jp, ns1.japantravel.com, ns2.japantravel.com

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for tokyoactivity.com (unsigned zone)

⏱️ Timing

Total: 1292ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A1172.233.76.4
NS4ns2.japantravel.com, ns1.metroworks.co.jp...
MX5alt4.aspmx.l.google.com (pri: 10), aspmx.l.google.com (pri: 1)...
TXT2google-site-verification=DUCjwXtMqM9zTdq, v=spf1 ip4:172.233.76.4 ip6:2400:8905::f
SOA1ns1.metroworks.co.jp it.metroworks.co.jp

πŸ“Œ Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.japantravel.com, ns2.japantravel.com)

Analysis

IP Addresses

tokyoactivity.com resolves to one IP number: 172.233.76.4.

Other host names such as fantail2.metroworks.co.jp and svl.co.jp share IP numbers with tokyoactivity.com.

Name Servers

tokyoactivity.com is delegated to four name servers: ns1.japantravel.com, ns2.japantravel.com, ns1.metroworks.co.jp and ns2.metroworks.co.jp.

tokyoactivity.com at least partially shares name servers with other domains, for instance japaninc.com, uniquecures.com, uniteksystemgroup.com, cjnn.com and japantravel.com.

These name servers are commonly used alongside ns1.metropolis.co.jp and ns2.metropolis.co.jp.

Host names with one IP number:

Host name ns1.japantravel.com points to: 172.105.171.172.

Host name ns2.japantravel.com points to: 78.47.19.216.

Host name ns1.metroworks.co.jp points to: 172.105.171.172.

Host name ns2.metroworks.co.jp points to: 78.47.19.216.

Host names pointing to 172.105.171.172: ns1.japantravel.com and ns1.metroworks.co.jp.

Host names pointing to 78.47.19.216: ns2.japantravel.com and ns2.metroworks.co.jp.

Mail Servers

tokyoactivity.com is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com.

tokyoactivity.com shares some mail servers with other domains, at least partially, for instance rfranks.com, locutores.org, ns500693.ns500734.ns500734.ns500734.ns500699.ns500699.ns500693.ns500693.ns500588.ns500588.ns500683.ns500699.ns500632.ns500112.dtrkdll.com, ns500758.ns500758.ns500698.ns500736.ns500735.ns500698.ns500698.ns500735.ns500735.ns500736.ns500576.ns500708.ns500652.ns500619.ns500619.trackreceptor.com and ns500742.ns500671.ns500671.ns500731.ns500742.ns500731.ns500705.ns500704.ns500688.ns500649.ns500649.ns500291.ns500291.ns500131.lustychickser.com.

These mail servers are commonly used alongside aspmx2.googlemail.com and aspmx3.googlemail.com.

Host names with two IP numbers:

aspmx.l.google.com points to 2607:f8b0:4023:c0b::1b and 142.250.141.26

alt1.aspmx.l.google.com points to 2607:f8b0:4023:2801::1b and 192.178.128.26

alt2.aspmx.l.google.com points to 2607:f8b0:4023:1015::1a and 172.253.135.27

alt3.aspmx.l.google.com points to 2a00:1450:4009:c0f::1a and 192.178.223.26

alt4.aspmx.l.google.com points to 2607:f8b0:4003:c4a::1b and 142.251.96.26