tmf2.com - dns.ninja

`tmf2.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3031::ac43:d5c0^{🇺🇸 Cloudflare2606:4700:3031::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3033::6815:4b2c^{🇺🇸 Cloudflare2606:4700:3033::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.75.44^{Cloudflare104.21.64.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.213.192^{🇺🇸 Cloudflare172.67.208.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`aspen.ns.cloudflare.com` ⭐
		A	2606:4700:50::a29f:266d^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`aspen.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c26d^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`aspen.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:226d^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`aspen.ns.cloudflare.com`
		A	108.162.194.109^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`aspen.ns.cloudflare.com`
		A	162.159.38.109^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`aspen.ns.cloudflare.com`
		A	172.64.34.109^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`aspen.ns.cloudflare.com`
NS	`trace.ns.cloudflare.com`
		A	2606:4700:58::a29f:2cac^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`trace.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c3ac^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`trace.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:23ac^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`trace.ns.cloudflare.com`
		A	108.162.195.172^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`trace.ns.cloudflare.com`
		A	162.159.44.172^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`trace.ns.cloudflare.com`
		A	172.64.35.172^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`trace.ns.cloudflare.com`
MX	`mx2.zoho.com` ⭐
		A	136.143.183.44^{🇺🇸 ZohoAS136.143.182.0/23 Zoho}
			PTR	`mx2.zoho.com`
			PTR	`mx3.zoho.com`
			PTR	`mx.zoho.com`
			PTR	`mx2.zohomail.com`
			PTR	`mx3.zohomail.com`
			PTR	`mx.zohomail.com`
MX	`mx3.zoho.com`⁽²⁰⁾
		A	204.141.43.44^{🇺🇸 ZohoAS204.141.42.0/23 Zoho Corporation}
			PTR	`mx2.zoho.com`
			PTR	`mx3.zoho.com`
			PTR	`mx6.zoho.com`
			PTR	`mx7.zoho.com`
			PTR	`mx8.zoho.com`
			PTR	`mx.zoho.com`
			PTR	`mx2.zohomail.com`
			PTR	`mx3.zohomail.com`
			PTR	`mx.zohomail.com`
MX	`mx.zoho.com`⁽³⁰⁾
		A	204.141.43.44^{🇺🇸 ZohoAS204.141.42.0/23 Zoho Corporation}
			PTR	`mx2.zoho.com`
			PTR	`mx3.zoho.com`
			PTR	`mx6.zoho.com`
			PTR	`mx7.zoho.com`
			PTR	`mx8.zoho.com`
			PTR	`mx.zoho.com`
			PTR	`mx2.zohomail.com`
			PTR	`mx3.zohomail.com`
			PTR	`mx.zohomail.com`
TXT	`v=spf1 include:zoho.com ~all`
TXT	`zoho-verification=zb10787164.zmverify.zoho.com`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.75.44, 172.67.213.192
		IPv6 hints	2606:4700:3031::ac43:d5c0, 2606:4700:3033::6815:4b2c
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=17, name=cloudflare-ech.com
SOA	`aspen.ns.cloudflare.com`dns@cloudflare.com serial=2411231546

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

Same first word

tmf2.com

Similar names

tf2m.com

fmt2.myshopify.com

m2tf.org

f2tm.com

tm2f.com

2mft.com

tfm2.co.uk

ftm2.com

m2tf.com

m2ft.com

t2mf.com

DNS History

30 records (9 active, 21 former)

●NSaspen.ns.cloudflare.com2026-03-13 → 2026-08-04 · 3 obs

○ 2017-06-26 15:34:28
● 2026-03-13 16:50:24
● 2026-08-04 08:46:16

○NSns-us.1and1-dns.com2015-06-28 → 2016-11-28 · 4 obs

● 2015-06-28 16:20:28
● 2016-11-28 14:55:42
○ 2017-06-26 15:34:28
○ 2026-08-04 08:46:16

○NSns-us.1and1-dns.de2015-06-28 → 2016-11-28 · 4 obs

● 2015-06-28 16:20:28
● 2016-11-28 14:55:42
○ 2017-06-26 15:34:28
○ 2026-08-04 08:46:16

○NSns-us.1and1-dns.org2015-06-28 → 2016-11-28 · 4 obs

● 2015-06-28 16:20:28
● 2016-11-28 14:55:42
○ 2017-06-26 15:34:28
○ 2026-08-04 08:46:16

○NSns-us.1and1-dns.us2015-06-28 → 2016-11-28 · 4 obs

● 2015-06-28 16:20:28
● 2016-11-28 14:55:42
○ 2017-06-26 15:34:28
○ 2026-08-04 08:46:16

○NSns1.dynu.com2017-06-26 → 2017-06-26 · 4 obs

○ 2016-11-28 14:55:42
● 2017-06-26 15:34:28
○ 2026-03-13 16:50:24
○ 2026-08-04 08:46:16

○NSns2.dynu.com2017-06-26 → 2017-06-26 · 4 obs

○ 2016-11-28 14:55:42
● 2017-06-26 15:34:28
○ 2026-03-13 16:50:24
○ 2026-08-04 08:46:16

○NSns3.dynu.com2017-06-26 → 2017-06-26 · 4 obs

○ 2016-11-28 14:55:42
● 2017-06-26 15:34:28
○ 2026-03-13 16:50:24
○ 2026-08-04 08:46:16

○NSns4.dynu.com2017-06-26 → 2017-06-26 · 4 obs

○ 2016-11-28 14:55:42
● 2017-06-26 15:34:28
○ 2026-03-13 16:50:24
○ 2026-08-04 08:46:16

○NSns5.dynu.com2017-06-26 → 2017-06-26 · 4 obs

○ 2016-11-28 14:55:42
● 2017-06-26 15:34:28
○ 2026-03-13 16:50:24
○ 2026-08-04 08:46:16

○NSns6.dynu.com2017-06-26 → 2017-06-26 · 4 obs

○ 2016-11-28 14:55:42
● 2017-06-26 15:34:28
○ 2026-03-13 16:50:24
○ 2026-08-04 08:46:16

●NStrace.ns.cloudflare.com2026-03-13 → 2026-08-04 · 3 obs

○ 2017-06-26 15:34:28
● 2026-03-13 16:50:24
● 2026-08-04 08:46:16

○MXmail.tmf2.com2015-06-28 → 2016-11-28 · 4 obs

● 2015-06-28 16:20:28
● 2016-11-28 14:55:42
○ 2017-06-26 15:34:28
○ 2026-08-04 08:46:16

●MXmx.zoho.com2026-03-13 → 2026-08-04 · 3 obs

○ 2017-06-26 15:34:28
● 2026-03-13 16:50:24
● 2026-08-04 08:46:16

○MXmx00.1and1.com2017-06-26 → 2017-06-26 · 4 obs

○ 2016-11-28 14:55:42
● 2017-06-26 15:34:28
○ 2026-03-13 16:50:24
○ 2026-08-04 08:46:16

○MXmx01.1and1.com2017-06-26 → 2017-06-26 · 4 obs

○ 2016-11-28 14:55:42
● 2017-06-26 15:34:28
○ 2026-03-13 16:50:24
○ 2026-08-04 08:46:16

●MXmx2.zoho.com2026-03-13 → 2026-08-04 · 3 obs

○ 2017-06-26 15:34:28
● 2026-03-13 16:50:24
● 2026-08-04 08:46:16

●MXmx3.zoho.com2026-03-13 → 2026-08-04 · 3 obs

○ 2017-06-26 15:34:28
● 2026-03-13 16:50:24
● 2026-08-04 08:46:16

●A104.21.75.442026-03-13 → 2026-08-04 · 4 obs

○ 2017-06-26 15:34:28
● 2026-03-13 16:50:24
○ 2026-07-02 21:15:22
● 2026-08-04 08:46:16

●A172.67.213.1922026-03-13 → 2026-08-04 · 4 obs

○ 2017-06-26 15:34:28
● 2026-03-13 16:50:24
○ 2026-07-02 21:15:22
● 2026-08-04 08:46:16

○A188.114.96.02026-07-02 → 2026-07-02 · 3 obs

○ 2026-03-13 16:50:24
● 2026-07-02 21:15:22
○ 2026-08-04 08:46:16

○A188.114.97.02026-07-02 → 2026-07-02 · 3 obs

○ 2026-03-13 16:50:24
● 2026-07-02 21:15:22
○ 2026-08-04 08:46:16

○A23.252.3.142015-06-28 → 2016-11-28 · 4 obs

● 2015-06-28 16:20:28
● 2016-11-28 14:55:42
○ 2017-06-26 15:34:28
○ 2026-08-04 08:46:16

○A24.246.49.482017-06-26 → 2017-06-26 · 4 obs

○ 2016-11-28 14:55:42
● 2017-06-26 15:34:28
○ 2026-03-13 16:50:24
○ 2026-08-04 08:46:16

●A2606:4700:3031::ac43:d5c02026-06-25 → 2026-08-04 · 4 obs

○ 2026-03-13 16:50:24
● 2026-06-25 05:09:50
○ 2026-07-02 21:15:22
● 2026-08-04 08:46:16

●A2606:4700:3033::6815:4b2c2026-06-25 → 2026-08-04 · 4 obs

○ 2026-03-13 16:50:24
● 2026-06-25 05:09:50
○ 2026-07-02 21:15:22
● 2026-08-04 08:46:16

○A2606:4700:3034::ac43:d5c02026-03-13 → 2026-03-13 · 4 obs

○ 2017-06-26 15:34:28
● 2026-03-13 16:50:24
○ 2026-06-25 05:09:50
○ 2026-08-04 08:46:16

○A2606:4700:3037::6815:4b2c2026-03-13 → 2026-03-13 · 4 obs

○ 2017-06-26 15:34:28
● 2026-03-13 16:50:24
○ 2026-06-25 05:09:50
○ 2026-08-04 08:46:16

○A2a06:98c1:3120::2026-07-02 → 2026-07-02 · 3 obs

○ 2026-03-13 16:50:24
● 2026-07-02 21:15:22
○ 2026-08-04 08:46:16

○A2a06:98c1:3121::2026-07-02 → 2026-07-02 · 3 obs

○ 2026-03-13 16:50:24
● 2026-07-02 21:15:22
○ 2026-08-04 08:46:16

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
tmf2.com	aspen.ns.cloudflare.com, trace.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.195.172

NS records: aspen.ns.cloudflare.com, trace.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for tmf2.com (unsigned zone)

⏱️ Timing

Total: 1648ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.75.44, 172.67.213.192`
AAAA	2	`2606:4700:3033::6815:4b2c, 2606:4700:3031::ac43:d5c0`
NS	2	`aspen.ns.cloudflare.com, trace.ns.cloudflare.com`
MX	3	`mx.zoho.com (pri: 10), mx2.zoho.com (pri: 20)...`
TXT	2	`v=spf1 include:zoho.com ~all, zoho-verification=zb10787164.zmverify.zo`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`aspen.ns.cloudflare.com dns.cloudflare.c`

