myspacesworks.com - dns.ninja
myspacesworks.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=1786580094 | ||||||
Same first word
myspacesworks.com |
DNS History
10 records (8 active, 2 former)
●NSns1.netnames.net2016-12-20 → 2026-08-13 · 2 obs
● 2026-08-13 00:38:36
●NSns2.netnames.net2016-12-20 → 2026-08-13 · 2 obs
● 2026-08-13 00:38:36
●NSns5.netnames.net2016-12-20 → 2026-08-13 · 2 obs
● 2026-08-13 00:38:36
●NSns6.netnames.net2016-12-20 → 2026-08-13 · 2 obs
● 2026-08-13 00:38:36
●MXrelay1.netnames.net2016-12-20 → 2026-08-13 · 2 obs
● 2026-08-13 00:38:36
●MXrelay2.netnames.net2016-12-20 → 2026-08-13 · 2 obs
● 2026-08-13 00:38:36
○A185.26.230.1292016-12-20 → 2016-12-20 · 3 obs
○ 2017-11-06 07:07:16
○ 2026-08-13 00:38:36
●A45.223.20.12026-03-15 → 2026-08-13 · 3 obs
● 2026-03-15 20:11:30
● 2026-08-13 00:38:36
●A45.223.26.12026-03-15 → 2026-08-13 · 3 obs
● 2026-03-15 20:11:30
● 2026-08-13 00:38:36
○A77.95.80.1772017-11-06 → 2018-03-05 · 5 obs
● 2017-11-06 07:07:16
● 2018-03-05 20:54:00
○ 2026-03-15 20:11:30
○ 2026-08-13 00:38:36
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | g.gtld-servers.net, a.gtld-servers.net, l.gtld-servers.net, j.gtld-servers.net... | - |
| myspacesworks.com | ns2.netnames.net, ns1.netnames.net, ns5.netnames.net, ns6.netnames.net | - |
✅ Authoritative Response
Server:156.154.131.100
NS records: ns2.netnames.net, ns1.netnames.net, ns5.netnames.net, ns6.netnames.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for myspacesworks.com (unsigned zone)
⏱️ Timing
Total: 1390ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 45.223.20.1, 45.223.26.1 |
| NS | 4 | ns1.netnames.net, ns2.netnames.net... |
| MX | 2 | relay1.netnames.net (pri: 10), relay2.netnames.net (pri: 20) |
| TXT | 1 | v=spf1 ip4:149.72.39.137 ip4:149.72.59.1 |
| SOA | 1 | ns1.netnames.net hostmaster.cscdns.net |
Analysis
IP Addresses
myspacesworks.com points to the IP addresses 45.223.20.1 and 45.223.26.1
The host names myregus.com, my.hq.com, basepointapp.co.uk and basepoint.co.uk all share IP numbers with myspacesworks.com.
Name Servers
Four name servers handle the delegation for myspacesworks.com: ns1.netnames.net, ns2.netnames.net, ns5.netnames.net and ns6.netnames.net.
The name servers of myspacesworks.com overlap at least partially with those of other domains — among them saxobankingcircle.eu, galetta.de, batimat.com and two more.
These name servers commonly appear alongside the name servers dns1.cscdns.net and dns2.cscdns.net.
ns1.netnames.net, ns2.netnames.net, ns5.netnames.net and ns6.netnames.net each have two IP addresses. Specifically, ns1.netnames.net resolves to 156.154.130.100 and 2610:a1:1022::100, ns2.netnames.net resolves to 156.154.131.100 and 2610:a1:1023::100, ns5.netnames.net resolves to 156.154.130.100 and 2610:a1:1022::100 and ns6.netnames.net resolves to 156.154.131.100 and 2610:a1:1023::100.
Host names pointing to 2610:a1:1022::100 IP addresses: ns1.netnames.net and ns5.netnames.net.
Host names pointing to 156.154.130.100 IP addresses: ns1.netnames.net and ns5.netnames.net.
Host names pointing to 2610:a1:1023::100 IP addresses: ns2.netnames.net and ns6.netnames.net.
Host names pointing to 156.154.131.100 IP addresses: ns2.netnames.net and ns6.netnames.net.
Mail Servers
myspacesworks.com uses two mail servers, relay1.netnames.net and relay2.netnames.net.
The mail server setup of myspacesworks.com matches that of other domains such as kapsch.ro, betfairmoc.org, biktarvy.com.cdn.cloudflare.net and two others.
myspacesworks.com has mail servers in common with other domains — sageone.com being one example.
Both relay1.netnames.net and relay2.netnames.net have a single IP address each — relay1.netnames.net resolves to 185.26.230.83 while relay2.netnames.net resolves to 185.26.230.89.