`blazing-cloud.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3030::6815:5221^{🇺🇸 Cloudflare2606:4700:3030::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3031::ac43:97cc^{🇺🇸 Cloudflare2606:4700:3031::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.82.33^{Cloudflare104.21.80.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.151.204^{🇺🇸 Cloudflare172.67.144.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`journey.ns.cloudflare.com` ⭐
		A	2606:4700:50::a29f:2603^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`journey.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c203^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`journey.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2203^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`journey.ns.cloudflare.com`
		A	108.162.194.3^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`journey.ns.cloudflare.com`
		A	162.159.38.3^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`journey.ns.cloudflare.com`
		A	172.64.34.3^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`journey.ns.cloudflare.com`
NS	`ryan.ns.cloudflare.com`
		A	2606:4700:58::a29f:2ce5^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ryan.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c3e5^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`ryan.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:23e5^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`ryan.ns.cloudflare.com`
		A	108.162.195.229^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ryan.ns.cloudflare.com`
		A	162.159.44.229^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ryan.ns.cloudflare.com`
		A	172.64.35.229^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ryan.ns.cloudflare.com`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.82.33, 172.67.151.204
		IPv6 hints	2606:4700:3030::6815:5221, 2606:4700:3031::ac43:97cc
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=211, name=cloudflare-ech.com
SOA	`journey.ns.cloudflare.com`dns@cloudflare.com serial=2397731946

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

⚠️ On DNS blocklist: tif

Subdomains

cloudflare.blazing-cloud.com

Same first word

blazing-cloud.com

DNS History

6 records (6 active, 0 former)

●NSjourney.ns.cloudflare.com2026-03-11 → 2026-04-12 · 2 obs

● 2026-03-11 00:48:08
● 2026-04-12 09:10:12

●NSryan.ns.cloudflare.com2026-03-11 → 2026-04-12 · 2 obs

● 2026-03-11 00:48:08
● 2026-04-12 09:10:12

●A104.21.82.332026-03-11 → 2026-04-12 · 2 obs

● 2026-03-11 00:48:08
● 2026-04-12 09:10:12

●A172.67.151.2042026-03-11 → 2026-04-12 · 2 obs

● 2026-03-11 00:48:08
● 2026-04-12 09:10:12

●A2606:4700:3030::6815:52212026-03-11 → 2026-04-12 · 2 obs

● 2026-03-11 00:48:08
● 2026-04-12 09:10:12

●A2606:4700:3031::ac43:97cc2026-03-11 → 2026-04-12 · 2 obs

● 2026-03-11 00:48:08
● 2026-04-12 09:10:12

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, k.gtld-servers.net, f.gtld-servers.net, i.gtld-servers.net...	-
blazing-cloud.com	journey.ns.cloudflare.com, ryan.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.195.229

NS records: journey.ns.cloudflare.com, ryan.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for blazing-cloud.com (unsigned zone)

⏱️ Timing

Total: 271ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.82.33, 172.67.151.204`
AAAA	2	`2606:4700:3031::ac43:97cc, 2606:4700:3030::6815:5221`
NS	2	`journey.ns.cloudflare.com, ryan.ns.cloudflare.com`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`journey.ns.cloudflare.com dns.cloudflare`

📌 Glue Records Collected

Total: 12

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

Analysis

Hierarchy

The parent of cloudflare.blazing-cloud.com is blazing-cloud.com.

IP Addresses

blazing-cloud.com maps to four IP numbers: 2606:4700:3030::6815:5221, 2606:4700:3031::ac43:97cc, 104.21.82.33 and 172.67.151.204.

Other host names such as share.timsach.vn, www.darrinward.com, office.timsach.vn, pb553.com and 4004.ir share IPs with blazing-cloud.com.

Name Servers

Two name servers journey.ns.cloudflare.com and ryan.ns.cloudflare.com handle the delegation for blazing-cloud.com.

blazing-cloud.com shares the same name server setup as other domains, for example kriper.ru, howli.gg, kurdsat.tv, leelalab.it and kurdsatnews.com.

blazing-cloud.com at least partially shares name servers with other domains, for example fideligift.com, bodytech.it, zbtzhb.com, salentolibri.it and lucidus.hr.

These name servers are often used with evelyn.ns.cloudflare.com, anita.ns.cloudflare.com, adam.ns.cloudflare.com, amanda.ns.cloudflare.com and brynne.ns.cloudflare.com.

Host names with six IP numbers:

journey.ns.cloudflare.com points to 2606:4700:50::a29f:2603, 2803:f800:50::6ca2:c203, 2a06:98c1:50::ac40:2203, 108.162.194.3, 162.159.38.3 and 172.64.34.3.

ryan.ns.cloudflare.com points to 2606:4700:58::a29f:2ce5, 2803:f800:50::6ca2:c3e5, 2a06:98c1:50::ac40:23e5, 108.162.195.229, 162.159.44.229 and 172.64.35.229.

blazing-cloud.com - robtex.com