🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`proloopgroup.com`

DNSSEC	⚠️ Not signed
A	100.63.128.113^{🇺🇸 Amazon100.48.0.0/12 EC2 IAD prefix}
		PTR	`ec2-100-63-128-113.compute-1.amazonaws.com`
NS	`ns-cloud-b1.googledomains.com` ⭐
		A	2001:4860:4802:32::6b^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-b1.googledomains.com`
		A	216.239.32.107^{🇺🇸 Google216.239.32.0/24}
			PTR	`ns-cloud-b1.googledomains.com`
NS	`ns-cloud-b2.googledomains.com`
		A	2001:4860:4802:34::6b^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-b2.googledomains.com`
		A	216.239.34.107^{🇺🇸 Google216.239.34.0/24}
			PTR	`ns-cloud-b2.googledomains.com`
NS	`ns-cloud-b3.googledomains.com`
		A	2001:4860:4802:36::6b^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-b3.googledomains.com`
		A	216.239.36.107^{🇺🇸 Google216.239.36.0/24}
			PTR	`ns-cloud-b3.googledomains.com`
NS	`ns-cloud-b4.googledomains.com`
		A	2001:4860:4802:38::6b^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-b4.googledomains.com`
		A	216.239.38.107^{🇺🇸 Google216.239.38.0/24}
			PTR	`ns-cloud-b4.googledomains.com`
MX	`smtp.google.com` ⭐
		A	2607:f8b0:4023:2009::1a^{🇺🇸 Google2607:f8b0::/32}
			PTR	`yuphxer-in-f26.1e100.net`
		A	2607:f8b0:4023:2009::1b^{🇺🇸 Google2607:f8b0::/32}
			PTR	`yuphxer-in-f27.1e100.net`
		A	2607:f8b0:4023:200b::1a^{🇺🇸 Google2607:f8b0::/32}
			PTR	`yuphxej-in-f26.1e100.net`
		A	2607:f8b0:4023:200b::1b^{🇺🇸 Google2607:f8b0::/32}
			PTR	`yuphxej-in-f27.1e100.net`
		A	172.217.75.26^{🇺🇸 Google172.217.75.0/24}
			PTR	`yuphxej-in-f26.1e100.net`
		A	172.217.75.27^{🇺🇸 Google172.217.75.0/24}
			PTR	`yuphxej-in-f27.1e100.net`
		A	192.178.164.27^{🇺🇸 Google192.178.164.0/24}
			PTR	`yuphxer-in-f27.1e100.net`
		A	192.178.231.26^{🇺🇸 Google192.178.0.0/15}
			PTR	`yuphxrp-in-f26.1e100.net`
		A	192.178.231.27^{🇺🇸 Google192.178.0.0/15}
			PTR	`yuphxrp-in-f27.1e100.net`
TXT	`v=spf1 include:_spf.google.com ~all`
TXT	`google-site-verification=oqbuC03rPTliFcgG3VDxuy525zjBlOYS3PTZOViKulM`
SOA	`ns-cloud-b1.googledomains.com`cloud-dns-hostmaster@google.com serial=1

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

Same first word

proloopgroup.com

Previous names

Next names

DNS History

8 records (6 active, 2 former)

●NSns-cloud-b1.googledomains.com2026-08-26 → 2026-11-15 · 2 obs

● 2026-08-26 06:10:08
● 2026-11-15 23:06:58

●NSns-cloud-b2.googledomains.com2026-08-26 → 2026-11-15 · 2 obs

● 2026-08-26 06:10:08
● 2026-11-15 23:06:58

●NSns-cloud-b3.googledomains.com2026-08-26 → 2026-11-15 · 2 obs

● 2026-08-26 06:10:08
● 2026-11-15 23:06:58

●NSns-cloud-b4.googledomains.com2026-08-26 → 2026-11-15 · 2 obs

● 2026-08-26 06:10:08
● 2026-11-15 23:06:58

●MXsmtp.google.com2026-08-26 → 2026-11-15 · 2 obs

● 2026-08-26 06:10:08
● 2026-11-15 23:06:58

●A100.63.128.1132026-11-15 → 2026-11-15 · 3 obs

○ 2026-10-08 21:17:30
● 2026-11-15 22:41:56
● 2026-11-15 23:06:58

○A32.196.154.1872026-10-08 → 2026-10-08 · 4 obs

○ 2026-08-26 06:10:08
● 2026-10-08 21:17:30
○ 2026-11-15 22:41:56
○ 2026-11-15 23:06:58

○A52.15.49.972026-08-26 → 2026-08-26 · 3 obs

● 2026-08-26 06:10:08
○ 2026-10-08 21:17:30
○ 2026-11-15 23:06:58

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	f.gtld-servers.net, c.gtld-servers.net, i.gtld-servers.net, a.gtld-servers.net...	-
proloopgroup.com	ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com	8 records

✅ Authoritative Response

Server:216.239.32.107

NS records: ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

Root DNSKEY fetch failed: Error: connect EADDRNOTAVAIL 198.41.0.4:53 - Local (0.0.0.0:0)

⏱️ Timing

Total: 386ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`100.63.128.113`
NS	4	`ns-cloud-b4.googledomains.com, ns-cloud-b2.googledomains.com...`
MX	1	`smtp.google.com (pri: 1)`
TXT	2	`google-site-verification=oqbuC03rPTliFcg, v=spf1 include:_spf.google.com ~all`
SOA	1	`ns-cloud-b1.googledomains.com cloud-dns-`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns-cloud-b1.googledomains.com, ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com...)

Analysis

IP Addresses

proloopgroup.com points to a single IP number: 100.63.128.113.

Additional host names — coveragexs.info, inboxcoveragextech.live, blumecontentflow.com and two others — share IP numbers with proloopgroup.com.

Name Servers

proloopgroup.com has four authoritative name servers: ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com and ns-cloud-b4.googledomains.com.

There is at least partial name server overlap between proloopgroup.com and other domains — mermaidcoveco.com, greenewrks.co, wolferlaw.com and two more among them.

All four hostnames — ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com and ns-cloud-b4.googledomains.com — resolve to two IP numbers apiece: ns-cloud-b1.googledomains.com to 216.239.32.107 and 2001:4860:4802:32::6b; ns-cloud-b2.googledomains.com to 216.239.34.107 and 2001:4860:4802:34::6b; ns-cloud-b3.googledomains.com to 216.239.36.107 and 2001:4860:4802:36::6b; ns-cloud-b4.googledomains.com to 216.239.38.107 and 2001:4860:4802:38::6b.

Mail Servers

proloopgroup.com has one mail server: smtp.google.com.

proloopgroup.com shares the same mail server setup as other domains, including alvaessenciasoficial.com.br, bronti-capital.com, apexopsystem.com and two others.

Some mail servers of proloopgroup.com are also used by other domains, notably iamnz.org.nz and desteknt.com.

smtp.google.com points to 9 IP numbers: 172.217.75.26, 172.217.75.27, 192.178.164.27 and 6 other.

proloopgroup.com - robtex.com