🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`letsgetblazed.blog`

DNSSEC	⚠️ Not signed
A	2606:4700:3032::ac43:d97d^{🇺🇸 Cloudflare2606:4700:3032::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3034::6815:3e07^{🇺🇸 Cloudflare2606:4700:3034::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.62.7^{Cloudflare104.21.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.217.125^{🇺🇸 Cloudflare172.67.208.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`camilo.ns.cloudflare.com` ⭐
		A	2606:4700:58::a29f:2c76^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`camilo.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c376^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`camilo.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2376^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`camilo.ns.cloudflare.com`
		A	108.162.195.118^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`camilo.ns.cloudflare.com`
		A	162.159.44.118^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`camilo.ns.cloudflare.com`
		A	172.64.35.118^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`camilo.ns.cloudflare.com`
NS	`sue.ns.cloudflare.com`
		A	2606:4700:50::adf5:3a91^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`sue.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c091^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`sue.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2091^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`sue.ns.cloudflare.com`
		A	108.162.192.145^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`sue.ns.cloudflare.com`
		A	172.64.32.145^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`sue.ns.cloudflare.com`
		A	173.245.58.145^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`sue.ns.cloudflare.com`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.62.7, 172.67.217.125
		IPv6 hints	2606:4700:3032::ac43:d97d, 2606:4700:3034::6815:3e07
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=21, name=cloudflare-ech.com
SOA	`camilo.ns.cloudflare.com`dns@cloudflare.com serial=2415219858

`blog`

	DNSSEC	🔒 Signed (DS record present)
	NS	`prd-fzp-07.corp.cira.ca` ⭐
	NS	`a.ns.nic.blog`
	NS	`b.ns.nic.blog`
	NS	`c.ns.nic.blog`
	NS	`d.ns.nic.blog`
	SOA	`prd-fzp-07.corp.cira.ca`admin-dns@cira.ca serial=2610121435

Same first word

letsgetblazed.blog

letsgetblazed.net

letsgetblazed.info

letsgetblazed.shop

Previous names

Next names

DNS History

6 records (6 active, 0 former)

●NScamilo.ns.cloudflare.com2026-08-18 → 2026-10-12 · 2 obs

● 2026-08-18 06:23:38
● 2026-10-12 14:41:16

●NSsue.ns.cloudflare.com2026-08-18 → 2026-10-12 · 2 obs

● 2026-08-18 06:23:38
● 2026-10-12 14:41:16

●A104.21.62.72026-08-18 → 2026-10-12 · 2 obs

● 2026-08-18 06:23:38
● 2026-10-12 14:41:16

●A172.67.217.1252026-08-18 → 2026-10-12 · 2 obs

● 2026-08-18 06:23:38
● 2026-10-12 14:41:16

●A2606:4700:3032::ac43:d97d2026-08-18 → 2026-10-12 · 2 obs

● 2026-08-18 06:23:38
● 2026-10-12 14:41:16

●A2606:4700:3034::6815:3e072026-08-18 → 2026-10-12 · 2 obs

● 2026-08-18 06:23:38
● 2026-10-12 14:41:16

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
blog	a.ns.nic.blog, b.ns.nic.blog, c.ns.nic.blog, d.ns.nic.blog	8 records
letsgetblazed.blog	sue.ns.cloudflare.com, camilo.ns.cloudflare.com	-

✅ Authoritative Response

Server:108.162.195.118

NS records: sue.ns.cloudflare.com, camilo.ns.cloudflare.com

🔒 DNSSEC Status

❌ Bogus (DNSSEC validation failed)

Validation error at blog: Error: DNS query timeout: 185.159.197.9 for DNSKEY blog

⏱️ Timing

Total: 4266ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.62.7, 172.67.217.125`
AAAA	2	`2606:4700:3032::ac43:d97d, 2606:4700:3034::6815:3e07`
NS	2	`camilo.ns.cloudflare.com, sue.ns.cloudflare.com`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`camilo.ns.cloudflare.com dns.cloudflare.`

📌 Glue Records Collected

Total: 8

In-bailiwick: 8 (a.ns.nic.blog, a.ns.nic.blog, b.ns.nic.blog...)

Analysis

IP Addresses

letsgetblazed.blog has four IP addresses: 104.21.62.7, 172.67.217.125, 2606:4700:3032::ac43:d97d and 2606:4700:3034::6815:3e07.

Among the host names that share IP numbers with letsgetblazed.blog are ttoqvluihdcbr.site, islandwater.ru, gasamed.cl and two others.

Name Servers

letsgetblazed.blog is served by two delegated name servers, camilo.ns.cloudflare.com and sue.ns.cloudflare.com.

letsgetblazed.blog has the same name server delegation as a number of other domains, such as kivvi-cosmetics.com, olainpharm.info, jitendrkumararya0.workers.dev and two more.

letsgetblazed.blog shares at least some of its name servers with other domains, including usbuygold.com, to-kenp1zk7jt.info, fileteam.ru and two others.

These name servers are frequently seen alongside the name servers nile.ns.cloudflare.com, sasha.ns.cloudflare.com, tegan.ns.cloudflare.com and brianna.ns.cloudflare.com.

Host names resolving to 6 IP numbers:

camilo.ns.cloudflare.com carries IP addresses 108.162.195.118, 162.159.44.118 and 172.64.35.118, with 3 other addresses beyond those.

sue.ns.cloudflare.com carries IP addresses 108.162.192.145, 172.64.32.145 and 173.245.58.145, with 3 other addresses beyond those.

letsgetblazed.blog - robtex.com