rescuefetch.com - robtex.com
rescuefetch.com
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1774487777 | ||||||
Same first word
rescuefetch.com |
DNS History
11 records (7 active, 4 former)
○NSdns17.ovh.net2015-07-09 → 2015-07-09 · 3 obs
○ 2015-11-29 16:49:20
○ 2026-03-26 01:30:24
●NSns1.vultr.com2026-02-15 → 2026-03-26 · 3 obs
● 2026-02-15 10:45:44
● 2026-03-26 01:30:24
●NSns1.wpdns.host2026-02-15 → 2026-03-26 · 3 obs
● 2026-02-15 10:45:44
● 2026-03-26 01:30:24
○NSns17.ovh.net2015-07-09 → 2015-07-09 · 3 obs
○ 2015-11-29 16:49:20
○ 2026-03-26 01:30:24
●NSns2.wpdns.host2026-02-15 → 2026-03-26 · 3 obs
● 2026-02-15 10:45:44
● 2026-03-26 01:30:24
●NSns3.wpdns.host2026-02-15 → 2026-03-26 · 3 obs
● 2026-02-15 10:45:44
● 2026-03-26 01:30:24
●MXmx.zoho.com2026-02-15 → 2026-03-26 · 3 obs
● 2026-02-15 10:45:44
● 2026-03-26 01:30:24
●MXmx2.zoho.com2026-02-15 → 2026-03-26 · 3 obs
● 2026-02-15 10:45:44
● 2026-03-26 01:30:24
●MXmx3.zoho.com2026-02-15 → 2026-03-26 · 3 obs
● 2026-02-15 10:45:44
● 2026-03-26 01:30:24
○MXredirect.ovh.net2015-07-09 → 2015-07-09 · 3 obs
○ 2015-11-29 16:49:20
○ 2026-03-26 01:30:24
○A213.186.33.52015-07-09 → 2015-07-09 · 3 obs
○ 2015-11-29 16:49:20
○ 2026-03-26 01:30:24
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | c.gtld-servers.net, h.gtld-servers.net, e.gtld-servers.net, l.gtld-servers.net... | - |
| rescuefetch.com | ns1.wpdns.host, ns2.wpdns.host, ns3.wpdns.host | - |
✅ Authoritative Response
Server:173.199.96.96
NS records: ns1.wpdns.host, ns2.wpdns.host, ns3.wpdns.host
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for rescuefetch.com (unsigned zone)
⏱️ Timing
Total: 560ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 3 | ns3.wpdns.host, ns2.wpdns.host... |
| MX | 3 | mx3.zoho.com (pri: 50), mx.zoho.com (pri: 10)... |
| TXT | 2 | v=spf1 include:zohomail.com ~all, zoho-verification=zb55278513.zmverify.zo |
| SOA | 1 | ns1.vultr.com dnsadm.choopa.com |
Analysis
Name Servers
rescuefetch.com delegates to four name servers: ns1.vultr.com, ns1.wpdns.host, ns2.wpdns.host and ns3.wpdns.host.
rescuefetch.com at least partially shares name servers with other domains, including loshogares.mx, johnsonsmarketing.co.uk, legacytheme.net, kwangdocable.co.kr and threadtraders.com.
These name servers are commonly used with ns2.vultr.com.
Three IP numbers:
Host ns1.vultr.com points to 2001:19f0:ccc::1, 2001:19f0:ccd::1 and 173.199.96.96.
Two IP numbers:
Host ns1.wpdns.host points to 2001:19f0:ccd::1 and 173.199.96.96.
Host ns2.wpdns.host points to 2001:19f0:ccd::2 and 173.199.96.97.
Host ns3.wpdns.host points to 2001:19f0:ccd::1 and 173.199.96.96.
Hosts pointing to 2001:19f0:ccd::1: ns1.vultr.com, ns1.wpdns.host and ns3.wpdns.host.
Hosts pointing to 173.199.96.96: ns1.vultr.com, ns1.wpdns.host and ns3.wpdns.host.
Mail Servers
Three mail servers handle rescuefetch.com: mx2.zoho.com, mx3.zoho.com and mx.zoho.com.
rescuefetch.com shares at least some mail servers with other domains, for example mdcinvite.com, hillchoicejewel.com, padovanibus.com.br, gamehunt.asia and hoteltowersquare.com.
Host names with two IPs:
mx.zoho.com points to 136.143.183.44 and 136.143.191.44.
Host names with one IP:
mx2.zoho.com points to 136.143.183.44.
mx3.zoho.com points to 136.143.191.44.
Hosts pointing to 136.143.183.44: mx.zoho.com and mx2.zoho.com.
Hosts pointing to 136.143.191.44: mx.zoho.com and mx3.zoho.com.