`teamfett.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3034::ac43:8179^{🇺🇸 Cloudflare2606:4700:3034::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3037::6815:2a9^{🇺🇸 Cloudflare2606:4700:3037::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.2.169^{Cloudflare104.21.0.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.129.121^{🇺🇸 Cloudflare172.67.128.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`dayana.ns.cloudflare.com` ⭐
		A	2606:4700:50::a29f:2667^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`dayana.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c267^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`dayana.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2267^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`dayana.ns.cloudflare.com`
		A	108.162.194.103^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`dayana.ns.cloudflare.com`
		A	162.159.38.103^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`dayana.ns.cloudflare.com`
		A	172.64.34.103^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`dayana.ns.cloudflare.com`
NS	`leland.ns.cloudflare.com`
		A	2606:4700:58::a29f:2c08^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`leland.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c308^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`leland.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2308^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`leland.ns.cloudflare.com`
		A	108.162.195.8^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`leland.ns.cloudflare.com`
		A	162.159.44.8^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`leland.ns.cloudflare.com`
		A	172.64.35.8^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`leland.ns.cloudflare.com`
MX	`mx1.titan.email` ⭐
		A	3.223.93.12^{🇺🇸 Amazon3.208.0.0/12 EC2 IAD prefix}
			PTR	`ec2-3-223-93-12.compute-1.amazonaws.com`
		A	34.195.53.246^{🇺🇸 Amazon34.192.0.0/12 EC2 IAD prefix}
			PTR	`ec2-34-195-53-246.compute-1.amazonaws.com`
		A	34.196.168.106^{🇺🇸 Amazon34.192.0.0/12 EC2 IAD prefix}
			PTR	`ec2-34-196-168-106.compute-1.amazonaws.com`
MX	`mx2.titan.email`⁽²⁰⁾
		A	3.223.93.12^{🇺🇸 Amazon3.208.0.0/12 EC2 IAD prefix}
			PTR	`ec2-3-223-93-12.compute-1.amazonaws.com`
		A	34.195.53.246^{🇺🇸 Amazon34.192.0.0/12 EC2 IAD prefix}
			PTR	`ec2-34-195-53-246.compute-1.amazonaws.com`
		A	34.196.168.106^{🇺🇸 Amazon34.192.0.0/12 EC2 IAD prefix}
			PTR	`ec2-34-196-168-106.compute-1.amazonaws.com`
TXT	`v=spf1 include:spf.titan.email ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.2.169, 172.67.129.121
		IPv6 hints	2606:4700:3034::ac43:8179, 2606:4700:3037::6815:2a9
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=127, name=cloudflare-ech.com
SOA	`dayana.ns.cloudflare.com`dns@cloudflare.com serial=2400016780

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

Same first word

teamfett.com

DNS History

18 records (8 active, 10 former)

●NSdayana.ns.cloudflare.com2026-04-02 → 2026-04-08 · 3 obs

○ 2017-07-03 14:18:18
● 2026-04-02 05:23:38
● 2026-04-08 20:33:14

●NSleland.ns.cloudflare.com2026-04-02 → 2026-04-08 · 3 obs

○ 2017-07-03 14:18:18
● 2026-04-02 05:23:38
● 2026-04-08 20:33:14

○NSns-1344.awsdns-40.org2016-12-18 → 2017-07-03 · 4 obs

● 2016-12-18 19:18:28
● 2017-07-03 14:18:18
○ 2026-04-02 05:23:38
○ 2026-04-08 20:33:14

○NSns-1767.awsdns-28.co.uk2016-12-18 → 2017-07-03 · 4 obs

● 2016-12-18 19:18:28
● 2017-07-03 14:18:18
○ 2026-04-02 05:23:38
○ 2026-04-08 20:33:14

○NSns-490.awsdns-61.com2016-12-18 → 2017-07-03 · 4 obs

● 2016-12-18 19:18:28
● 2017-07-03 14:18:18
○ 2026-04-02 05:23:38
○ 2026-04-08 20:33:14

○NSns-630.awsdns-14.net2016-12-18 → 2017-07-03 · 4 obs

● 2016-12-18 19:18:28
● 2017-07-03 14:18:18
○ 2026-04-02 05:23:38
○ 2026-04-08 20:33:14

○MXalt1.aspmx.l.google.com2016-12-18 → 2017-07-03 · 4 obs

● 2016-12-18 19:18:28
● 2017-07-03 14:18:18
○ 2026-04-02 05:23:38
○ 2026-04-08 20:33:14

○MXalt2.aspmx.l.google.com2016-12-18 → 2017-07-03 · 4 obs

● 2016-12-18 19:18:28
● 2017-07-03 14:18:18
○ 2026-04-02 05:23:38
○ 2026-04-08 20:33:14

○MXaspmx.l.google.com2016-12-18 → 2017-07-03 · 4 obs

● 2016-12-18 19:18:28
● 2017-07-03 14:18:18
○ 2026-04-02 05:23:38
○ 2026-04-08 20:33:14

○MXaspmx2.googlemail.com2016-12-18 → 2017-07-03 · 4 obs

