`crypto-war.net`

DNSSEC	⚠️ Not signed
A	2606:4700:3032::6815:3bbe^{🇺🇸 Cloudflare2606:4700:3032::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3037::ac43:b675^{🇺🇸 Cloudflare2606:4700:3037::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.59.190^{Cloudflare104.21.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.182.117^{🇺🇸 Cloudflare172.67.176.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`ken.ns.cloudflare.com` ⭐
		A	2606:4700:58::adf5:3b7f^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ken.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c17f^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`ken.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:217f^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`ken.ns.cloudflare.com`
		A	108.162.193.127^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ken.ns.cloudflare.com`
		A	172.64.33.127^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ken.ns.cloudflare.com`
		A	173.245.59.127^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ken.ns.cloudflare.com`
NS	`pearl.ns.cloudflare.com`
		A	2606:4700:50::a29f:268c^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`pearl.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c28c^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`pearl.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:228c^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`pearl.ns.cloudflare.com`
		A	108.162.194.140^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`pearl.ns.cloudflare.com`
		A	162.159.38.140^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`pearl.ns.cloudflare.com`
		A	172.64.34.140^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`pearl.ns.cloudflare.com`
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`
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`
TXT	`v=spf1 include:_spf.mx.cloudflare.net ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.59.190, 172.67.182.117
		IPv6 hints	2606:4700:3032::6815:3bbe, 2606:4700:3037::ac43:b675
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=84, name=cloudflare-ech.com
SOA	`ken.ns.cloudflare.com`dns@cloudflare.com serial=2410273445

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

Same first word

crypto-war.net

DNS History

24 records (9 active, 15 former)

○NS01.dnsv.jp2018-05-13 → 2018-05-13 · 3 obs

● 2018-05-13 06:24:54
○ 2026-04-04 18:46:50
○ 2026-08-01 05:30:02

○NS02.dnsv.jp2018-05-13 → 2018-05-13 · 3 obs

● 2018-05-13 06:24:54
○ 2026-04-04 18:46:50
○ 2026-08-01 05:30:02

○NS03.dnsv.jp2018-05-13 → 2018-05-13 · 3 obs

● 2018-05-13 06:24:54
○ 2026-04-04 18:46:50
○ 2026-08-01 05:30:02

○NS04.dnsv.jp2018-05-13 → 2018-05-13 · 3 obs

● 2018-05-13 06:24:54
○ 2026-04-04 18:46:50
○ 2026-08-01 05:30:02

●NSken.ns.cloudflare.com2026-04-04 → 2026-08-01 · 3 obs

○ 2018-05-13 06:24:54
● 2026-04-04 18:46:50
● 2026-08-01 05:30:02

○NSns-canada.topdns.com2026-04-04 → 2026-08-01 · 2 obs

○ 2026-04-04 18:46:50
○ 2026-08-01 05:30:02

○NSns-uk.topdns.com2026-04-04 → 2026-08-01 · 2 obs

○ 2026-04-04 18:46:50
○ 2026-08-01 05:30:02

○NSns-usa.topdns.com2026-04-04 → 2026-08-01 · 2 obs

○ 2026-04-04 18:46:50
○ 2026-08-01 05:30:02

●NSpearl.ns.cloudflare.com2026-04-04 → 2026-08-01 · 3 obs

○ 2018-05-13 06:24:54
● 2026-04-04 18:46:50
● 2026-08-01 05:30:02

●MXroute1.mx.cloudflare.net2026-04-04 → 2026-08-01 · 2 obs

● 2026-04-04 18:46:50
● 2026-08-01 05:30:02

●MXroute2.mx.cloudflare.net2026-04-04 → 2026-08-01 · 2 obs

● 2026-04-04 18:46:50
● 2026-08-01 05:30:02

●MXroute3.mx.cloudflare.net2026-04-04 → 2026-08-01 · 2 obs

● 2026-04-04 18:46:50
● 2026-08-01 05:30:02

●A104.21.59.1902026-04-04 → 2026-08-01 · 6 obs

○ 2018-05-13 06:24:54
● 2026-04-04 18:46:50
● 2026-06-06 07:01:36
○ 2026-06-19 15:32:44
● 2026-07-31 22:01:30
● 2026-08-01 05:30:02

○A171.244.21.832018-05-13 → 2018-05-13 · 3 obs

● 2018-05-13 06:24:54
○ 2026-04-04 18:46:50
○ 2026-08-01 05:30:02

●A172.67.182.1172026-04-04 → 2026-08-01 · 6 obs

○ 2018-05-13 06:24:54
● 2026-04-04 18:46:50
● 2026-06-06 07:01:36
○ 2026-06-19 15:32:44
● 2026-07-31 22:01:30
● 2026-08-01 05:30:02

○A188.114.96.02026-06-19 → 2026-06-19 · 4 obs

○ 2026-06-06 07:01:36
● 2026-06-19 15:32:44
○ 2026-07-31 22:01:30
○ 2026-08-01 05:30:02

○A188.114.97.02026-06-19 → 2026-06-19 · 4 obs

○ 2026-06-06 07:01:36
● 2026-06-19 15:32:44
○ 2026-07-31 22:01:30
○ 2026-08-01 05:30:02

●A2606:4700:3032::6815:3bbe2026-07-31 → 2026-08-01 · 3 obs

○ 2026-06-19 15:32:44
● 2026-07-31 22:01:30
● 2026-08-01 05:30:02

○A2606:4700:3035::ac43:b6752026-04-04 → 2026-06-06 · 5 obs

○ 2018-05-13 06:24:54
● 2026-04-04 18:46:50
● 2026-06-06 07:01:36
○ 2026-06-19 15:32:44
○ 2026-08-01 05:30:02

○A2606:4700:3037::6815:3bbe2026-04-04 → 2026-06-06 · 5 obs

○ 2018-05-13 06:24:54
● 2026-04-04 18:46:50
● 2026-06-06 07:01:36
○ 2026-06-19 15:32:44
○ 2026-08-01 05:30:02

●A2606:4700:3037::ac43:b6752026-07-31 → 2026-08-01 · 3 obs

○ 2026-06-19 15:32:44
● 2026-07-31 22:01:30
● 2026-08-01 05:30:02

○A2a06:98c1:3120::2026-06-19 → 2026-06-19 · 4 obs

○ 2026-06-06 07:01:36
● 2026-06-19 15:32:44
○ 2026-07-31 22:01:30
○ 2026-08-01 05:30:02

○A2a06:98c1:3121::2026-06-19 → 2026-06-19 · 4 obs

○ 2026-06-06 07:01:36
● 2026-06-19 15:32:44
○ 2026-07-31 22:01:30
○ 2026-08-01 05:30:02

○A54.37.159.452026-04-04 → 2026-08-01 · 2 obs

○ 2026-04-04 18:46:50
○ 2026-08-01 05:30:02

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	m.gtld-servers.net, k.gtld-servers.net, b.gtld-servers.net, f.gtld-servers.net...	-
crypto-war.net	ken.ns.cloudflare.com, pearl.ns.cloudflare.com	-

✅ Authoritative Response

Server:108.162.193.127

NS records: ken.ns.cloudflare.com, pearl.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for crypto-war.net (unsigned zone)

⏱️ Timing

Total: 416ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`172.67.182.117, 104.21.59.190`
AAAA	2	`2606:4700:3037::ac43:b675, 2606:4700:3032::6815:3bbe`
NS	2	`ken.ns.cloudflare.com, pearl.ns.cloudflare.com`
MX	3	`route2.mx.cloudflare.net (pri: 55), route3.mx.cloudflare.net (pri: 75)...`
TXT	1	`v=spf1 include:_spf.mx.cloudflare.net ~a`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`ken.ns.cloudflare.com dns.cloudflare.com`

Analysis

IP Addresses

crypto-war.net points to the four IP addresses 104.21.59.190, 172.67.182.117, 2606:4700:3032::6815:3bbe and 2606:4700:3037::ac43:b675.

Among the host names that share IP numbers with crypto-war.net are heyankara.com, gurstet.pro, gportals.com and two others.

Name Servers

Two name servers handle the delegation for crypto-war.net: ken.ns.cloudflare.com and pearl.ns.cloudflare.com.

crypto-war.net has the same name server delegation as a number of other domains, such as v2up.com, michaelenglish.es, difoolou.net and two more.

At least some of crypto-war.net's name servers are shared with other domains, for example healthvery.com, vegra.ro, 57.95.23.in-addr.arpa and two more.

It is common for these name servers to be used in conjunction with the name servers lisa.ns.cloudflare.com, ns1.colocrossing.com and ns2.colocrossing.com.

Host names resolving to 6 IP numbers:

ken.ns.cloudflare.com resolves to 108.162.193.127, 172.64.33.127 and 173.245.59.127 among others, with 3 other IP addresses in total.

pearl.ns.cloudflare.com resolves to 108.162.194.140, 162.159.38.140 and 172.64.34.140 among others, with 3 other IP addresses in total.

Mail Servers

The MX records for crypto-war.net list three mail servers: route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

crypto-war.net shares at least some of its mail servers with other domains — for example gamewinexch.in, onescene.com, sudo-self.com and two more.

Host names resolving to 6 IP numbers:

route1.mx.cloudflare.net resolves to 162.159.205.11, 162.159.205.12 and 162.159.205.13 among others, with 3 other IP addresses in total.

route2.mx.cloudflare.net resolves to 162.159.205.17, 162.159.205.18 and 162.159.205.19 among others, with 3 other IP addresses in total.

route3.mx.cloudflare.net resolves to 162.159.205.23, 162.159.205.24 and 162.159.205.25 among others, with 3 other IP addresses in total.

crypto-war.net - robtex.com

crypto-war.net

net

Same first word

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

Analysis

IP Addresses

Name Servers

Mail Servers

`crypto-war.net`

`net`