imu.tokyo checked at 2024-12-27T19:45:34.777Z 528ms 107/107/107 100% R:16
DNSTREE.COM - imu.tokyo
Search for IP or hostnames
imu.tokyo
NS | ns-rs1.gmoserver.jp | ||||||
A | 157.7.32.87🇯🇵 GMO-DNS | ||||||
PTR | ns-rs1.gmoserver.jp | ||||||
NS | ns-rs2.gmoserver.jp | ||||||
A | 157.7.33.87🇯🇵 GMO-DNS | ||||||
PTR | ns-rs2.gmoserver.jp | ||||||
MX | aspmx.l.google.com | ||||||
A | 2a00:1450:400c:c00::1a 🇧🇪 Google | ||||||
PTR | ws-in-f26.1e100.net | ||||||
PTR | ws-in-x1a.1e100.net | ||||||
A | 74.125.71.27🇺🇸 Google | ||||||
PTR | wn-in-f27.1e100.net | ||||||
MX | alt1.aspmx.l.google.com | ||||||
A | 2a00:1450:4013:c16::1a 🇳🇱 Google | ||||||
PTR | ea-in-f26.1e100.net | ||||||
A | 142.250.153.27🇺🇸 Google | ||||||
PTR | ea-in-f27.1e100.net | ||||||
MX | alt2.aspmx.l.google.com | ||||||
A | 2a00:1450:4025:c03::1a 🇵🇱 Google | ||||||
PTR | rc-in-f26.1e100.net | ||||||
A | 142.251.9.27🇺🇸 Google | ||||||
PTR | rc-in-f27.1e100.net | ||||||
MX | alt3.aspmx.l.google.com | ||||||
A | 2a00:1450:4010:c1c::1a 🇫🇮 Google | ||||||
PTR | la-in-f26.1e100.net | ||||||
A | 142.250.150.27🇺🇸 Google | ||||||
PTR | la-in-f27.1e100.net | ||||||
MX | alt4.aspmx.l.google.com | ||||||
A | 2404:6800:4003:c00::1a 🇸🇬 Google | ||||||
PTR | sa-in-f26.1e100.net | ||||||
PTR | sa-in-x1a.1e100.net | ||||||
A | 74.125.200.27🇺🇸 Google | ||||||
PTR | sa-in-f27.1e100.net | ||||||
A | 160.251.148.151🇯🇵 GMO Internet West | ||||||
PTR | www1073.onamae.ne.jp |
tokyo
NS | a.gmoregistry.net | ||||||
NS | b.gmoregistry.net | ||||||
NS | k.gmoregistry.net | ||||||
NS | l.gmoregistry.net |
AI analysis
160.251.148.151 is the IP number that imu.tokyo points to.
IP numbers are shared between imu.tokyo and other host names such as morizumi.com, dus.jp, wa-da.com, gcomega.com, and moco-me.com.
Two name servers, ns-rs1.gmoserver.jp and ns-rs2.gmoserver.jp, have been delegated to imu.tokyo.
The name server setup of imu.tokyo is identical to that of other domains such as chobirin.com, iso-cafe.com, resgw.com, asmile7.com, and advt.jp.
ns-rs1.gmoserver.jp and ns-rs2.gmoserver.jp both point to different IP numbers. 157.7.32.87 and 157.7.33.87 respectively.
Five mail servers, namely 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, manage imu.tokyo.
Like other domains such as ns500698.ns500759.ns500698.ns500736.ns500698.ns500736.ns500735.ns500735.ns500736.ns500576.ns500576.ns500619.ns500576.ns500576.ns500652.trackreceptor.com, ns500742.ns500671.ns500731.ns500671.ns500704.ns500671.ns500666.ns500291.ns500131.lustychickser.com, ns500742.ns500754.ns500671.ns500731.ns500731.ns500705.ns500705.ns500671.ns500688.ns500688.ns500649.ns500649.ns500666.ns500142.lustyslutz.com, ns500758.ns500758.ns500759.ns500735.ns500698.ns500698.ns500698.ns500698.ns500708.ns500576.ns500708.ns500698.ns500619.ns500619.ns500619.trackreceptor.com, and ns500699.ns500734.ns500693.ns500699.ns500699.ns500588.ns500588.ns500699.ns500699.ns500588.ns500588.ns500588.ns500588.ns500612.ns500588.ns500578.ns500110.dtrkdll.com, imu.tokyo also has the same mail server setup.
Some mail servers are at least partially shared between imu.tokyo and other domains such as pneus-mobile.ca, kentlaue.com, and sat.qc.ca.
aspmx.l.google.com, 2a00:1450:400c:c00::1a, and 74.125.71.27 are associated.
alt1.aspmx.l.google.com, 2a00:1450:4013:c16::1a, and 142.250.153.27 are associated.
alt2.aspmx.l.google.com, 2a00:1450:4025:c03::1a, and 142.251.9.27 are associated.
alt3.aspmx.l.google.com, 2a00:1450:4010:c1c::1a, and 142.250.150.27 are associated.
alt4.aspmx.l.google.com, 2404:6800:4003:c00::1a, and 74.125.200.27 are associated.