ftcrowd.com - dns.ninja

`ftcrowd.com`

DNSSEC	⚠️ Not signed
A	95.179.238.226^{🇬🇧 AS-VULTR95.179.224.0/20 Vultr Assigned Prefix}
		PTR	`95.179.238.226.vultrusercontent.com`
NS	`ns1.vultr.com` ⭐
		A	2001:19f0:ccc::1^{🇺🇸 AS-VULTR2001:19f0:ccc::/48 DNS1}
		A	2001:19f0:ccd::1^{🇺🇸 AS-VULTR2001:19f0:ccd::/48 Vultr Assigned Prefix}
			PTR	`ns1.vultr.com`
		A	173.199.96.96^{🇺🇸 AS-VULTR173.199.96.0/24 Vultr Assigned Prefix}
			PTR	`ns1.vultrusercontent.com`
NS	`ns2.vultr.com`
		A	2001:19f0:ccc::2^{🇺🇸 AS-VULTR2001:19f0:ccc::/48 DNS1}
		A	2001:19f0:ccd::2^{🇺🇸 AS-VULTR2001:19f0:ccd::/48 Vultr Assigned Prefix}
			PTR	`ns2.vultr.com`
		A	173.199.96.97^{🇺🇸 AS-VULTR173.199.96.0/24 Vultr Assigned Prefix}
			PTR	`ns2.vultrusercontent.com`
