callingcommand.com - robtex.com

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

callingcommand.com

com

Same first word

Previous names

Next names

DNS History

5 records (5 active, 0 former)

NSns-cloud-a1.googledomains.comns-cloud-a2.googledomains.comns-cloud-a3.googledomains.comns-cloud-a4.googledomains.comA103.169.142.0
●NSns-cloud-a1.googledomains.com2026-08-29 → 2026-11-07 · 2 obs
● 2026-08-29 21:57:32
● 2026-11-07 03:41:48
●NSns-cloud-a2.googledomains.com2026-08-29 → 2026-11-07 · 2 obs
● 2026-08-29 21:57:32
● 2026-11-07 03:41:48
●NSns-cloud-a3.googledomains.com2026-08-29 → 2026-11-07 · 2 obs
● 2026-08-29 21:57:32
● 2026-11-07 03:41:48
●NSns-cloud-a4.googledomains.com2026-08-29 → 2026-11-07 · 2 obs
● 2026-08-29 21:57:32
● 2026-11-07 03:41:48
●A103.169.142.02026-08-29 → 2026-11-07 · 2 obs
● 2026-08-29 21:57:32
● 2026-11-07 03:41:48

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
callingcommand.comns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com8 records

✅ Authoritative Response

Server:216.239.38.106

NS records: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for callingcommand.com (unsigned zone)

⏱️ Timing

Total: 246ms | Queries: -

📄 Records

TypeCountSample Data
A1103.169.142.0
NS4ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com...
TXT2canva-domain-verify=f6f21802-830e-4dc6-9, v=spf1 -all
SOA1ns-cloud-a1.googledomains.com cloud-dns-

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns-cloud-a1.googledomains.com, ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com...)

Analysis

IP Addresses

callingcommand.com points to a single IP number: 103.169.142.0.

Additional host names — unifiedhealingandco.com.au, albapujolcamins.com, bloombirthsupport.com and two others — share IP numbers with callingcommand.com.

Name Servers

callingcommand.com has four authoritative name servers: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com and ns-cloud-a4.googledomains.com.

The name servers of callingcommand.com overlap at least partially with those of other domains — among them danvillepride.com, riderr.io, stillwindbodywork.com and two more.

These name servers commonly appear alongside the name servers ns1.mirusresearch.com and ns2.mir.us.

Each of the four hosts ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com and ns-cloud-a4.googledomains.com has two IP addresses. ns-cloud-a1.googledomains.com points to 216.239.32.106 and 2001:4860:4802:32::6a. ns-cloud-a2.googledomains.com points to 216.239.34.106 and 2001:4860:4802:34::6a. ns-cloud-a3.googledomains.com points to 216.239.36.106 and 2001:4860:4802:36::6a. ns-cloud-a4.googledomains.com points to 216.239.38.106 and 2001:4860:4802:38::6a.