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
NS | dns1.name-services.com | ||||||
A | 2604:4000:2800:2000:64:98:148:137 🇨🇦 TUCOWS-3 | ||||||
A | 64.98.148.137🇨🇦 TUCOWS-3 | ||||||
NS | dns2.name-services.com | ||||||
A | 2604:4000:0:d:216:40:47:201 🇨🇦 Tucows | ||||||
A | 216.40.47.201🇨🇦 Tucows | ||||||
NS | dns3.name-services.com | ||||||
A | 2604:4000:2800:2000:64:98:148:138 🇨🇦 TUCOWS-3 | ||||||
A | 64.98.148.138🇨🇦 TUCOWS-3 | ||||||
NS | dns4.name-services.com | ||||||
A | 2604:4000:0:d:216:40:47:202 🇨🇦 Tucows | ||||||
A | 216.40.47.202🇨🇦 Tucows | ||||||
NS | dns5.name-services.com | ||||||
A | 2604:4000:2800:2000:64:98:148:139 🇨🇦 TUCOWS-3 | ||||||
A | 64.98.148.139🇨🇦 TUCOWS-3 | ||||||
MX | mx.fetch.in.cust.a.hostedemail.com | ||||||
A | 216.40.42.4🇨🇦 Tucows | ||||||
PTR | mx.hostedemail.com |
in
NS | ns01.trs-dns.com | ||||||
NS | ns10.trs-dns.info | ||||||
NS | ns01.trs-dns.net | ||||||
NS | ns10.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.