dotft.com - dns.ninja

`dotft.com`

DNSSEC	⚠️ Not signed
A	64.190.63.222^{🇩🇪 SEDO64.190.62.0/23 -NET2-PI}
NS	`ns1.sedoparking.com` ⭐
		A	3.130.216.63^{🇺🇸 Amazon3.130.0.0/16 EC2 CMH prefix}
			PTR	`ec2-3-130-216-63.us-east-2.compute.amazonaws.com`
		A	91.195.241.8^{🇩🇪 SEDO91.195.240.0/23 -NET-PI}
NS	`ns2.sedoparking.com`
		A	34.211.188.210^{🇺🇸 Amazon34.208.0.0/12 EC2 PDX prefix}
			PTR	`ec2-34-211-188-210.us-west-2.compute.amazonaws.com`
		A	91.195.240.8^{🇩🇪 SEDO91.195.240.0/23 -NET-PI}
MX	`localhost` ⭐ 🔒
		A	`::1`
		A	127.0.0.1
TXT	`v=spf1 -all`
SOA	`ns1.sedoparking.com`hostmaster@sedo.de 2018-05-16 #1

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

Same first word

dotft.com

dotft.org

Similar names

ftdot.com

otftd.blogspot.com

otftd.blogspot.co.uk

dottf.com

totdf.org

todtf.com

dtoft.com

DNS History

25 records (4 active, 21 former)

○NSdns1.registrar-servers.com2019-03-25 → 2019-03-25 · 4 obs

○ 2017-02-12 06:01:18
● 2019-03-25 04:03:32
○ 2026-02-16 00:22:46
○ 2026-07-08 02:15:30

○NSdns2.registrar-servers.com2019-03-25 → 2019-03-25 · 4 obs

○ 2017-02-12 06:01:18
● 2019-03-25 04:03:32
○ 2026-02-16 00:22:46
○ 2026-07-08 02:15:30

○NSines.ns.cloudflare.com2026-02-16 → 2026-06-13 · 5 obs

○ 2019-03-25 04:03:32
● 2026-02-16 00:22:46
● 2026-06-13 13:13:50
○ 2026-06-16 22:42:18
○ 2026-07-08 02:15:30

○NSns1.domain-resolution.net2015-08-03 → 2017-02-12 · 4 obs

● 2015-08-03 03:05:02
● 2017-02-12 06:01:18
○ 2019-03-25 04:03:32
○ 2026-07-08 02:15:30

●NSns1.sedoparking.com2026-06-16 → 2026-07-08 · 3 obs

○ 2026-06-13 13:13:50
● 2026-06-16 22:42:18
● 2026-07-08 02:15:30

●NSns2.sedoparking.com2026-06-16 → 2026-07-08 · 3 obs

○ 2026-06-13 13:13:50
● 2026-06-16 22:42:18
● 2026-07-08 02:15:30

○NSns2qvz.domain-resolution.net2015-08-03 → 2017-02-12 · 4 obs

● 2015-08-03 03:05:02
● 2017-02-12 06:01:18
○ 2019-03-25 04:03:32
○ 2026-07-08 02:15:30

○NSns3.domain-resolution.net2015-08-03 → 2017-02-12 · 4 obs

● 2015-08-03 03:05:02
● 2017-02-12 06:01:18
○ 2019-03-25 04:03:32
○ 2026-07-08 02:15:30

○NSns4qxz.domain-resolution.net2015-08-03 → 2017-02-12 · 4 obs

● 2015-08-03 03:05:02
● 2017-02-12 06:01:18
○ 2019-03-25 04:03:32
○ 2026-07-08 02:15:30

○NSwest.ns.cloudflare.com2026-02-16 → 2026-06-13 · 5 obs

○ 2019-03-25 04:03:32
● 2026-02-16 00:22:46
● 2026-06-13 13:13:50
○ 2026-06-16 22:42:18
○ 2026-07-08 02:15:30

○MXalt1.aspmx.l.google.com2015-08-03 → 2026-06-13 · 4 obs

● 2015-08-03 03:05:02
● 2026-06-13 13:13:50
○ 2026-06-16 22:42:18
○ 2026-07-08 02:15:30

○MXalt2.aspmx.l.google.com2015-08-03 → 2026-06-13 · 4 obs

● 2015-08-03 03:05:02
● 2026-06-13 13:13:50
○ 2026-06-16 22:42:18
○ 2026-07-08 02:15:30

