fetch.in - dns.ninja
fetch.in
in
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns.trs-dns.com ⭐ | ||||||
| NS | ns1.registry.in | ||||||
| NS | ns2.registry.in | ||||||
| NS | ns3.registry.in | ||||||
| NS | ns4.registry.in | ||||||
| SOA | ns.trs-dns.comtrs-ops@tucows.com serial=1786152063 | ||||||
Subdomains
mx.fetch.in |
Same first word
Similar names
DNS History
13 records (3 active, 10 former)
●NSamir.ns.cloudflare.com2026-03-26 → 2026-08-08 · 3 obs
● 2026-03-26 07:50:38
● 2026-08-08 01:34:46
○NSdns1.name-services.com2015-05-18 → 2017-06-04 · 4 obs
● 2017-06-04 14:20:54
○ 2026-03-26 07:50:38
○ 2026-08-08 01:34:46
○NSdns2.name-services.com2015-05-18 → 2017-06-04 · 4 obs
● 2017-06-04 14:20:54
○ 2026-03-26 07:50:38
○ 2026-08-08 01:34:46
○NSdns3.name-services.com2015-05-18 → 2017-06-04 · 4 obs
● 2017-06-04 14:20:54
○ 2026-03-26 07:50:38
○ 2026-08-08 01:34:46
○NSdns4.name-services.com2015-05-18 → 2017-06-04 · 4 obs
● 2017-06-04 14:20:54
○ 2026-03-26 07:50:38
○ 2026-08-08 01:34:46
○NSdns5.name-services.com2015-05-18 → 2017-06-04 · 4 obs
● 2017-06-04 14:20:54
○ 2026-03-26 07:50:38
○ 2026-08-08 01:34:46
●NSsierra.ns.cloudflare.com2026-03-26 → 2026-08-08 · 3 obs
● 2026-03-26 07:50:38
● 2026-08-08 01:34:46
○MXmail.fetch.in2015-05-18 → 2017-06-04 · 4 obs
● 2017-06-04 14:20:54
○ 2026-03-26 07:50:38
○ 2026-08-08 01:34:46
●MXmx.fetch.in2026-04-06 → 2026-08-08 · 3 obs
● 2026-04-06 04:33:56
● 2026-08-08 01:34:46
○MXmx.fetch.in.cust.a.hostedemail.com2026-03-26 → 2026-08-08 · 2 obs
○ 2026-08-08 01:34:46
○A98.124.198.12015-05-18 → 2015-10-06 · 4 obs
● 2015-10-06 08:02:40
○ 2016-01-18 16:31:14
○ 2026-08-08 01:34:46
○A98.124.199.12015-05-18 → 2015-10-06 · 4 obs
● 2015-10-06 08:02:40
○ 2017-06-04 14:20:54
○ 2026-08-08 01:34:46
○A98.124.199.662016-01-18 → 2017-06-04 · 5 obs
● 2016-01-18 16:31:14
● 2017-06-04 14:20:54
○ 2026-03-26 07:50:38
○ 2026-08-08 01:34:46
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| in | ns1.registry.in, ns2.registry.in, ns3.registry.in, ns4.registry.in | - |
| fetch.in | amir.ns.cloudflare.com, sierra.ns.cloudflare.com | - |
✅ Authoritative Response
Server:108.162.193.62
NS records: amir.ns.cloudflare.com, sierra.ns.cloudflare.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for fetch.in (unsigned zone)
⏱️ Timing
Total: 449ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | amir.ns.cloudflare.com, sierra.ns.cloudflare.com |
| MX | 1 | mx.fetch.in (pri: 10) |
| TXT | 1 | v=spf1 ip4:82.180.147.112 include:amazon |
| SOA | 1 | amir.ns.cloudflare.com dns.cloudflare.co |
Analysis
Hierarchy
mx.fetch.in is delegated beneath fetch.in.
Name Servers
fetch.in has two authoritative name servers — amir.ns.cloudflare.com and sierra.ns.cloudflare.com.
fetch.in uses the same name servers as several other domains — among them osbckansas.gov, charismagaming.com, omnigame.id and two more.
There is at least partial name server overlap between fetch.in and other domains — stay-update.com, magice.cn, liveruleta.net and two more among them.
These name servers are routinely deployed together with the name servers aiden.ns.cloudflare.com.
Hostnames that resolve to 6 IP addresses:
amir.ns.cloudflare.com points to 108.162.193.62, 172.64.33.62, 173.245.59.62 and 3 other IP addresses.
sierra.ns.cloudflare.com points to 108.162.194.245, 162.159.38.245, 172.64.34.245 and 3 other IP addresses.
Mail Servers
Mail for fetch.in is handled by a single mail server, mx.fetch.in.
mx.fetch.in points to one IP number — 82.180.147.112.