`ftftech.net`

DNSSEC	⚠️ Not signed
A	64.71.164.66^{🇺🇸 HURRICANE64.71.128.0/18 Hurricane Electric 55 South Market St San Jose, CA}
NS	`ns1.markmonitor.com` ⭐
		A	2620:10a:80a8::1^{🇨🇦 CIRA-22620:10a:80a8::/48 markmonitor v6 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
		A	149.112.160.1^{🇨🇦 CIRA-2149.112.160.0/24 markmonitor v4 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
NS	`ns2.markmonitor.com`
		A	2001:67c:10b8::1^{🇨🇭 RCODEZERO-ANYCAST-SEC22001:67c:10b8::/48 IPCOM-anycast-net}
			PTR	`ns2.markmonitor.com`
		A	176.97.158.1^{🇦🇹 RCODEZERO-ANYCAST-SEC2176.97.158.0/24 NICat-anycast-net}
			PTR	`ns2.markmonitor.com`
NS	`ns3.markmonitor.com`
		A	2620:10a:80a9::1^{🇨🇦 CIRA-32620:10a:80a9::/48 markmonitor v6 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
		A	149.112.161.1^{🇨🇦 CIRA-3149.112.161.0/24 markmonitor v4 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
NS	`ns4.markmonitor.com`
		A	2001:67c:1bc::1^{🇦🇹 RCODEZERO-ANYCAST-SEC1-TLD2001:67c:1bc::/48 IPCom-NET Anycast}
			PTR	`ns1.markmonitor.com`
		A	192.174.68.1^{🇦🇹 RCODEZERO-ANYCAST-SEC1-TLD192.174.68.0/24 NICat-anycast-net}
			PTR	`ns1.markmonitor.com`
NS	`ns5.markmonitor.com`
		A	2620:10a:80a8::2^{🇨🇦 CIRA-22620:10a:80a8::/48 markmonitor v6 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
		A	149.112.160.2^{🇨🇦 CIRA-2149.112.160.0/24 markmonitor v4 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
NS	`ns6.markmonitor.com`
		A	2001:67c:10b8::3^{🇨🇭 RCODEZERO-ANYCAST-SEC22001:67c:10b8::/48 IPCOM-anycast-net}
			PTR	`ns6.markmonitor.com`
		A	176.97.158.3^{🇦🇹 RCODEZERO-ANYCAST-SEC2176.97.158.0/24 NICat-anycast-net}
			PTR	`ns6.markmonitor.com`
NS	`ns7.markmonitor.com`
		A	2620:10a:80a9::2^{🇨🇦 CIRA-32620:10a:80a9::/48 markmonitor v6 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
		A	149.112.161.2^{🇨🇦 CIRA-3149.112.161.0/24 markmonitor v4 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c23::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadrs-in-f27.1e100.net`
		A	142.251.167.27^{🇺🇸 Google142.251.167.0/24}
			PTR	`ww-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f27.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.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.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.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
TXT	`MS=ms45697460`
TXT	`v=spf1 include:spf.ftftech.net -all`
SOA	`ns1.markmonitor.com`hostmaster@markmonitor.com 2025-06-02 #2

`net`

	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=1784373247

Same first word

ftftech.org

ftftech.net

ftftech.com

Similar names

tfftech.com

DNS History

17 records (13 active, 4 former)

●NSns1.markmonitor.com2026-03-11 → 2026-07-18 · 3 obs

○ 2017-08-17 03:17:56
● 2026-03-11 09:01:14
● 2026-07-18 11:40:46

○NSns1.p28.dynect.net2015-08-11 → 2017-08-17 · 4 obs

● 2015-08-11 15:24:58
● 2017-08-17 03:17:56
○ 2026-03-11 09:01:14
○ 2026-07-18 11:40:46

●NSns2.markmonitor.com2026-03-11 → 2026-07-18 · 3 obs

○ 2017-08-17 03:17:56
● 2026-03-11 09:01:14
● 2026-07-18 11:40:46

○NSns2.p28.dynect.net2015-08-11 → 2017-08-17 · 4 obs

● 2015-08-11 15:24:58
● 2017-08-17 03:17:56
○ 2026-03-11 09:01:14
○ 2026-07-18 11:40:46

●NSns3.markmonitor.com2026-03-11 → 2026-07-18 · 3 obs

○ 2017-08-17 03:17:56
● 2026-03-11 09:01:14
● 2026-07-18 11:40:46

○NSns3.p28.dynect.net2015-08-11 → 2017-08-17 · 4 obs

● 2015-08-11 15:24:58
● 2017-08-17 03:17:56
○ 2026-03-11 09:01:14
○ 2026-07-18 11:40:46

●NSns4.markmonitor.com2026-03-11 → 2026-07-18 · 3 obs

○ 2017-08-17 03:17:56
● 2026-03-11 09:01:14
● 2026-07-18 11:40:46

○NSns4.p28.dynect.net2015-08-11 → 2017-08-17 · 4 obs

● 2015-08-11 15:24:58
● 2017-08-17 03:17:56
○ 2026-03-11 09:01:14
○ 2026-07-18 11:40:46

●NSns5.markmonitor.com2026-03-11 → 2026-07-18 · 3 obs

○ 2017-08-17 03:17:56
● 2026-03-11 09:01:14
● 2026-07-18 11:40:46

●NSns6.markmonitor.com2026-03-11 → 2026-07-18 · 3 obs

○ 2017-08-17 03:17:56
● 2026-03-11 09:01:14
● 2026-07-18 11:40:46

●NSns7.markmonitor.com2026-03-11 → 2026-07-18 · 3 obs

○ 2017-08-17 03:17:56
● 2026-03-11 09:01:14
● 2026-07-18 11:40:46

●MXalt1.aspmx.l.google.com2015-08-11 → 2026-07-18 · 2 obs

● 2015-08-11 15:24:58
● 2026-07-18 11:40:46

●MXalt2.aspmx.l.google.com2015-08-11 → 2026-07-18 · 2 obs

● 2015-08-11 15:24:58
● 2026-07-18 11:40:46

●MXalt3.aspmx.l.google.com2015-08-11 → 2026-07-18 · 2 obs

● 2015-08-11 15:24:58
● 2026-07-18 11:40:46

●MXalt4.aspmx.l.google.com2015-08-11 → 2026-07-18 · 2 obs

● 2015-08-11 15:24:58
● 2026-07-18 11:40:46

●MXaspmx.l.google.com2015-08-11 → 2026-07-18 · 2 obs

● 2015-08-11 15:24:58
● 2026-07-18 11:40:46

●A64.71.164.662015-08-11 → 2026-07-18 · 2 obs

● 2015-08-11 15:24:58
● 2026-07-18 11:40:46

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	m.gtld-servers.net, k.gtld-servers.net, b.gtld-servers.net, f.gtld-servers.net...	-
ftftech.net	ns1.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com, ns5.markmonitor.com...	-

✅ Authoritative Response

Server:176.97.158.3

NS records: ns1.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com, ns5.markmonitor.com, ns6.markmonitor.com, ns7.markmonitor.com, ns2.markmonitor.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for ftftech.net (unsigned zone)

⏱️ Timing

Total: 694ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`64.71.164.66`
NS	7	`ns1.markmonitor.com, ns2.markmonitor.com...`
MX	5	`aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)...`
TXT	2	`MS=ms45697460, v=spf1 include:spf.ftftech.net -all`
SOA	1	`ns1.markmonitor.com hostmaster.markmonit`

Analysis

IP Addresses

ftftech.net resolves to just one IP address, 64.71.164.66.

ftftechnologies.net and firsttofile.org, along with other host names, share IP addresses with ftftech.net.

Name Servers

ftftech.net is served by 7 authoritative name servers — among them ns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com and 4 others.

ftftech.net partially shares its NS delegation with several other domains, including payeezy.hk, airpouch.com.pe, purolite.hk and two others.

The name servers ns4.markmonitor.com, ns5.markmonitor.com, ns6.markmonitor.com and ns7.markmonitor.com are often found in use alongside these name servers.

Host names that have two IP addresses:

ns1.markmonitor.com resolves to two addresses: 149.112.160.1 and 2620:10a:80a8::1.

ns2.markmonitor.com resolves to two addresses: 176.97.158.1 and 2001:67c:10b8::1.

ns3.markmonitor.com resolves to two addresses: 149.112.161.1 and 2620:10a:80a9::1.

ns4.markmonitor.com resolves to two addresses: 192.174.68.1 and 2001:67c:1bc::1.

ns5.markmonitor.com resolves to two addresses: 149.112.160.2 and 2620:10a:80a8::2.

ns6.markmonitor.com resolves to two addresses: 176.97.158.3 and 2001:67c:10b8::3.

ns7.markmonitor.com resolves to two addresses: 149.112.161.2 and 2620:10a:80a9::2.

Mail Servers

Mail for ftftech.net is handled by five mail servers, namely aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

There is at least a partial MX overlap between ftftech.net and other domains, including ns500759.ns500758.ns500758.ns500698.ns500698.ns500735.ns500698.ns500735.ns500708.ns500576.ns500576.ns500576.trackreceptor.com, ns500758.ns500698.ns500759.ns500698.ns500736.ns500735.ns500698.ns500736.ns500708.ns500576.ns500708.ns500619.ns500652.ns500619.ns500619.trackreceptor.com, ns500758.ns500698.ns500758.ns500759.ns500736.ns500736.ns500735.ns500698.ns500698.ns500708.ns500576.ns500698.ns500652.ns500652.trackreceptor.com and two others.

alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com are mail servers that frequently appear together with these mail servers.

Host names that have two IP addresses:

aspmx.l.google.com resolves to two addresses: 142.251.167.27 and 2607:f8b0:4004:c23::1b.

alt1.aspmx.l.google.com resolves to two addresses: 108.177.123.27 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.27 and 2a00:1450:4009:c0f::1b.

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

ftftech.net - robtex.com

ftftech.net

net

Same first word

Similar names

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

Analysis

IP Addresses

Name Servers

Mail Servers

`ftftech.net`

`net`