ROBTEX.COM - fetch.in

Search for IP or hostnames:

fetch.in checked at 2025-12-03T08:30:31.588Z 271ms 84/84/84 100% R:11 allDone:true timedOut:false

fetch.in

NSdns1.name-services.com
A2604:4000:2800:2000:64:98:148:137🇨🇦 TUCOWS-3
A64.98.148.137🇨🇦 TUCOWS-3
NSdns2.name-services.com
A2604:4000:0:d:216:40:47:201🇨🇦 TUCOWS
A216.40.47.201🇨🇦 TUCOWS
NSdns3.name-services.com
A2604:4000:2800:2000:64:98:148:138🇨🇦 TUCOWS-3
A64.98.148.138🇨🇦 TUCOWS-3
NSdns4.name-services.com
A2604:4000:0:d:216:40:47:202🇨🇦 TUCOWS
A216.40.47.202🇨🇦 TUCOWS
NSdns5.name-services.com
A2604:4000:2800:2000:64:98:148:139🇨🇦 TUCOWS-3
A64.98.148.139🇨🇦 TUCOWS-3
MXmx.fetch.in.cust.a.hostedemail.com
A216.40.42.4🇨🇦 TUCOWS
PTRmx.hostedemail.com

in

Starts with same word

Starts similarily

AI analysis

fetch.in is delegated to five name servers: dns1.name-services.com, dns2.name-services.com, dns3.name-services.com, dns4.name-services.com and dns5.name-services.com.

fetch.in at least partially shares name servers with other domains, including mnbweb.com, naidu.co, smartcart.us, marisavictor.com and genetitle.com.

Host names with two IP numbers:

dns1.name-services.com points to: 2604:4000:2800:2000:64:98:148:137 and 64.98.148.137.

dns2.name-services.com points to: 2604:4000:0:d:216:40:47:201 and 216.40.47.201.

dns3.name-services.com points to: 2604:4000:2800:2000:64:98:148:138 and 64.98.148.138.

dns4.name-services.com points to: 2604:4000:0:d:216:40:47:202 and 216.40.47.202.

dns5.name-services.com points to: 2604:4000:2800:2000:64:98:148:139 and 64.98.148.139.

A single mail server handles fetch.in, mx.fetch.in.cust.a.hostedemail.com.

Host name mx.fetch.in.cust.a.hostedemail.com resolves to a single IP: 216.40.42.4.