client-command.us - dns.ninja
client-command.us
us
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.cctld.us ⭐ | ||||||
| NS | b.cctld.us | ||||||
| NS | f.cctld.us | ||||||
| NS | k.cctld.us | ||||||
| NS | m.cctld.us | ||||||
| NS | n.cctld.us | ||||||
| NS | w.cctld.us | ||||||
| NS | x.cctld.us | ||||||
| NS | y.cctld.us | ||||||
| SOA | a.cctld.usadmin@tldns.godaddy serial=1793145683 | ||||||
Same first word
client-command.net |
client-command.us |
Previous names
clidi.us |
clidpay.us |
clidrive.us |
cliedoss.us |
cliemtauthorlze.us |
cliemtcemter.us |
clienntsareaaccoumts.us |
client-boursobank.us |
client-cdiscount.us |
DNS History
9 records (8 active, 1 former)
●NSdns1.registrar-servers.com2026-09-08 → 2026-10-28 · 2 obs
● 2026-10-28 01:05:16
●NSdns2.registrar-servers.com2026-09-08 → 2026-10-28 · 2 obs
● 2026-10-28 01:05:16
●MXalt1.aspmx.l.google.com2026-09-08 → 2026-10-28 · 2 obs
● 2026-10-28 01:05:16
●MXalt2.aspmx.l.google.com2026-09-08 → 2026-10-28 · 2 obs
● 2026-10-28 01:05:16
●MXalt3.aspmx.l.google.com2026-09-08 → 2026-10-28 · 2 obs
● 2026-10-28 01:05:16
●MXalt4.aspmx.l.google.com2026-09-08 → 2026-10-28 · 2 obs
● 2026-10-28 01:05:16
●MXaspmx.l.google.com2026-09-08 → 2026-10-28 · 2 obs
● 2026-10-28 01:05:16
○A143.198.158.112026-09-08 → 2026-09-08 · 3 obs
○ 2026-10-14 13:53:08
○ 2026-10-28 01:05:16
●A35.165.220.2292026-10-14 → 2026-10-28 · 3 obs
● 2026-10-14 13:53:08
● 2026-10-28 01:05:16
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| us | b.cctld.us, f.cctld.us, k.cctld.us, m.cctld.us... | - |
| client-command.us | dns2.registrar-servers.com, dns1.registrar-servers.com | - |
✅ Authoritative Response
Server:156.154.133.200
NS records: dns2.registrar-servers.com, dns1.registrar-servers.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: 1143ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 35.165.220.229 |
| NS | 2 | dns1.registrar-servers.com, dns2.registrar-servers.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 3 | v=spf1 include:_spf.google.com ~all, google-site-verification=QvcVOr9nvk2WXtc... |
| SOA | 1 | dns1.registrar-servers.com hostmaster.re |
Analysis
IP Addresses
client-command.us resolves to one IP address: 35.165.220.229.
Name Servers
client-command.us is delegated to two name servers: dns1.registrar-servers.com and dns2.registrar-servers.com.
dns1.registrar-servers.com and dns2.registrar-servers.com each resolve to two IP addresses: dns1.registrar-servers.com points to 156.154.132.200 and 2610:a1:1024::200, while dns2.registrar-servers.com points to 156.154.133.200 and 2610:a1:1025::200.
Mail Servers
client-command.us is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
Hostnames that resolve to two IP addresses:
aspmx.l.google.com points to 192.178.164.27 and 2607:f8b0:4023:2009::1a.
alt1.aspmx.l.google.com points to 192.178.228.26 and 2a00:1450:4025:4403::1b.
alt2.aspmx.l.google.com points to 172.253.135.27 and 2607:f8b0:4023:1015::1b.
alt3.aspmx.l.google.com points to 192.178.223.26 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com points to 172.253.157.27 and 2a00:1450:400c:c23::1a.