callingcommand.com - dns.ninja

🛡️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-10-20 · 2 obs
● 2026-08-29 21:57:32
● 2026-10-20 08:33:46
●NSns-cloud-a2.googledomains.com2026-08-29 → 2026-10-20 · 2 obs
● 2026-08-29 21:57:32
● 2026-10-20 08:33:46
●NSns-cloud-a3.googledomains.com2026-08-29 → 2026-10-20 · 2 obs
● 2026-08-29 21:57:32
● 2026-10-20 08:33:46
●NSns-cloud-a4.googledomains.com2026-08-29 → 2026-10-20 · 2 obs
● 2026-08-29 21:57:32
● 2026-10-20 08:33:46
●A103.169.142.02026-08-29 → 2026-10-20 · 2 obs
● 2026-08-29 21:57:32
● 2026-10-20 08:33:46

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
come.gtld-servers.net, d.gtld-servers.net, a.gtld-servers.net, l.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.36.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: 504ms | Queries: -

📄 Records

TypeCountSample Data
A1103.169.142.0
NS4ns-cloud-a2.googledomains.com, ns-cloud-a4.googledomains.com...
TXT2v=spf1 -all, canva-domain-verify=f6f21802-830e-4dc6-9
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.

callingcommand.com shares at least some of its name servers with other domains, including danvillepride.com, riderr.io, stillwindbodywork.com and two others.

The host names ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com and ns-cloud-a4.googledomains.com each resolve to two IP addresses: ns-cloud-a1.googledomains.com resolves to 216.239.32.106 and 2001:4860:4802:32::6a; ns-cloud-a2.googledomains.com resolves to 216.239.34.106 and 2001:4860:4802:34::6a; ns-cloud-a3.googledomains.com resolves to 216.239.36.106 and 2001:4860:4802:36::6a; ns-cloud-a4.googledomains.com resolves to 216.239.38.106 and 2001:4860:4802:38::6a.