● 2016-12-18 19:18:28
● 2017-07-03 14:18:18
○ 2026-04-02 05:23:38
○ 2026-04-08 20:33:14

○MXaspmx3.googlemail.com2016-12-18 → 2017-07-03 · 4 obs

● 2016-12-18 19:18:28
● 2017-07-03 14:18:18
○ 2026-04-02 05:23:38
○ 2026-04-08 20:33:14

●MXmx1.titan.email2026-04-02 → 2026-04-08 · 3 obs

○ 2017-07-03 14:18:18
● 2026-04-02 05:23:38
● 2026-04-08 20:33:14

●MXmx2.titan.email2026-04-02 → 2026-04-08 · 3 obs

○ 2017-07-03 14:18:18
● 2026-04-02 05:23:38
● 2026-04-08 20:33:14

●A104.21.2.1692026-04-02 → 2026-04-08 · 3 obs

○ 2017-07-03 14:18:18
● 2026-04-02 05:23:38
● 2026-04-08 20:33:14

●A172.67.129.1212026-04-02 → 2026-04-08 · 3 obs

○ 2017-07-03 14:18:18
● 2026-04-02 05:23:38
● 2026-04-08 20:33:14

●A2606:4700:3034::ac43:81792026-04-02 → 2026-04-08 · 3 obs

○ 2017-07-03 14:18:18
● 2026-04-02 05:23:38
● 2026-04-08 20:33:14

●A2606:4700:3037::6815:2a92026-04-02 → 2026-04-08 · 3 obs

○ 2017-07-03 14:18:18
● 2026-04-02 05:23:38
● 2026-04-08 20:33:14

○A54.86.147.1972016-12-18 → 2017-07-03 · 4 obs

● 2016-12-18 19:18:28
● 2017-07-03 14:18:18
○ 2026-04-02 05:23:38
○ 2026-04-08 20:33:14

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
teamfett.com	dayana.ns.cloudflare.com, leland.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.195.8

NS records: dayana.ns.cloudflare.com, leland.ns.cloudflare.com

🔒 DNSSEC Status

🔐 Secure (DNSSEC validated)

Chain of trust verified from root to domain

⏱️ Timing

Total: 324ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.2.169, 172.67.129.121`
AAAA	2	`2606:4700:3034::ac43:8179, 2606:4700:3037::6815:2a9`
NS	2	`dayana.ns.cloudflare.com, leland.ns.cloudflare.com`
MX	2	`mx1.titan.email (pri: 10), mx2.titan.email (pri: 20)`
TXT	1	`v=spf1 include:spf.titan.email ~all`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`dayana.ns.cloudflare.com dns.cloudflare.`

📌 Glue Records Collected

Total: 12

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

Analysis

IP Addresses

teamfett.com resolves to four IP numbers: 2606:4700:3034::ac43:8179, 2606:4700:3037::6815:2a9, 104.21.2.169 and 172.67.129.121.

Other host names such as yatirimgurusu.com, www.gynexin.com, baywa-re.co.uk, collectfootprints.com and rus.seg.ar share IPs with teamfett.com.

Name Servers

teamfett.com is delegated to two name servers: dayana.ns.cloudflare.com and leland.ns.cloudflare.com.

teamfett.com shares the same name server setup as booty(0x787878).com, anemidesign.com, (0x736578)ebony.com, hornypersonals.com and bdsmpunishment.com.

teamfett.com at least partially shares name servers with other domains, for instance 567728.com, unlockfull.com, deepinfomedical.com, mergersandlegalteam.com and azans.az.

These name servers are commonly used together with elma.ns.cloudflare.com, bradley.ns.cloudflare.com and rayden.ns.cloudflare.com.

Host names with six IP numbers:

dayana.ns.cloudflare.com points to 2606:4700:50::a29f:2667, 2803:f800:50::6ca2:c267, 2a06:98c1:50::ac40:2267, 108.162.194.103, 162.159.38.103 and 172.64.34.103.

leland.ns.cloudflare.com points to 2606:4700:58::a29f:2c08, 2803:f800:50::6ca2:c308, 2a06:98c1:50::ac40:2308, 108.162.195.8, 162.159.44.8 and 172.64.35.8.

Mail Servers

teamfett.com is handled by two mail servers: mx1.titan.email and mx2.titan.email.

The mail server setup for teamfett.com matches that of other domains, for instance dzili.com, willataylor.com, borgdanastasi.com, avishaymizrav.com and energizedgraphics.com.

teamfett.com shares some mail servers with other domains, at least in part, for instance tmalleyne.com.

Host names with three IP numbers:

mx1.titan.email points to 3.223.93.12, 34.195.53.246 and 34.196.168.106.

mx2.titan.email points to 3.223.93.12, 34.195.53.246 and 34.196.168.106.

Names that point to 3.223.93.12: mx1.titan.email and mx2.titan.email.

Names that point to 34.195.53.246: mx1.titan.email and mx2.titan.email.

Names that point to 34.196.168.106: mx1.titan.email and mx2.titan.email.

teamfett.com - robtex.com

teamfett.com

com

Same first word

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

📌 Glue Records Collected

Analysis

IP Addresses

Name Servers

Mail Servers

`teamfett.com`

`com`