MX	`ftcrowd-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:ca0b::^{🇬🇧 Microsoft2a01:111:f000::/36}
			PTR	`mail-lo2p265cu02300.inbound.protection.outlook.com`
		A	2a01:111:f403:ca0b::1^{🇬🇧 Microsoft2a01:111:f000::/36}
			PTR	`mail-lo3p265cu00301.inbound.protection.outlook.com`
		A	2a01:111:f403:ca1a::^{🇬🇧 Microsoft2a01:111:f000::/36}
			PTR	`mail-cwxp265cu00500.inbound.protection.outlook.com`
		A	2a01:111:f403:ca1a::1^{🇬🇧 Microsoft2a01:111:f000::/36}
			PTR	`mail-cwxp265cu00601.inbound.protection.outlook.com`
		A	52.101.89.1^{🇬🇧 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-lo0p265cu00201.inbound.protection.outlook.com`
		A	52.101.89.2^{🇬🇧 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-lo3p265cu00302.inbound.protection.outlook.com`
		A	52.101.99.0^{🇬🇧 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-cwxp265cu00600.inbound.protection.outlook.com`
		A	52.101.99.2^{🇬🇧 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-cwxp265cu00502.inbound.protection.outlook.com`
MX	`aspmx.l.google.com`⁽¹⁾
		A	2607:f8b0:4004:c1d::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`ww-in-f26.1e100.net`
		A	142.251.163.27^{🇺🇸 Google142.251.163.0/24}
			PTR	`wv-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.26^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1b^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f27.1e100.net`
		A	192.178.223.26^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f26.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f26.1e100.net`
		A	172.253.157.26^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f26.1e100.net`
TXT	`MS=708CAB61B8258BFC00B25860182D9E5C1C21AEA4`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
TXT	`google-site-verification=adeFBHFf-fx0Z52xnb1yiQSGrXP8qQRJjklefFD9G2w`
SOA	`ns1.vultr.com`dnsadm@choopa.com serial=0

`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=1783260281

Same first word

ftcrowd.com

DNS History

12 records (9 active, 3 former)

●NSns1.vultr.com2026-03-21 → 2026-07-05 · 3 obs

○ 2017-10-05 04:31:10
● 2026-03-21 23:42:02
● 2026-07-05 14:04:54

○NSns10.wixdns.net2016-12-20 → 2017-10-05 · 4 obs

● 2016-12-20 01:18:10
● 2017-10-05 04:31:10
○ 2026-03-21 23:42:02
○ 2026-07-05 14:04:54

○NSns11.wixdns.net2016-12-20 → 2017-10-05 · 4 obs

● 2016-12-20 01:18:10
● 2017-10-05 04:31:10
○ 2026-03-21 23:42:02
○ 2026-07-05 14:04:54

●NSns2.vultr.com2026-03-21 → 2026-07-05 · 3 obs

○ 2017-10-05 04:31:10
● 2026-03-21 23:42:02
● 2026-07-05 14:04:54

●MXalt1.aspmx.l.google.com2026-03-21 → 2026-07-05 · 3 obs

○ 2016-12-20 01:18:10
● 2026-03-21 23:42:02
● 2026-07-05 14:04:54

●MXalt2.aspmx.l.google.com2026-03-21 → 2026-07-05 · 3 obs

○ 2016-12-20 01:18:10
● 2026-03-21 23:42:02
● 2026-07-05 14:04:54

●MXalt3.aspmx.l.google.com2026-03-21 → 2026-07-05 · 3 obs

○ 2016-12-20 01:18:10
● 2026-03-21 23:42:02
● 2026-07-05 14:04:54

●MXalt4.aspmx.l.google.com2026-03-21 → 2026-07-05 · 3 obs

○ 2016-12-20 01:18:10
● 2026-03-21 23:42:02
● 2026-07-05 14:04:54

●MXaspmx.l.google.com2026-03-21 → 2026-07-05 · 3 obs

○ 2016-12-20 01:18:10
● 2026-03-21 23:42:02
● 2026-07-05 14:04:54

●MXftcrowd-com.mail.protection.outlook.com2016-12-20 → 2026-07-05 · 2 obs

● 2016-12-20 01:18:10
● 2026-07-05 14:04:54

○A23.236.62.1472016-12-20 → 2017-10-05 · 4 obs

● 2016-12-20 01:18:10
● 2017-10-05 04:31:10
○ 2026-03-21 23:42:02
○ 2026-07-05 14:04:54

●A95.179.238.2262026-03-21 → 2026-07-05 · 3 obs

○ 2017-10-05 04:31:10
● 2026-03-21 23:42:02
● 2026-07-05 14:04:54

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
ftcrowd.com	ns1.vultr.com, ns2.vultr.com	4 records

✅ Authoritative Response

Server:173.199.96.96

NS records: ns1.vultr.com, ns2.vultr.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for ftcrowd.com (unsigned zone)

⏱️ Timing

Total: 166ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`95.179.238.226`
NS	2	`ns1.vultr.com, ns2.vultr.com`
MX	6	`alt3.aspmx.l.google.com (pri: 10), alt1.aspmx.l.google.com (pri: 5)...`
TXT	3	`google-site-verification=adeFBHFf-fx0Z52, v=spf1 include:spf.protection.outlook.co...`
SOA	1	`ns1.vultr.com dnsadm.choopa.com`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns1.vultr.com, ns1.vultr.com, ns2.vultr.com...)

Analysis

IP Addresses

ftcrowd.com resolves to just one IP address, 95.179.238.226.

Host names like vinitsolutions.com are further examples that share IP numbers with ftcrowd.com.

Name Servers

Two name servers handle the delegation for ftcrowd.com: ns1.vultr.com and ns2.vultr.com.

ftcrowd.com shares its NS records with other domains, for example alojanetwork.com, haversine.net, powerdigital.sg and two others.

There is at least partial name server overlap between ftcrowd.com and other domains — libertyunbound.com, chasehafer.com, myhomeinkw.com and two more among them.

The name servers ns1.wpdns.host, ns2.wpdns.host and ns3.wpdns.host are often found in combination with these name servers.

ns1.vultr.com points to 173.199.96.96, 2001:19f0:ccc::1 and 2001:19f0:ccd::1. ns2.vultr.com points to 173.199.96.97, 2001:19f0:ccc::2 and 2001:19f0:ccd::2. Both hosts resolve to three IP numbers.

Mail Servers

ftcrowd.com accepts email via 6 mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and 3 other.

There is at least a partial MX overlap between ftcrowd.com and other domains, including ns500758.ns500698.ns500758.ns500758.ns500736.ns500698.ns500735.ns500708.ns500576.ns500708.ns500576.ns500619.ns500652.ns500619.trackreceptor.com, ns500693.ns500734.ns500693.ns500699.ns500699.ns500693.ns500734.ns500588.ns500693.ns500588.ns500612.ns500588.ns500588.ns500612.ns500588.ns500588.dtrkdll.com, ns500671.ns500731.ns500671.ns500754.ns500754.ns500671.ns500705.ns500688.ns500649.ns500671.ns500671.ns500666.ns500153.tenderladiesbz.com and two others.

These mail servers tend to appear in combination with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.

DNS names with 8 IP addresses:

ftcrowd-com.mail.protection.outlook.com resolves to 52.101.89.1, 52.101.89.2 and 52.101.99.0 among others, with 5 other IP addresses in total.

Host names that have two IP addresses:

aspmx.l.google.com resolves to two addresses: 142.251.163.27 and 2607:f8b0:4004:c1d::1a.

alt1.aspmx.l.google.com resolves to two addresses: 108.177.123.26 and 2800:3f0:4003:c0f::1a.

alt2.aspmx.l.google.com resolves to two addresses: 172.253.116.27 and 2a00:1450:400b:c02::1b.

alt3.aspmx.l.google.com resolves to two addresses: 192.178.223.26 and 2a00:1450:4009:c0f::1b.

alt4.aspmx.l.google.com resolves to two addresses: 172.253.157.26 and 2a00:1450:400c:c23::1a.