`ionizerflow.click`

DNSSEC	⚠️ Not signed
NS	`fatima.ns.cloudflare.com` ⚠️ Not in zone NS records
		A	2606:4700:50::a29f:26bc^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`fatima.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c2bc^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`fatima.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:22bc^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`fatima.ns.cloudflare.com`
		A	108.162.194.188^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`fatima.ns.cloudflare.com`
		A	162.159.38.188^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`fatima.ns.cloudflare.com`
		A	172.64.34.188^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`fatima.ns.cloudflare.com`
NS	`pedro.ns.cloudflare.com` ⚠️ Not in zone NS records
		A	2606:4700:58::a29f:2cb7^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`pedro.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c3b7^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`pedro.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:23b7^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`pedro.ns.cloudflare.com`
		A	108.162.195.183^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`pedro.ns.cloudflare.com`
		A	162.159.44.183^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`pedro.ns.cloudflare.com`
		A	172.64.35.183^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`pedro.ns.cloudflare.com`

`click`

	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=1785508842

⚠️ On DNS blocklist: tif

Same first word

ionizerflow.click

DNS History

4 records (2 active, 2 former)

●NSfatima.ns.cloudflare.com2026-07-25 → 2026-07-31 · 2 obs

● 2026-07-25 09:52:14
● 2026-07-31 15:02:18

●NSpedro.ns.cloudflare.com2026-07-25 → 2026-07-31 · 2 obs

● 2026-07-25 09:52:14
● 2026-07-31 15:02:18

○A2a02:4780:f:2697::12026-07-25 → 2026-07-25 · 3 obs

● 2026-07-25 09:52:14
○ 2026-07-31 15:02:16
○ 2026-07-31 15:02:18

○A46.202.140.2262026-07-25 → 2026-07-25 · 3 obs

● 2026-07-25 09:52:14
○ 2026-07-31 15:02:16
○ 2026-07-31 15:02:18

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
click	ns01.trs-dns.net, ns10.trs-dns.org, ns10.trs-dns.info, ns01.trs-dns.com	-
ionizerflow.click	pedro.ns.cloudflare.com, fatima.ns.cloudflare.com	-

✅ Authoritative Response

Server:108.162.194.188

NS records: pedro.ns.cloudflare.com, fatima.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for ionizerflow.click (unsigned zone)

⏱️ Timing

Total: 371ms | Queries: -

📄 Records

Type	Count	Sample Data

Analysis

Name Servers

ionizerflow.click is delegated to two name servers: fatima.ns.cloudflare.com and pedro.ns.cloudflare.com.

ionizerflow.click shares its NS records with other domains, for example echelonprimeoperations.digital, cercalco.click, chanduyra.click and two others.

The name servers of ionizerflow.click overlap at least partially with those of other domains — among them idrslot.cc, sameday.bg, therecord.co.nz and two more.

These name servers commonly appear in combination with the name servers fred.ns.cloudflare.com.

DNS names with 6 IP addresses:

fatima.ns.cloudflare.com resolves to 108.162.194.188, 162.159.38.188, 172.64.34.188 and 3 other IP addresses.

pedro.ns.cloudflare.com resolves to 108.162.195.183, 162.159.44.183, 172.64.35.183 and 3 other IP addresses.

ionizerflow.click - robtex.com