`intelligentfit.com`

DNSSEC	⚠️ Not signed
A	216.40.47.17^{🇨🇦 TUCOWS216.40.47.0/24 -BRA-BLK1.4/NET-216-40-47-0}
		PTR	`redirect.managednsservice.com`
NS	`ns1.mdnsservice.com` ⭐
		A	2604:4000:0:d:216:40:47:18^{🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000}
			PTR	`ns1.mdnsservice.com`
		A	216.40.47.18^{🇨🇦 TUCOWS216.40.47.0/24 -BRA-BLK1.4/NET-216-40-47-0}
			PTR	`ns1.mdnsservice.com`
NS	`ns2.mdnsservice.com`
		A	2604:4000:2800:d:64:99:148:11^{🇨🇦 TUCOWS-32604:4000:2800::/37 Tucows.com Co.}
			PTR	`ns2.mdnsservice.com`
		A	64.98.148.11^{🇨🇦 TUCOWS-364.98.144.0/20 Tucows.com Co.}
			PTR	`ns2.mdnsservice.com`
NS	`ns3.mdnsservice.com`
		A	2604:4000:0:d:64:99:96:34^{🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000}
			PTR	`ns3.mdnsservice.com`
		A	64.99.96.34^{🇨🇦 TUCOWS64.99.96.0/24 -BRA-BLK2.7.2}
			PTR	`ns3.mdnsservice.com`
SOA	`ns1.mdnsservice.com`hostmaster@mdnsservice.com serial=1630832400

`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.net`nstld@verisign-grs.com serial=1774656907

Same first word

intelligentfit.com

DNS History

4 records (4 active, 0 former)

●NSns1.mdnsservice.com2015-08-14 → 2026-03-28 · 2 obs

● 2015-08-14 18:43:42
● 2026-03-28 00:25:08

●NSns2.mdnsservice.com2015-08-14 → 2026-03-28 · 2 obs

● 2015-08-14 18:43:42
● 2026-03-28 00:25:08

●NSns3.mdnsservice.com2015-08-14 → 2026-03-28 · 2 obs

● 2015-08-14 18:43:42
● 2026-03-28 00:25:08

●A216.40.47.172015-08-14 → 2026-03-28 · 2 obs

● 2015-08-14 18:43:42
● 2026-03-28 00:25:08

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
intelligentfit.com	ns1.mdnsservice.com, ns2.mdnsservice.com, ns3.mdnsservice.com	6 records

✅ Authoritative Response

Server:216.40.47.18

NS records: ns1.mdnsservice.com, ns2.mdnsservice.com, ns3.mdnsservice.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for intelligentfit.com (unsigned zone)

⏱️ Timing

Total: 216ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`216.40.47.17`
NS	3	`ns1.mdnsservice.com, ns3.mdnsservice.com...`
SOA	1	`ns1.mdnsservice.com hostmaster.mdnsservi`

📌 Glue Records Collected

Total: 6

Out-of-bailiwick: 6 (ns1.mdnsservice.com, ns1.mdnsservice.com, ns2.mdnsservice.com...)

Analysis

IP Addresses

intelligentfit.com resolves to one IP number: 216.40.47.17.

other host names including beardintl.com, jazztransaxion.org, bbhcafe.com, seawolfgus.com and parentsparents.com share IP numbers with intelligentfit.com.

Name Servers

intelligentfit.com is delegated to three name servers ns1.mdnsservice.com, ns2.mdnsservice.com and ns3.mdnsservice.com.

intelligentfit.com at least partially shares name servers with other domains, for instance upfitter.info, silvestri.org, kulik.com, minner.com and perego.org.

these name servers are often used together with ns1.mailbank.com, ns2.mailbank.com, ns1.criticalserver.net and ns2.criticalserver.net.

Host names with two IP numbers:

ns1.mdnsservice.com points to: 2604:4000:0:d:216:40:47:18 and 216.40.47.18.

ns2.mdnsservice.com points to: 2604:4000:2800:d:64:99:148:11 and 64.98.148.11.

ns3.mdnsservice.com points to: 2604:4000:0:d:64:99:96:34 and 64.99.96.34.

intelligentfit.com - robtex.com