connectedmobility.org - dns.ninja
connectedmobility.org
org
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a0.org.afilias-nst.info ⭐ ⚠️ Not in parent delegation | ||||||
| NS | a2.org.afilias-nst.info ⚠️ Not in parent delegation | ||||||
| NS | b0.org.afilias-nst.org | ||||||
| NS | b2.org.afilias-nst.org | ||||||
| NS | c0.org.afilias-nst.info ⚠️ Not in parent delegation | ||||||
| NS | d0.org.afilias-nst.org | ||||||
| SOA | a0.org.afilias-nst.infohostmaster@donuts.email serial=1782303323 | ||||||
Same first word
connectedmobility.org |
connectedmobility.com |
Similar names
DNS History
12 records (9 active, 3 former)
●NSns49.domaincontrol.com2015-06-22 → 2026-06-24 · 2 obs
● 2026-06-24 12:46:02
●NSns50.domaincontrol.com2015-06-22 → 2026-06-24 · 2 obs
● 2026-06-24 12:46:02
●MXalt1.aspmx.l.google.com2026-03-24 → 2026-06-24 · 3 obs
● 2026-03-24 21:54:48
● 2026-06-24 12:46:02
●MXalt2.aspmx.l.google.com2026-03-24 → 2026-06-24 · 3 obs
● 2026-03-24 21:54:48
● 2026-06-24 12:46:02
●MXaspmx.l.google.com2026-03-24 → 2026-06-24 · 3 obs
● 2026-03-24 21:54:48
● 2026-06-24 12:46:02
●MXaspmx2.googlemail.com2026-03-24 → 2026-06-24 · 3 obs
● 2026-03-24 21:54:48
● 2026-06-24 12:46:02
●MXaspmx3.googlemail.com2026-03-24 → 2026-06-24 · 3 obs
● 2026-03-24 21:54:48
● 2026-06-24 12:46:02
○MXmailstore1.secureserver.net2015-06-22 → 2018-08-29 · 4 obs
● 2018-08-29 04:13:26
○ 2026-03-24 21:54:48
○ 2026-06-24 12:46:02
○MXsmtp.secureserver.net2015-06-22 → 2018-08-29 · 4 obs
● 2018-08-29 04:13:26
○ 2026-03-24 21:54:48
○ 2026-06-24 12:46:02
●A15.197.225.1282026-03-24 → 2026-06-24 · 3 obs
● 2026-03-24 21:54:48
● 2026-06-24 12:46:02
●A3.33.251.1682026-03-24 → 2026-06-24 · 3 obs
● 2026-03-24 21:54:48
● 2026-06-24 12:46:02
○A50.63.202.82015-06-22 → 2018-08-29 · 4 obs
● 2018-08-29 04:13:26
○ 2026-03-24 21:54:48
○ 2026-06-24 12:46:02
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| org | b0.org.afilias-nst.org, b2.org.afilias-nst.org, d0.org.afilias-nst.org | - |
| connectedmobility.org | ns49.domaincontrol.com, ns50.domaincontrol.com | - |
✅ Authoritative Response
Server:97.74.104.25
NS records: ns49.domaincontrol.com, ns50.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for connectedmobility.org (unsigned zone)
⏱️ Timing
Total: 1242ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 15.197.225.128, 3.33.251.168 |
| NS | 2 | ns49.domaincontrol.com, ns50.domaincontrol.com |
| MX | 5 | alt1.aspmx.l.google.com (pri: 5), alt2.aspmx.l.google.com (pri: 5)... |
| TXT | 2 | google-site-verification=K_wTIX3b1R6th6M, v=spf1 include:_spf.google.com ~all |
| SOA | 1 | ns49.domaincontrol.com dns.jomax.net |
Analysis
IP Addresses
connectedmobility.org directs to two IP numbers, 3.33.251.168 and 15.197.225.128
Among the host names that share IP numbers with connectedmobility.org are planetwiseinc.com, derventiosolutions.com, yminsurance.com and two others.
Name Servers
connectedmobility.org uses two name servers for its delegation: ns49.domaincontrol.com and ns50.domaincontrol.com.
connectedmobility.org has the same name server delegation as a number of other domains, such as banco-comafi.org, timelesspiece.com, jim-lunsford.com and two more.
There is an overlap in name servers between connectedmobility.org and other domains, for example jabeztec.com, precisionspeaking.com and thecatprotectionsociety.org
The two host names ns49.domaincontrol.com and ns50.domaincontrol.com each have a pair of IP addresses: ns49.domaincontrol.com has 97.74.104.25 and 2603:5:2182::19, and ns50.domaincontrol.com has 173.201.72.25 and 2603:5:2282::19.
Mail Servers
Mail for connectedmobility.org is handled by five mail servers, namely aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
connectedmobility.org shares at least some of its mail servers with other domains — for example ns500693.ns500765.ns500734.ns500734.ns500734.ns500693.ns500699.ns500734.ns500588.ns500693.ns500699.ns500699.ns500588.ns500683.ns500699.ns500683.ns500112.dtrkdll.com, ns500731.ns500742.ns500731.ns500742.ns500731.ns500671.ns500704.ns500671.ns500705.ns500704.ns500705.ns500688.lusty(0x736c7574)z.com, ns500698.ns500759.ns500758.ns500758.ns500698.ns500735.ns500736.ns500736.ns500736.ns500576.ns500576.ns500698.ns500708.ns500576.ns500576.ns500576.trackreceptor.com and two more.
It is common to find these mail servers paired with mail servers alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 more.
Hosts with two IP numbers each:
aspmx2.googlemail.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1a.
aspmx3.googlemail.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1b.
aspmx.l.google.com directs traffic to 142.251.163.27 and 2607:f8b0:4004:c1f::1b.
alt1.aspmx.l.google.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1a.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 2800:3f0:4003:c0f::1a IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 172.253.116.27 IP addresses each.