MXLIST.NET - remoteaccess.tokyo
Search for IP or hostnames:
remoteaccess.tokyo checked at 2025-11-28T14:23:46.085Z 399ms 63/63/63 100% R:18 allDone:true timedOut:false remoteaccess.tokyo
| NS | dns01.muumuu-domain.com | ||||||
| A | 202.239.23.39🇯🇵 IDC | ||||||
| NS | dns02.muumuu-domain.com | ||||||
| A | 160.251.249.62🇯🇵 GMOOSK-NET | ||||||
| MX | mx01.lolipop.jp | ||||||
| A | 157.7.107.233🇯🇵 GMO-INTERNET | ||||||
| A | 157.7.107.26🇯🇵 GMO-INTERNET | ||||||
| PTR | 157-7-107-26.virt.lolipop.jp | ||||||
tokyo
Starts with same word
Starts similarily
AI analysis
remoteaccess.tokyo maps to IP address 157.7.107.26.
Other host names, for instance your-wants.com, kmp.to, zlen.info, bar-progresso.com and gaia-net.com share IP numbers with remoteaccess.tokyo.
Two name servers dns01.muumuu-domain.com and dns02.muumuu-domain.com are delegated to remoteaccess.tokyo.
remoteaccess.tokyo uses the same name server configuration as other domains, such as cafe-aroma.jp, domaibest.com, threechan.jp, h-dezain.com and caru.jp.
Host names with a single IP address:
dns01.muumuu-domain.com points to 202.239.23.39
dns02.muumuu-domain.com points to 160.251.249.62
remoteaccess.tokyo is handled by a single mail server, mx01.lolipop.jp.
remoteaccess.tokyo shares the same mail server setup as other domains, including e-nail.co.jp, hiirokokoro.com, pcube.cc, peco-rino.com and salacarina.com.
remoteaccess.tokyo shares some mail servers with other domains, at least partially, for instance ws-tokyo.com.
mx01.lolipop.jp points to one IP number: 157.7.107.233.