tokyoactivity.com - robtex.com
tokyoactivity.com
com
| DNSSEC | π Signed (DS record present) | ||||||
| NS | a.gtld-servers.net β | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1774431112 | ||||||
Same first word
tokyoactivity.com |
DNS History
13 records (10 active, 3 former)
βNSns1.japantravel.com2026-02-22 β 2026-03-25 Β· 3 obs
β 2026-02-22 23:17:52
β 2026-03-25 09:55:16
βNSns1.metropolis.co.jp2016-12-15 β 2018-01-29 Β· 4 obs
β 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
β 2026-02-22 23:17:52
β 2026-03-25 09:55:16
βNSns2.japantravel.com2026-02-22 β 2026-03-25 Β· 3 obs
β 2026-02-22 23:17:52
β 2026-03-25 09:55:16
βNSns2.metropolis.co.jp2016-12-15 β 2018-01-29 Β· 4 obs
β 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
β 2026-02-22 23:17:52
β 2026-03-25 09:55:16
βMXalt1.aspmx.l.google.com2016-12-15 β 2026-03-25 Β· 2 obs
β 2026-03-25 09:55:16
βMXalt2.aspmx.l.google.com2016-12-15 β 2026-03-25 Β· 2 obs
β 2026-03-25 09:55:16
βMXalt3.aspmx.l.google.com2016-12-15 β 2026-03-25 Β· 2 obs
β 2026-03-25 09:55:16
βMXalt4.aspmx.l.google.com2016-12-15 β 2026-03-25 Β· 2 obs
β 2026-03-25 09:55:16
βMXaspmx.l.google.com2016-12-15 β 2026-03-25 Β· 2 obs
β 2026-03-25 09:55:16
βA172.233.76.42026-02-22 β 2026-03-25 Β· 3 obs
β 2026-02-22 23:17:52
β 2026-03-25 09:55:16
βA50.97.216.302016-12-15 β 2018-01-29 Β· 4 obs
β 2018-01-29 05:54:28
β 2026-02-22 23:17:52
β 2026-03-25 09:55:16
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| tokyoactivity.com | ns1.metroworks.co.jp, ns2.metroworks.co.jp, ns1.japantravel.com, ns2.japantravel.com | 2 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
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 172.233.76.4 |
| NS | 4 | ns2.japantravel.com, ns1.metroworks.co.jp... |
| MX | 5 | alt4.aspmx.l.google.com (pri: 10), aspmx.l.google.com (pri: 1)... |
| TXT | 2 | google-site-verification=DUCjwXtMqM9zTdq, v=spf1 ip4:172.233.76.4 ip6:2400:8905::f |
| SOA | 1 | ns1.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