musiccitycode.com - dns.ninja
musiccitycode.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=1784813807 | ||||||
Subdomains
mail.musiccitycode.com |
Same first word
musiccitycode.com |
DNS History
11 records (8 active, 3 former)
●NSdns1.registrar-servers.com2026-02-28 → 2026-07-23 · 3 obs
● 2026-02-28 21:08:18
● 2026-07-23 13:39:46
●NSdns2.registrar-servers.com2026-02-28 → 2026-07-23 · 3 obs
● 2026-02-28 21:08:18
● 2026-07-23 13:39:46
○NSpdns1.registrar-servers.com2016-12-18 → 2016-12-18 · 3 obs
○ 2026-02-28 21:08:18
○ 2026-07-23 13:39:46
○NSpdns2.registrar-servers.com2016-12-18 → 2016-12-18 · 3 obs
○ 2026-02-28 21:08:18
○ 2026-07-23 13:39:46
●MXalt1.aspmx.l.google.com2016-12-18 → 2026-07-23 · 2 obs
● 2026-07-23 13:39:46
●MXalt2.aspmx.l.google.com2016-12-18 → 2026-07-23 · 2 obs
● 2026-07-23 13:39:46
●MXaspmx.l.google.com2016-12-18 → 2026-07-23 · 2 obs
● 2026-07-23 13:39:46
●MXaspmx2.googlemail.com2016-12-18 → 2026-07-23 · 2 obs
● 2026-07-23 13:39:46
●MXaspmx3.googlemail.com2016-12-18 → 2026-07-23 · 2 obs
● 2026-07-23 13:39:46
○A162.255.119.2482016-12-18 → 2016-12-18 · 3 obs
○ 2026-02-28 21:08:18
○ 2026-07-23 13:39:46
●A178.128.236.382026-02-28 → 2026-07-23 · 3 obs
● 2026-02-28 21:08:18
● 2026-07-23 13:39:46
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | k.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| musiccitycode.com | dns1.registrar-servers.com, dns2.registrar-servers.com | 4 records |
✅ Authoritative Response
Server:156.154.133.200
NS records: dns1.registrar-servers.com, dns2.registrar-servers.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for musiccitycode.com (unsigned zone)
⏱️ Timing
Total: 179ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 178.128.236.38 |
| 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 | 7 | MS=ms15140900, musiccitytech.azurewebsites.net... |
| SOA | 1 | dns1.registrar-servers.com hostmaster.re |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (dns1.registrar-servers.com, dns1.registrar-servers.com, dns2.registrar-servers.com...)
Analysis
Hierarchy
musiccitycode.com serves as the parent of mail.musiccitycode.com.
IP Addresses
musiccitycode.com has exactly one IP address — 178.128.236.38.
Name Servers
Two name servers handle the delegation for musiccitycode.com: dns1.registrar-servers.com and dns2.registrar-servers.com.
The name server configuration of musiccitycode.com is shared with other domains, for instance b24.work, exoarcade.com, luxespalife.com and two others.
musiccitycode.com shares at least some of its name servers with domains including ndscloud.net, bengaliweddings.com and deitryn.com
These name servers tend to appear together with the name servers dns3.registrar-servers.com, dns4.registrar-servers.com and dns5.registrar-servers.com.
dns1.registrar-servers.com and dns2.registrar-servers.com both carry two IP addresses. The A records for dns1.registrar-servers.com are 156.154.132.200 and 2610:a1:1024::200; the A records for dns2.registrar-servers.com are 156.154.133.200 and 2610:a1:1025::200.
Mail Servers
musiccitycode.com is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
At least some of the mail servers used by musiccitycode.com are shared with other domains: drift.com, elzan.com, ns500742.ns500671.ns500742.ns500742.ns500731.ns500704.ns500688.ns500671.ns500671.tenderladiesbz.com and two others among them.
These mail servers are often deployed together with alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 other mail servers.
Host names pointing to two IP addresses:
aspmx2.googlemail.com resolves to two addresses: 108.177.123.27 and 2800:3f0:4003:c0f::1b.
aspmx3.googlemail.com resolves to two addresses: 172.253.116.27 and 2a00:1450:400b:c02::1b.
aspmx.l.google.com resolves to two addresses: 172.253.63.27 and 2607:f8b0:4004:c07::1a.
alt1.aspmx.l.google.com resolves to two addresses: 108.177.123.26 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com resolves to two addresses: 172.253.116.27 and 2a00:1450:400b:c02::1a.
aspmx3.googlemail.com along with alt2.aspmx.l.google.com each resolve to 172.253.116.27 IP addresses.