CF1758146119815-tsm20250915222102

WWW.RTSAK.COM - api.tokyo

Search for IP or hostnames:

api.tokyo checked at 2025-09-17T21:55:19.800Z 443ms 72/72/72 100% R:18

api.tokyo

MXjp1-aspmx1.worksmobile.com
A110.234.239.93🇯🇵 NAVER
PTRjrcvmail.worksmobile.com
MXjp1-aspmx2.worksmobile.com
A110.234.239.93🇯🇵 NAVER
PTRjrcvmail.worksmobile.com
NSdns01.gmoserver.jp
A157.7.33.81🇯🇵 GMO-DNS
PTRdns01.gmoserver.jp
NSdns02.gmoserver.jp
A157.7.34.81🇯🇵 GMO-DNS
PTRdns02.gmoserver.jp
A210.172.183.49🇯🇵 GMO Internet, Inc.
PTRwww2.gmoserver.jp

tokyo

NSa.gmoregistry.net
NSb.gmoregistry.net
NSk.gmoregistry.net
NSl.gmoregistry.net

Starts with same word

Starts similarily

AI analysis

api.tokyo points to a single IP address: 210.172.183.49.

Other host names such as nex-eng.co.jp, www.mi-j.com, just-meet.net, 5757.me and mu-frontier.com share IP numbers with api.tokyo.

api.tokyo is delegated to two name servers: dns01.gmoserver.jp and dns02.gmoserver.jp.

api.tokyo uses the same name server setup as other domains, including hillpart.co.jp, babasangyo.net, xn--cck0a0rr15s99o.com, ushi.org and steng.co.jp.

Hostnames with a single IP

dns01.gmoserver.jp resolves to: 157.7.33.81.

dns02.gmoserver.jp resolves to: 157.7.34.81.

api.tokyo is handled by two mail servers: jp1-aspmx1.worksmobile.com and jp1-aspmx2.worksmobile.com.

api.tokyo uses the same mail server setup as other domains, for instance manifest.co.jp, total-hoken.com, yutokai.com, csware.net and koto-kanko.jp.

api.tokyo shares at least some mail servers with other domains, for example aodani.or.jp, mail.brow-cape.co.jp, ettoday.net, brow-cape.co.jp and tkwo.jp.

these mail servers are commonly used alongside aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com, alt4.aspmx.l.google.com and mx01.muumuu-mail.com.

Host names sharing a single IP: jp1-aspmx1.worksmobile.com and jp1-aspmx2.worksmobile.com point to 110.234.239.93.

Perform reverse DNS lookup as well as normal forward DNS. Check Autonomous System Numbers (ASNs) and BGP connections between Internet Service Providers.
dbq

bpVQJlz CF johedugfp 2025-09-17