digitalcommandcloud.org - dns.ninja

πŸ›‘οΈDomain Reputation CheckBlocklist, phishing & malware statusβ†’

digitalcommandcloud.org

DNSSEC⚠️ Not signed
A34.224.160.149πŸ‡ΊπŸ‡Έ Amazon34.224.0.0/12 EC2 Region prefix
PTRec2-34-224-160-149.compute-1.amazonaws.com
A72.1.32.168πŸ‡ΊπŸ‡Έ Amazon72.1.32.0/21 EC2 Prefix
NSns1.domaindiscover.com ⭐
A72.1.32.151πŸ‡ΊπŸ‡Έ Amazon72.1.32.0/21 EC2 Prefix
PTRns1.domaindiscover.com
NSns2.domaindiscover.com
A35.174.37.23πŸ‡ΊπŸ‡Έ Amazon35.168.0.0/13 EC2 IAD prefix
PTRec2-35-174-37-23.compute-1.amazonaws.com
MXmx1.daemonmail.net ⭐
A44.225.110.60πŸ‡ΊπŸ‡Έ Amazon44.224.0.0/11 EC2 PDX prefix
PTRmx1.daemonmail.net
MXmx2.daemonmail.net ⭐
A54.69.243.239πŸ‡ΊπŸ‡Έ Amazon54.68.0.0/15 EC2 PDX Prefix
PTRmx2.daemonmail.net
TXTv=spf1 include:_spf.tierra.net ~all
SOAns1.domaindiscover.comhostmaster@tierra.net 2026-08-15 #3

org

DNSSECπŸ”’ Signed (DS record present)
NSa0.org.afilias-nst.info ⭐ ⚠️ Not in parent delegation
NSa2.org.afilias-nst.info ⚠️ Not in parent delegation
NSb0.org.afilias-nst.org
NSb2.org.afilias-nst.org
NSc0.org.afilias-nst.info ⚠️ Not in parent delegation
NSd0.org.afilias-nst.org
SOAa0.org.afilias-nst.infohostmaster@donuts.email serial=1787898806

Same first word

Previous names

Next names

DNS History

6 records (6 active, 0 former)

NSns1.domaindiscover.comns2.domaindiscover.comMXmx1.daemonmail.netmx2.daemonmail.netA34.224.160.14972.1.32.168
●NSns1.domaindiscover.com2026-08-22 β†’ 2026-08-28 Β· 2 obs
● 2026-08-22 11:50:44
● 2026-08-28 06:54:22
●NSns2.domaindiscover.com2026-08-22 β†’ 2026-08-28 Β· 2 obs
● 2026-08-22 11:50:44
● 2026-08-28 06:54:22
●MXmx1.daemonmail.net2026-08-22 β†’ 2026-08-28 Β· 2 obs
● 2026-08-22 11:50:44
● 2026-08-28 06:54:22
●MXmx2.daemonmail.net2026-08-22 β†’ 2026-08-28 Β· 2 obs
● 2026-08-22 11:50:44
● 2026-08-28 06:54:22
●A34.224.160.1492026-08-22 β†’ 2026-08-28 Β· 2 obs
● 2026-08-22 11:50:44
● 2026-08-28 06:54:22
●A72.1.32.1682026-08-22 β†’ 2026-08-28 Β· 2 obs
● 2026-08-22 11:50:44
● 2026-08-28 06:54:22

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
orgb0.org.afilias-nst.org, b2.org.afilias-nst.org, d0.org.afilias-nst.org-
digitalcommandcloud.orgns1.domaindiscover.com, ns2.domaindiscover.com-

βœ… Authoritative Response

Server:72.1.32.151

NS records: ns1.domaindiscover.com, ns2.domaindiscover.com

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for digitalcommandcloud.org (unsigned zone)

⏱️ Timing

Total: 666ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A234.224.160.149, 72.1.32.168
NS2ns2.domaindiscover.com, ns1.domaindiscover.com
MX2mx2.daemonmail.net (pri: 10), mx1.daemonmail.net (pri: 10)
TXT1v=spf1 include:_spf.tierra.net ~all
SOA1ns1.domaindiscover.com hostmaster.tierra

Analysis

IP Addresses

digitalcommandcloud.org has two IP addresses: 34.224.160.149 and 72.1.32.168

stopwhitmer.org, thomasjeffersonuniversity200.org, bobarber.org plus two other host names have IP numbers in common with digitalcommandcloud.org.

Name Servers

The NS records for digitalcommandcloud.org delegate to ns1.domaindiscover.com and ns2.domaindiscover.com.

The name server configuration of digitalcommandcloud.org is shared with other domains, for instance rhotoncollection.org, arthearthandhome.net, earlylabs.com and two others.

The name servers of digitalcommandcloud.org overlap at least partially with those of other domains β€” among them menfacelift.com, myrentalassistant.com, keymm.com and two more.

These name servers commonly appear alongside the name servers ns1.tierra.net and ns2.tierra.net.

Both ns1.domaindiscover.com and ns2.domaindiscover.com have a single IP address each β€” ns1.domaindiscover.com resolves to 72.1.32.151 while ns2.domaindiscover.com resolves to 35.174.37.23.

Mail Servers

digitalcommandcloud.org uses two mail servers, mx1.daemonmail.net and mx2.daemonmail.net.

The mail server setup of digitalcommandcloud.org matches that of other domains such as bidbattles.com, glendalecommunity.com, pawsitivelypawsomeyou.com and two others.

digitalcommandcloud.org has mail servers in common with other domains β€” friscopta.org being one example.

Both mx1.daemonmail.net and mx2.daemonmail.net have a single IP address each β€” mx1.daemonmail.net resolves to 44.225.110.60 while mx2.daemonmail.net resolves to 54.69.243.239.