○MXalt3.aspmx.l.google.com2016-05-09 → 2026-06-13 · 8 obs

○ 2016-02-22 10:48:58
● 2016-05-09 09:34:02
● 2017-02-12 06:01:18
○ 2019-03-25 04:03:32
● 2026-02-16 00:22:46
● 2026-06-13 13:13:50
○ 2026-06-16 22:42:18
○ 2026-07-08 02:15:30

○MXalt4.aspmx.l.google.com2016-05-09 → 2026-06-13 · 8 obs

○ 2016-02-22 10:48:58
● 2016-05-09 09:34:02
● 2017-02-12 06:01:18
○ 2019-03-25 04:03:32
● 2026-02-16 00:22:46
● 2026-06-13 13:13:50
○ 2026-06-16 22:42:18
○ 2026-07-08 02:15:30

○MXaspmx.l.google.com2015-08-03 → 2026-06-13 · 4 obs

● 2015-08-03 03:05:02
● 2026-06-13 13:13:50
○ 2026-06-16 22:42:18
○ 2026-07-08 02:15:30

○MXaspmx2.googlemail.com2015-08-03 → 2019-03-25 · 7 obs

● 2015-08-03 03:05:02
● 2016-02-22 10:48:58
○ 2016-05-09 09:34:02
○ 2017-02-12 06:01:18
● 2019-03-25 04:03:32
○ 2026-02-16 00:22:46
○ 2026-07-08 02:15:30

○MXaspmx3.googlemail.com2015-08-03 → 2019-03-25 · 7 obs

● 2015-08-03 03:05:02
● 2016-02-22 10:48:58
○ 2016-05-09 09:34:02
○ 2017-02-12 06:01:18
● 2019-03-25 04:03:32
○ 2026-02-16 00:22:46
○ 2026-07-08 02:15:30

●MXlocalhost2026-06-16 → 2026-07-08 · 3 obs

○ 2026-06-13 13:13:50
● 2026-06-16 22:42:18
● 2026-07-08 02:15:30

○A104.21.76.182026-02-16 → 2026-06-13 · 5 obs

○ 2019-03-25 04:03:32
● 2026-02-16 00:22:46
● 2026-06-13 13:13:50
○ 2026-06-16 22:42:18
○ 2026-07-08 02:15:30

○A172.67.185.182026-02-16 → 2026-06-13 · 5 obs

○ 2019-03-25 04:03:32
● 2026-02-16 00:22:46
● 2026-06-13 13:13:50
○ 2026-06-16 22:42:18
○ 2026-07-08 02:15:30

○A198.199.119.1482016-02-22 → 2019-03-25 · 5 obs

○ 2015-12-31 21:44:24
● 2016-02-22 10:48:58
● 2019-03-25 04:03:32
○ 2026-02-16 00:22:46
○ 2026-07-08 02:15:30

○A2606:4700:3034::6815:4c122026-02-16 → 2026-06-13 · 5 obs

○ 2019-03-25 04:03:32
● 2026-02-16 00:22:46
● 2026-06-13 13:13:50
○ 2026-06-16 22:42:18
○ 2026-07-08 02:15:30

○A2606:4700:3037::ac43:b9122026-02-16 → 2026-06-13 · 5 obs

○ 2019-03-25 04:03:32
● 2026-02-16 00:22:46
● 2026-06-13 13:13:50
○ 2026-06-16 22:42:18
○ 2026-07-08 02:15:30

○A54.64.186.1192015-08-03 → 2015-12-31 · 4 obs

● 2015-08-03 03:05:02
● 2015-12-31 21:44:24
○ 2016-02-22 10:48:58
○ 2026-07-08 02:15:30

●A64.190.63.2222026-06-16 → 2026-07-08 · 3 obs

○ 2026-06-13 13:13:50
● 2026-06-16 22:42:18
● 2026-07-08 02:15:30

🔍 DNS Trace

Analysis

IP Addresses

dotft.com directs to one IP number, which is 64.190.63.222.

Name Servers

dotft.com has two authoritative name servers — ns1.sedoparking.com and ns2.sedoparking.com.

Both ns1.sedoparking.com and ns2.sedoparking.com have two IP addresses each. ns1.sedoparking.com resolves to 3.130.216.63 and 91.195.241.8; ns2.sedoparking.com resolves to 34.211.188.210 and 91.195.240.8.

Mail Servers

dotft.com routes its mail through a single mail server, localhost.

localhost resolves to two IP numbers — 127.0.0.1 and ::1.