managedssh.com - dns.ninja
managedssh.com
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.netnstld@verisign-grs.com serial=1793452531 | ||||||
Same first word
managedssh.com |
Similar names
Previous names
Next names
DNS History
7 records (6 active, 1 former)
●NSns33.domaincontrol.com2015-05-08 → 2026-10-31 · 2 obs
● 2026-10-31 13:26:54
●NSns34.domaincontrol.com2015-05-08 → 2026-10-31 · 2 obs
● 2026-10-31 13:26:54
●MXmailstore1.secureserver.net2015-05-08 → 2026-10-31 · 2 obs
● 2026-10-31 13:26:54
●MXsmtp.secureserver.net2015-05-08 → 2026-10-31 · 2 obs
● 2026-10-31 13:26:54
●A15.197.225.1282026-09-28 → 2026-10-31 · 3 obs
● 2026-09-28 07:43:06
● 2026-10-31 13:26:54
●A3.33.251.1682026-09-28 → 2026-10-31 · 3 obs
● 2026-09-28 07:43:06
● 2026-10-31 13:26:54
○A50.63.202.382015-05-08 → 2017-06-29 · 4 obs
● 2017-06-29 07:13:42
○ 2026-09-28 07:43:06
○ 2026-10-31 13:26:54
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | b.gtld-servers.net, m.gtld-servers.net, a.gtld-servers.net, f.gtld-servers.net... | - |
| managedssh.com | ns33.domaincontrol.com, ns34.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:97.74.106.17
NS records: ns33.domaincontrol.com, ns34.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for managedssh.com (unsigned zone)
⏱️ Timing
Total: 640ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 15.197.225.128, 3.33.251.168 |
| NS | 2 | ns34.domaincontrol.com, ns33.domaincontrol.com |
| MX | 2 | smtp.secureserver.net (pri: 0), mailstore1.secureserver.net (pri: 10) |
| SOA | 1 | ns33.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns33.domaincontrol.com, ns33.domaincontrol.com, ns34.domaincontrol.com...)
Analysis
IP Addresses
managedssh.com has two IP addresses: 3.33.251.168 and 15.197.225.128
computerswtf.com, hospitalcme.org, southernaccents.life and two other host names share IP numbers with managedssh.com.
Name Servers
Two name servers handle the delegation for managedssh.com: ns33.domaincontrol.com and ns34.domaincontrol.com.
managedssh.com uses the same name servers as several other domains — among them sunandsandiego.com, lonestarhire.com.au, slightlyfunnyrancher.com and two more.
ns33.domaincontrol.com and ns34.domaincontrol.com both carry two IP addresses. The A records for ns33.domaincontrol.com are 97.74.106.17 and 2603:5:21a1::11; the A records for ns34.domaincontrol.com are 173.201.74.17 and 2603:5:22a1::11.
Mail Servers
Mail for managedssh.com is handled by two mail servers — mailstore1.secureserver.net and smtp.secureserver.net.
managedssh.com uses an identical mail server configuration to several other domains — among them djgerace.com, trunkandbag.com, vermontcraftmom.com and two more.
managedssh.com has mail servers in common with other domains — doctrix.app being one example.
Both mailstore1.secureserver.net and smtp.secureserver.net point to three IP numbers: mailstore1.secureserver.net points to 216.69.141.78, 216.69.141.114 and 216.69.141.162, while smtp.secureserver.net points to 216.69.141.71, 216.69.141.84 and 216.69.141.113.