`warnetwork.fun`

DNSSEC	⚠️ Not signed
A	2606:4700:3032::6815:3fac^{🇺🇸 Cloudflare2606:4700:3032::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3037::ac43:94d4^{🇺🇸 Cloudflare2606:4700:3037::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.63.172^{Cloudflare104.21.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.148.212^{🇺🇸 Cloudflare172.67.144.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`chip.ns.cloudflare.com` ⭐
		A	2606:4700:58::adf5:3b54^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`chip.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c154^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`chip.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2154^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`chip.ns.cloudflare.com`
		A	108.162.193.84^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`chip.ns.cloudflare.com`
		A	172.64.33.84^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`chip.ns.cloudflare.com`
		A	173.245.59.84^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`chip.ns.cloudflare.com`
NS	`faye.ns.cloudflare.com`
		A	2606:4700:50::a29f:26b4^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`faye.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c2b4^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`faye.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:22b4^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`faye.ns.cloudflare.com`
		A	108.162.194.180^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`faye.ns.cloudflare.com`
		A	162.159.38.180^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`faye.ns.cloudflare.com`
		A	172.64.34.180^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`faye.ns.cloudflare.com`
MX	`route1.mx.cloudflare.net` ⭐
		A	2606:4700:f5::b^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::c^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::d^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.11^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.12^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.13^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
MX	`route2.mx.cloudflare.net`⁽²⁰⁾
		A	2606:4700:f5::e^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::f^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::10^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.17^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.18^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.19^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
MX	`route3.mx.cloudflare.net`⁽²⁰⁾
		A	2606:4700:f5::11^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::12^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::13^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.23^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.24^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.25^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
TXT	`v=spf1 include:_spf.mx.cloudflare.net ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4	104.21.63.172, 172.67.148.212
		IPv6	2606:4700:3032::6815:3fac, 2606:4700:3037::ac43:94d4
SOA	`chip.ns.cloudflare.com`dns@cloudflare.com serial=2397361752

`fun`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns01.trs-dns.com` ⭐
	NS	`ns.trs-dns.com`
	NS	`ns01.trs-dns.net`
	NS	`ns10.trs-dns.info`
	NS	`ns10.trs-dns.org`
	SOA	`ns.trs-dns.com`trs-ops@tucows.com serial=1774177714

Same first word

warnetwork.fun

Similar names

newartwork.digital

DNS History

10 records (9 active, 1 former)

●NSchip.ns.cloudflare.com2026-02-15 → 2026-03-23 · 2 obs

● 2026-02-15 08:53:40
● 2026-03-23 03:29:30

●NSfaye.ns.cloudflare.com2026-02-15 → 2026-03-23 · 2 obs

● 2026-02-15 08:53:40
● 2026-03-23 03:29:30

●MXroute1.mx.cloudflare.net2026-02-15 → 2026-03-23 · 2 obs

● 2026-02-15 08:53:40
● 2026-03-23 03:29:30

●MXroute2.mx.cloudflare.net2026-02-15 → 2026-03-23 · 2 obs

● 2026-02-15 08:53:40
● 2026-03-23 03:29:30

●MXroute3.mx.cloudflare.net2026-02-15 → 2026-03-23 · 2 obs

● 2026-02-15 08:53:40
● 2026-03-23 03:29:30

●A104.21.63.1722026-02-15 → 2026-03-23 · 6 obs

● 2026-02-15 08:53:40
● 2026-02-25 05:10:54
○ 2026-02-26 23:51:46
○ 2026-02-27 06:16:38
● 2026-03-01 18:57:54
● 2026-03-23 03:29:30

○A172.64.80.12026-02-26 → 2026-02-27 · 5 obs

○ 2026-02-25 05:10:54
● 2026-02-26 23:51:46
● 2026-02-27 06:16:38
○ 2026-03-01 18:57:54
○ 2026-03-23 03:29:30

●A172.67.148.2122026-02-15 → 2026-03-23 · 6 obs

● 2026-02-15 08:53:40
● 2026-02-25 05:10:54
○ 2026-02-26 23:51:46
○ 2026-02-27 06:16:38
● 2026-03-01 18:57:54
● 2026-03-23 03:29:30

●A2606:4700:3032::6815:3fac2026-02-15 → 2026-03-23 · 2 obs

● 2026-02-15 08:53:40
● 2026-03-23 03:29:30

●A2606:4700:3037::ac43:94d42026-02-15 → 2026-03-23 · 2 obs

● 2026-02-15 08:53:40
● 2026-03-23 03:29:30

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
fun	ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org, ns10.trs-dns.info	8 records
warnetwork.fun	chip.ns.cloudflare.com, faye.ns.cloudflare.com	-

✅ Authoritative Response

Server:162.159.38.180

NS records: chip.ns.cloudflare.com, faye.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for warnetwork.fun (unsigned zone)

⏱️ Timing

Total: 533ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`172.64.80.1`
AAAA	1	`2606:4700:130:436c:6f75:6466:6c61:7265`
NS	2	`chip.ns.cloudflare.com, faye.ns.cloudflare.com`
MX	3	`route2.mx.cloudflare.net (pri: 20), route3.mx.cloudflare.net (pri: 20)...`
TXT	1	`v=spf1 include:_spf.mx.cloudflare.net ~a`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`chip.ns.cloudflare.com dns.cloudflare.co`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns01.trs-dns.com, ns01.trs-dns.com, ns01.trs-dns.net...)

Analysis

IP Addresses

warnetwork.fun points to four IP numbers: 2606:4700:3032::6815:3fac, 2606:4700:3037::ac43:94d4, 104.21.63.172 and 172.67.148.212.

Other host names including srilankaembassy.at, myresellrightsproducts.com.cdn.cloudflare.net, panaceava.com, psy-declic.fr and nektor.de share IP numbers with warnetwork.fun.

Name Servers

warnetwork.fun's delegation uses two name servers, chip.ns.cloudflare.com and faye.ns.cloudflare.com.

warnetwork.fun uses the same name server setup as asliinc.com and d3design.vn and relevant.co.

warnetwork.fun at least partially shares name servers with other domains, including scommessedeposito.com, soma-read.com, mcookie.cn, pvweb.mx and lukeinfinger.com.

these name servers are commonly used together with liberty.ns.cloudflare.com, mitch.ns.cloudflare.com and nelly.ns.cloudflare.com.

Host names with six IP numbers:

chip.ns.cloudflare.com points to: 2606:4700:58::adf5:3b54, 2803:f800:50::6ca2:c154, 2a06:98c1:50::ac40:2154, 108.162.193.84, 172.64.33.84 and 173.245.59.84.

faye.ns.cloudflare.com points to: 2606:4700:50::a29f:26b4, 2803:f800:50::6ca2:c2b4, 2a06:98c1:50::ac40:22b4, 108.162.194.180, 162.159.38.180 and 172.64.34.180.

Mail Servers

warnetwork.fun is handled by three mail servers: route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

The mail servers for warnetwork.fun are shared with other domains, for instance ultimatealtitude.com, masturhub.com, solaceimage.com, kzhu.men and oswled.com.

Host names with six IP numbers:

route1.mx.cloudflare.net points to 2606:4700:f5::b, 2606:4700:f5::c, 2606:4700:f5::d, 162.159.205.11, 162.159.205.12 and 162.159.205.13.

route2.mx.cloudflare.net points to 2606:4700:f5::e, 2606:4700:f5::f, 2606:4700:f5::10, 162.159.205.17, 162.159.205.18 and 162.159.205.19.

route3.mx.cloudflare.net points to 2606:4700:f5::11, 2606:4700:f5::12, 2606:4700:f5::13, 162.159.205.23, 162.159.205.24 and 162.159.205.25.

warnetwork.fun - robtex.com

warnetwork.fun

fun

Same first word

Similar names

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

📌 Glue Records Collected

Analysis

IP Addresses

Name Servers

Mail Servers

`warnetwork.fun`

`fun`