mdbell.com - dns.ninja
mdbell.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=1785015052 | ||||||
Same first word
Similar names
DNS History
10 records (9 active, 1 former)
●NSns05.domaincontrol.com2015-06-14 → 2026-07-25 · 2 obs
● 2026-07-25 21:58:58
●NSns06.domaincontrol.com2015-06-14 → 2026-07-25 · 2 obs
● 2026-07-25 21:58:58
●MXalt1.aspmx.l.google.com2015-06-14 → 2026-07-25 · 2 obs
● 2026-07-25 21:58:58
●MXalt2.aspmx.l.google.com2015-06-14 → 2026-07-25 · 2 obs
● 2026-07-25 21:58:58
●MXaspmx.l.google.com2015-06-14 → 2026-07-25 · 2 obs
● 2026-07-25 21:58:58
●MXaspmx2.googlemail.com2015-06-14 → 2026-07-25 · 2 obs
● 2026-07-25 21:58:58
●MXaspmx3.googlemail.com2015-06-14 → 2026-07-25 · 2 obs
● 2026-07-25 21:58:58
●A15.197.225.1282026-02-23 → 2026-07-25 · 3 obs
● 2026-02-23 16:54:04
● 2026-07-25 21:58:58
○A184.168.221.32015-06-14 → 2016-03-28 · 4 obs
● 2016-03-28 22:37:18
○ 2026-02-23 16:54:04
○ 2026-07-25 21:58:58
●A3.33.251.1682026-02-23 → 2026-07-25 · 3 obs
● 2026-02-23 16:54:04
● 2026-07-25 21:58:58
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| mdbell.com | ns05.domaincontrol.com, ns06.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:173.201.70.3
NS records: ns05.domaincontrol.com, ns06.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for mdbell.com (unsigned zone)
⏱️ Timing
Total: 152ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 15.197.225.128, 3.33.251.168 |
| NS | 2 | ns05.domaincontrol.com, ns06.domaincontrol.com |
| MX | 5 | alt1.aspmx.l.google.com (pri: 5), alt2.aspmx.l.google.com (pri: 5)... |
| SOA | 1 | ns05.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns05.domaincontrol.com, ns05.domaincontrol.com, ns06.domaincontrol.com...)
Analysis
IP Addresses
mdbell.com directs to two IP numbers, 3.33.251.168 and 15.197.225.128
volconvo.com, gravityrcs.com, shondell.us and two other host names share IP numbers with mdbell.com.
Name Servers
Two name servers handle the delegation for mdbell.com: ns05.domaincontrol.com and ns06.domaincontrol.com.
mdbell.com uses the same name servers as several other domains — among them omnescurae.com, streamlinecompany.com, exitrealtypremium.com and two more.
ns05.domaincontrol.com and ns06.domaincontrol.com both carry two IP addresses. The A records for ns05.domaincontrol.com are 97.74.102.3 and 2603:5:2160::3; the A records for ns06.domaincontrol.com are 173.201.70.3 and 2603:5:2260::3.
Mail Servers
Mail for mdbell.com is handled by five mail servers, namely aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
mdbell.com has at least partial mail server overlap with other domains such as ns500698.ns500758.ns500759.ns500698.ns500736.ns500735.ns500698.ns500735.ns500708.ns500708.ns500708.ns500686.ns500652.ns500619.ns500576.trackreceptor.com, ns500759.ns500759.ns500759.ns500758.ns500758.ns500758.ns500735.ns500736.ns500698.ns500698.ns500708.ns500698.ns500652.ns500576.ns500576.trackreceptor.com, ns500759.ns500758.ns500698.ns500758.ns500736.ns500735.ns500576.ns500576.ns500576.ns500698.ns500619.ns500619.ns500619.trackreceptor.com and two more.
These mail servers commonly co-occur with mail servers alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.
Hostnames that resolve to two IP addresses:
aspmx2.googlemail.com resolves to two addresses: 108.177.123.26 and 2800:3f0:4003:c0f::1a.
aspmx3.googlemail.com resolves to two addresses: 172.253.116.27 and 2a00:1450:400b:c02::1a.
aspmx.l.google.com resolves to two addresses: 172.253.115.27 and 2607:f8b0:4004:c08::1b.
alt1.aspmx.l.google.com resolves to two addresses: 108.177.123.27 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com resolves to two addresses: 172.253.116.27 and 2a00:1450:400b:c02::1b.
aspmx3.googlemail.com along with alt2.aspmx.l.google.com each resolve to 172.253.116.27 IP addresses.