CF1757983041953-tsm20250915222102

IPLIST.NET - fetch.in

Search for IP or hostnames:

fetch.in checked at 2025-09-16T00:37:21.892Z 217ms 84/84/84 100% R:13

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

NSns01.trs-dns.com
NSns10.trs-dns.info
NSns01.trs-dns.net
NSns10.trs-dns.org

Starts with same word

Starts similarily

AI analysis

Five name servers, dns1.name-services.com, dns2.name-services.com, dns3.name-services.com, dns4.name-services.com, and dns5.name-services.com, are delegated to fetch.in.

The domain fetch.in partially shares name servers with other domains such as mnbweb.com, naidu.co, smartcart.us, genetitle.com, and snkone.com.

dns1.name-services.com, dns2.name-services.com, dns3.name-services.com, dns4.name-services.com, and dns5.name-services.com each point to two IP numbers respectively: 2604:4000:2800:2000:64:98:148:137 and 64.98.148.137, 2604:4000:0:d:216:40:47:201 and 216.40.47.201, 2604:4000:2800:2000:64:98:148:138 and 64.98.148.138, 2604:4000:0:d:216:40:47:202 and 216.40.47.202, 2604:4000:2800:2000:64:98:148:139 and 64.98.148.139.

The mail server, mx.fetch.in.cust.a.hostedemail.com, manages fetch.in.

The DNS record mx.fetch.in.cust.a.hostedemail.com is configured to resolve to the IP address 216.40.42.4.

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

TIkOyNK CF johedugfp 2025-09-16