flamechannel.com - dns.ninja

`flamechannel.com`

DNSSEC	⚠️ Not signed
A	23.111.84.4^{🇳🇱 SERVERS23.111.84.0/24 .COM NL01 SPECIFIC}
A	23.111.84.116^{🇳🇱 SERVERS23.111.84.0/24 .COM NL01 SPECIFIC}
A	23.111.84.124^{🇳🇱 SERVERS23.111.84.0/24 .COM NL01 SPECIFIC}
A	23.111.84.220^{🇳🇱 SERVERS23.111.84.0/24 .COM NL01 SPECIFIC}
A	23.111.84.228^{🇳🇱 SERVERS23.111.84.0/24 .COM NL01 SPECIFIC}
A	172.240.108.68^{🇺🇸 SERVERS172.240.108.0/24 .COM US WAS1}
A	172.240.108.76^{🇺🇸 SERVERS172.240.108.0/24 .COM US WAS1}
A	172.240.108.84^{🇺🇸 SERVERS172.240.108.0/24 .COM US WAS1}
A	172.240.127.234^{🇺🇸 SERVERS172.240.127.0/24 .COM WAS1}
A	172.240.127.242^{🇺🇸 SERVERS172.240.127.0/24 .COM WAS1}
A	172.240.127.243^{🇺🇸 SERVERS172.240.127.0/24 .COM WAS1}
A	172.240.127.244^{🇺🇸 SERVERS172.240.127.0/24 .COM WAS1}
A	172.240.253.132^{🇺🇸 SERVERS172.240.253.0/24 .COM WAS1}
A	172.255.141.4^{🇳🇱 SERVERS172.255.141.0/24 .COM AMS3}
NS	`ns1.publicdnsservice.com` ⭐
		A	52.223.51.231^{🇺🇸 Amazon52.223.48.0/20}
			PTR	`aa378b12f9b002b84.awsglobalaccelerator.com`
NS	`ns2.publicdnsservice.com`
		A	99.83.185.193^{🇺🇸 Amazon99.83.176.0/20}
			PTR	`aa378b12f9b002b84.awsglobalaccelerator.com`
SOA	`ns1.publicdnsservice.com`hostmaster@flamechannel.com 2026-07-15 #4

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

⚠️ On DNS blocklist: light, multi, pro, pro.mini, pro.plus, pro.plus.mini, ultimate, ultimate.mini
📈 Tranco rank: #955,707

Subdomains

www.flamechannel.com

Same first word

flamechannel.co.uk

flamechannel.com

Similar names

channelflame.co.uk

DNS History

19 records (16 active, 3 former)

●NSns1.publicdnsservice.com2026-05-22 → 2026-08-14 · 3 obs

○ 2017-09-10 10:52:32
● 2026-05-22 08:16:36
● 2026-08-14 19:03:44

●NSns2.publicdnsservice.com2026-05-22 → 2026-08-14 · 3 obs

○ 2017-09-10 10:52:32
● 2026-05-22 08:16:36
● 2026-08-14 19:03:44

○NSns33.domaincontrol.com2017-09-10 → 2017-09-10 · 3 obs

● 2017-09-10 10:52:32
○ 2026-05-22 08:16:36
○ 2026-08-14 19:03:44

○NSns34.domaincontrol.com2017-09-10 → 2017-09-10 · 3 obs

● 2017-09-10 10:52:32
○ 2026-05-22 08:16:36
○ 2026-08-14 19:03:44

●A172.240.108.682026-05-22 → 2026-08-14 · 3 obs

○ 2017-09-10 10:52:32
● 2026-05-22 08:16:36
● 2026-08-14 19:03:44

●A172.240.108.762026-05-22 → 2026-08-14 · 3 obs

○ 2017-09-10 10:52:32
● 2026-05-22 08:16:36
● 2026-08-14 19:03:44

●A172.240.108.842026-05-22 → 2026-08-14 · 3 obs

○ 2017-09-10 10:52:32
● 2026-05-22 08:16:36
● 2026-08-14 19:03:44

●A172.240.127.2342026-05-22 → 2026-08-14 · 3 obs

○ 2017-09-10 10:52:32
● 2026-05-22 08:16:36
● 2026-08-14 19:03:44

●A172.240.127.2422026-05-22 → 2026-08-14 · 3 obs

○ 2017-09-10 10:52:32
● 2026-05-22 08:16:36
● 2026-08-14 19:03:44

●A172.240.127.2432026-05-22 → 2026-08-14 · 3 obs

○ 2017-09-10 10:52:32
● 2026-05-22 08:16:36
● 2026-08-14 19:03:44

●A172.240.127.2442026-05-22 → 2026-08-14 · 3 obs

○ 2017-09-10 10:52:32
● 2026-05-22 08:16:36
● 2026-08-14 19:03:44

●A172.240.253.1322026-05-22 → 2026-08-14 · 3 obs

○ 2017-09-10 10:52:32
● 2026-05-22 08:16:36
● 2026-08-14 19:03:44

●A172.255.141.42026-08-14 → 2026-08-14 · 2 obs

○ 2026-05-22 08:16:36
● 2026-08-14 19:03:44

●A23.111.84.1162026-08-14 → 2026-08-14 · 2 obs

○ 2026-05-22 08:16:36
● 2026-08-14 19:03:44

●A23.111.84.1242026-08-14 → 2026-08-14 · 2 obs

○ 2026-05-22 08:16:36
● 2026-08-14 19:03:44

●A23.111.84.2202026-08-14 → 2026-08-14 · 2 obs

○ 2026-05-22 08:16:36
● 2026-08-14 19:03:44

●A23.111.84.2282026-08-14 → 2026-08-14 · 2 obs

○ 2026-05-22 08:16:36
● 2026-08-14 19:03:44

●A23.111.84.42026-08-14 → 2026-08-14 · 2 obs

○ 2026-05-22 08:16:36
● 2026-08-14 19:03:44

○A50.63.202.542017-09-10 → 2017-09-10 · 3 obs

● 2017-09-10 10:52:32
○ 2026-05-22 08:16:36
○ 2026-08-14 19:03:44

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
flamechannel.com	ns1.publicdnsservice.com, ns2.publicdnsservice.com	2 records

✅ Authoritative Response

Server:99.83.185.193

NS records: ns1.publicdnsservice.com, ns2.publicdnsservice.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for flamechannel.com (unsigned zone)

⏱️ Timing

Total: 508ms | Queries: -

📄 Records

Type	Count	Sample Data
A	14	`23.111.84.228, 23.111.84.116...`
NS	2	`ns2.publicdnsservice.com, ns1.publicdnsservice.com`
SOA	1	`ns1.publicdnsservice.com hostmaster.flam`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.publicdnsservice.com, ns2.publicdnsservice.com)

Analysis

Hierarchy

www.flamechannel.com is a subdomain of flamechannel.com.

IP Addresses

flamechannel.com resolves to 14 IP numbers: 23.111.84.4, 23.111.84.116, 23.111.84.124 and 11 other.

Additional host names — dismissedstooped.com, flickerprobabilityset.com, margive.com and two others — share IP numbers with flamechannel.com.

Name Servers

Two name servers handle the delegation for flamechannel.com: ns1.publicdnsservice.com and ns2.publicdnsservice.com.

flamechannel.com shares its name server setup with other domains, including foxheadquarter.com, bugturkey.com, irradiateduketranslating.com and two others.

Both ns1.publicdnsservice.com and ns2.publicdnsservice.com have a single IP address each — ns1.publicdnsservice.com resolves to 52.223.51.231 while ns2.publicdnsservice.com resolves to 99.83.185.193.