📌 Glue Records Collected

Total: 12

Out-of-bailiwick: 12 (aspen.ns.cloudflare.com, aspen.ns.cloudflare.com, aspen.ns.cloudflare.com...)

Analysis

IP Addresses

tmf2.com resolves to four IP addresses: 104.21.75.44, 172.67.213.192, 2606:4700:3031::ac43:d5c0 and 2606:4700:3033::6815:4b2c.

lemoninsight.com, www.aries.co.za, vefenex.world and two other host names share IP numbers with tmf2.com.

Name Servers

tmf2.com is delegated to two name servers: aspen.ns.cloudflare.com and trace.ns.cloudflare.com.

tmf2.com uses the same name servers as several other domains — among them fireant22.com, chiefmind.cc, fireantvn.com and two more.

tmf2.com partially shares its NS delegation with several other domains, including bluecommunitytoday.nl, lokoplans.com, azwm.net and two others.

The name servers gordon.ns.cloudflare.com, becky.ns.cloudflare.com, nash.ns.cloudflare.com and elsa.ns.cloudflare.com are often found in use alongside these name servers.

Hostnames that resolve to 6 IP addresses:

aspen.ns.cloudflare.com resolves to 108.162.194.109, 162.159.38.109, 172.64.34.109 and 3 other IP addresses.

trace.ns.cloudflare.com resolves to 108.162.195.172, 162.159.44.172, 172.64.35.172 and 3 other IP addresses.

Mail Servers

tmf2.com uses three mail servers — mx2.zoho.com, mx3.zoho.com and mx.zoho.com.

tmf2.com has at least partial mail server overlap with other domains such as dialogoymovimiento.org, alfilsecurity.com, kalajan.com and two more.

mx2.zoho.com resolves to 136.143.183.44, while mx3.zoho.com and mx.zoho.com both resolve to 204.141.43.44.

mx3.zoho.com and mx.zoho.com are host names that each point to 204.141.43.44 IP addresses.