medesync.com - dns.ninja
medesync.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=1784895497 | ||||||
Subdomains
secure.medesync.com |
secure2.medesync.com |
www.medesync.com |
secure1.medesync.com |
patient.medesync.com |
aidenonprod.medesync.com |
secure1-api.medesync.com |
Same first word
medesync.com |
DNS History
18 records (7 active, 11 former)
○NSns-1312.awsdns-36.org2017-08-13 → 2017-10-01 · 5 obs
● 2017-08-13 11:09:52
● 2017-10-01 19:22:24
○ 2026-02-19 10:53:52
○ 2026-07-24 12:48:12
●NSns-1481.awsdns-57.org2026-02-19 → 2026-07-24 · 3 obs
● 2026-02-19 10:53:52
● 2026-07-24 12:48:12
●NSns-1769.awsdns-29.co.uk2026-02-19 → 2026-07-24 · 3 obs
● 2026-02-19 10:53:52
● 2026-07-24 12:48:12
○NSns-1784.awsdns-31.co.uk2017-08-13 → 2017-10-01 · 5 obs
● 2017-08-13 11:09:52
● 2017-10-01 19:22:24
○ 2026-02-19 10:53:52
○ 2026-07-24 12:48:12
○NSns-429.awsdns-53.com2017-08-13 → 2017-10-01 · 5 obs
● 2017-08-13 11:09:52
● 2017-10-01 19:22:24
○ 2026-02-19 10:53:52
○ 2026-07-24 12:48:12
●NSns-466.awsdns-58.com2026-02-19 → 2026-07-24 · 3 obs
● 2026-02-19 10:53:52
● 2026-07-24 12:48:12
○NSns-630.awsdns-14.net2017-08-13 → 2017-10-01 · 5 obs
● 2017-08-13 11:09:52
● 2017-10-01 19:22:24
○ 2026-02-19 10:53:52
○ 2026-07-24 12:48:12
●NSns-885.awsdns-46.net2026-02-19 → 2026-07-24 · 3 obs
● 2026-02-19 10:53:52
● 2026-07-24 12:48:12
○NSns1.p30.dynect.net2015-09-01 → 2016-10-20 · 4 obs
● 2016-10-20 20:05:48
○ 2017-08-13 11:09:52
○ 2026-07-24 12:48:12
○NSns2.p30.dynect.net2015-09-01 → 2016-10-20 · 4 obs
● 2016-10-20 20:05:48
○ 2017-08-13 11:09:52
○ 2026-07-24 12:48:12
○NSns3.p30.dynect.net2015-09-01 → 2016-10-20 · 4 obs
● 2016-10-20 20:05:48
○ 2017-08-13 11:09:52
○ 2026-07-24 12:48:12
○NSns4.p30.dynect.net2015-09-01 → 2016-10-20 · 4 obs
● 2016-10-20 20:05:48
○ 2017-08-13 11:09:52
○ 2026-07-24 12:48:12
●MXbliksem.nssi.telus.com2015-09-01 → 2026-07-24 · 2 obs
● 2026-07-24 12:48:12
●MXhagel.nssi.telus.com2015-09-01 → 2026-07-24 · 2 obs
● 2026-07-24 12:48:12
●A142.169.24.612026-02-19 → 2026-07-24 · 3 obs
● 2026-02-19 10:53:52
● 2026-07-24 12:48:12
○A192.175.105.1342017-08-13 → 2017-10-01 · 5 obs
● 2017-08-13 11:09:52
● 2017-10-01 19:22:24
○ 2026-02-19 10:53:52
○ 2026-07-24 12:48:12
○A209.172.58.2052015-10-20 → 2016-10-20 · 5 obs
● 2015-10-20 08:51:02
● 2016-10-20 20:05:48
○ 2017-08-13 11:09:52
○ 2026-07-24 12:48:12
○A70.38.15.2292015-09-01 → 2015-09-01 · 3 obs
○ 2015-10-20 08:51:02
○ 2026-07-24 12:48:12
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| medesync.com | ns-466.awsdns-58.com, ns-885.awsdns-46.net, ns-1769.awsdns-29.co.uk, ns-1481.awsdns-57.org | 2 records |
✅ Authoritative Response
Server:205.251.198.233
NS records: ns-466.awsdns-58.com, ns-885.awsdns-46.net, ns-1769.awsdns-29.co.uk, ns-1481.awsdns-57.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for medesync.com (unsigned zone)
⏱️ Timing
Total: 2634ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 142.169.24.61 |
| NS | 4 | ns-1481.awsdns-57.org, ns-1769.awsdns-29.co.uk... |
| MX | 2 | bliksem.nssi.telus.com (pri: 20), hagel.nssi.telus.com (pri: 20) |
| TXT | 1 | _yow2y5cgxkzjj19fduiq9bcqvylteu0 |
| SOA | 1 | ns-885.awsdns-46.net awsdns-hostmaster.a |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns-466.awsdns-58.com, ns-466.awsdns-58.com)
Analysis
Hierarchy
medesync.com is a parent domain; its children include secure.medesync.com, secure2.medesync.com, www.medesync.com, secure1.medesync.com, patient.medesync.com and a few other host names.
IP Addresses
medesync.com has exactly one IP address — 142.169.24.61.
Name Servers
Four name servers handle the delegation for medesync.com: ns-466.awsdns-58.com, ns-885.awsdns-46.net, ns-1481.awsdns-57.org and ns-1769.awsdns-29.co.uk.
medesync.com partially shares its NS delegation with several other domains, including bishopsguns.com, keihan-group-jobinfo.net, filthydirty.com and two others.
ns-466.awsdns-58.com, ns-885.awsdns-46.net, ns-1481.awsdns-57.org and ns-1769.awsdns-29.co.uk each carry two IP addresses. ns-466.awsdns-58.com has 205.251.193.210 and 2600:9000:5301:d200::1; ns-885.awsdns-46.net has 205.251.195.117 and 2600:9000:5303:7500::1; ns-1481.awsdns-57.org has 205.251.197.201 and 2600:9000:5305:c900::1; ns-1769.awsdns-29.co.uk has 205.251.198.233 and 2600:9000:5306:e900::1.
Mail Servers
medesync.com uses two mail servers, bliksem.nssi.telus.com and hagel.nssi.telus.com.
The mail server setup of medesync.com matches that of other domains such as sherpa-grc.com, med-access.net, arpel.com and two others.
At least some of the mail servers used by medesync.com are shared with other domains: friendlyfuture.com, storyhive.com, telusmobilite.ca and two others among them.
The mail servers bcv-secee08.nssi.telus.com, onl-secee08.nssi.telus.com and donder.nssi.telus.com frequently co-occur with these mail servers.
Host names resolving to a single IP address:
bliksem.nssi.telus.com directs to 204.174.64.57.