🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`criptobuzz.com`

DNSSEC	🔒 Signed (DS record present)
A	44.224.45.103^{🇺🇸 Amazon44.224.0.0/11 EC2 PDX prefix}
		PTR	`ec2-44-224-45-103.us-west-2.compute.amazonaws.com`
NS	`ns-cloud-c1.googledomains.com` ⭐
		A	2001:4860:4802:32::6c^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-c1.googledomains.com`
		A	216.239.32.108^{🇺🇸 Google216.239.32.0/24}
			PTR	`ns-cloud-c1.googledomains.com`
NS	`ns-cloud-c2.googledomains.com`
		A	2001:4860:4802:34::6c^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-c2.googledomains.com`
		A	216.239.34.108^{🇺🇸 Google216.239.34.0/24}
			PTR	`ns-cloud-c2.googledomains.com`
NS	`ns-cloud-c3.googledomains.com`
		A	2001:4860:4802:36::6c^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-c3.googledomains.com`
		A	216.239.36.108^{🇺🇸 Google216.239.36.0/24}
			PTR	`ns-cloud-c3.googledomains.com`
NS	`ns-cloud-c4.googledomains.com`
		A	2001:4860:4802:38::6c^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-c4.googledomains.com`
		A	216.239.38.108^{🇺🇸 Google216.239.38.0/24}
			PTR	`ns-cloud-c4.googledomains.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c08::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bi-in-f27.1e100.net`
		A	142.250.31.27^{🇺🇸 Google142.250.31.0/24}
			PTR	`bj-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c14::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.26^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1a^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f26.1e100.net`
		A	192.178.223.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f26.1e100.net`
		A	172.253.157.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
TXT	`v=spf1 +a +mx +ip4:35.203.64.202 include:_spf.google.com ~all`
SOA	`ns-cloud-c1.googledomains.com`cloud-dns-hostmaster@google.com serial=24

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

Same first word

criptobuzz.com

Previous names

Next names

DNS History

20 records (10 active, 10 former)

●NSns-cloud-c1.googledomains.com2026-08-17 → 2026-08-28 · 3 obs

○ 2018-01-24 18:56:58
● 2026-08-17 09:28:50
● 2026-08-28 10:12:04

●NSns-cloud-c2.googledomains.com2026-08-17 → 2026-08-28 · 3 obs

○ 2018-01-24 18:56:58
● 2026-08-17 09:28:50
● 2026-08-28 10:12:04

●NSns-cloud-c3.googledomains.com2026-08-17 → 2026-08-28 · 3 obs

○ 2018-01-24 18:56:58
● 2026-08-17 09:28:50
● 2026-08-28 10:12:04

●NSns-cloud-c4.googledomains.com2026-08-17 → 2026-08-28 · 3 obs

○ 2018-01-24 18:56:58
● 2026-08-17 09:28:50
● 2026-08-28 10:12:04

○NSns39.domaincontrol.com2018-01-24 → 2018-01-24 · 3 obs

● 2018-01-24 18:56:58
○ 2026-08-17 09:28:50
○ 2026-08-28 10:12:04

○NSns40.domaincontrol.com2018-01-24 → 2018-01-24 · 3 obs

● 2018-01-24 18:56:58
○ 2026-08-17 09:28:50
○ 2026-08-28 10:12:04

●MXalt1.aspmx.l.google.com2026-08-17 → 2026-08-28 · 2 obs

● 2026-08-17 09:28:50
● 2026-08-28 10:12:04

●MXalt2.aspmx.l.google.com2026-08-17 → 2026-08-28 · 2 obs

● 2026-08-17 09:28:50
● 2026-08-28 10:12:04

●MXalt3.aspmx.l.google.com2026-08-17 → 2026-08-28 · 2 obs

● 2026-08-17 09:28:50
● 2026-08-28 10:12:04

●MXalt4.aspmx.l.google.com2026-08-17 → 2026-08-28 · 2 obs

● 2026-08-17 09:28:50
● 2026-08-28 10:12:04

●MXaspmx.l.google.com2026-08-17 → 2026-08-28 · 2 obs

● 2026-08-17 09:28:50
● 2026-08-28 10:12:04

○A184.168.221.342018-01-24 → 2018-01-24 · 3 obs

● 2018-01-24 18:56:58
○ 2026-08-17 09:28:50
○ 2026-08-28 10:12:04

○A184.168.221.372018-01-24 → 2018-01-24 · 3 obs

● 2018-01-24 18:56:58
○ 2026-08-17 09:28:50
○ 2026-08-28 10:12:04

○A184.168.221.432018-01-24 → 2018-01-24 · 3 obs

● 2018-01-24 18:56:58
○ 2026-08-17 09:28:50
○ 2026-08-28 10:12:04

○A184.168.221.532018-01-24 → 2018-01-24 · 3 obs

● 2018-01-24 18:56:58
○ 2026-08-17 09:28:50
○ 2026-08-28 10:12:04

○A184.168.221.582018-01-24 → 2018-01-24 · 3 obs

● 2018-01-24 18:56:58
○ 2026-08-17 09:28:50
○ 2026-08-28 10:12:04

●A44.224.45.1032026-08-17 → 2026-08-28 · 3 obs

○ 2018-01-24 18:56:58
● 2026-08-17 09:28:50
● 2026-08-28 10:12:04

○A50.63.202.462018-01-24 → 2018-01-24 · 3 obs

● 2018-01-24 18:56:58
○ 2026-08-17 09:28:50
○ 2026-08-28 10:12:04

○A50.63.202.572018-01-24 → 2018-01-24 · 3 obs

● 2018-01-24 18:56:58
○ 2026-08-17 09:28:50
○ 2026-08-28 10:12:04

○A50.63.202.602018-01-24 → 2018-01-24 · 3 obs

● 2018-01-24 18:56:58
○ 2026-08-17 09:28:50
○ 2026-08-28 10:12:04

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
criptobuzz.com	ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com	8 records

✅ Authoritative Response

Server:216.239.36.108

NS records: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com

🔒 DNSSEC Status

🔐 Secure (DNSSEC validated)

Chain of trust verified from root to domain

⏱️ Timing

Total: 631ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`44.224.45.103`
NS	4	`ns-cloud-c1.googledomains.com, ns-cloud-c3.googledomains.com...`
MX	5	`alt1.aspmx.l.google.com (pri: 5), alt2.aspmx.l.google.com (pri: 5)...`
TXT	1	`v=spf1 +a +mx +ip4:35.203.64.202 include`
SOA	1	`ns-cloud-c1.googledomains.com cloud-dns-`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns-cloud-c1.googledomains.com, ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com...)

Analysis

IP Addresses

criptobuzz.com resolves to just one IP address, 44.224.45.103.

Name Servers

The NS records for criptobuzz.com point to four name servers: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com and ns-cloud-c4.googledomains.com.

There is at least partial name server overlap between criptobuzz.com and other domains — trybiopaw.com, tecnoempleo.us, naplesvirtualoffice.com and two more among them.

All four hostnames — ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com and ns-cloud-c4.googledomains.com — resolve to two IP numbers apiece: ns-cloud-c1.googledomains.com to 216.239.32.108 and 2001:4860:4802:32::6c; ns-cloud-c2.googledomains.com to 216.239.34.108 and 2001:4860:4802:34::6c; ns-cloud-c3.googledomains.com to 216.239.36.108 and 2001:4860:4802:36::6c; ns-cloud-c4.googledomains.com to 216.239.38.108 and 2001:4860:4802:38::6c.

Mail Servers

Five mail servers handle criptobuzz.com: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

There is at least a partial MX overlap between criptobuzz.com and other domains, including viewadam.com, bridgegraphy.org, lakesidekitchendesign.com and two others.

alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com are mail servers that frequently appear together with these mail servers.

Host names that have two IP addresses:

aspmx.l.google.com directs traffic to 142.250.31.27 and 2607:f8b0:4004:c08::1b.

alt1.aspmx.l.google.com directs traffic to 192.178.234.26 and 2800:3f0:4003:c14::1a.

alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1b.

alt3.aspmx.l.google.com directs traffic to 192.178.223.27 and 2a00:1450:4009:c0f::1a.

alt4.aspmx.l.google.com directs traffic to 172.253.157.27 and 2a00:1450:400c:c23::1a.