vsync.vdscloud.com - dns.ninja
vsync.vdscloud.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 81.95.118.133🇧🇪 LCPDCO81.95.118.0/23 DCoostkamp colo | ||||||
vdscloud.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.edpnet.be ⭐ | ||||||
| NS | ns2.edpnet.be | ||||||
| MX | aspmx.l.google.com ⭐ | ||||||
| MX | alt1.aspmx.l.google.com(5) | ||||||
| MX | alt2.aspmx.l.google.com(5) | ||||||
| MX | alt3.aspmx.l.google.com(10) | ||||||
| MX | alt4.aspmx.l.google.com(10) | ||||||
| TXT | v=spf1 include:_spf.google.com ~all | ||||||
| SOA | ns1.edpnet.beadmin@edpnet.net 2024-06-03 #0 | ||||||
Same first word
vsync.io |
vsync.mobi |
vsync.co.uk |
vsync.com |
vsync.co |
vsync.tv |
vsync.de |
vsync.pw |
vsync.net |
vsync.in |
vsync.org |
vsync.eu |
Similar names
DNS History
2 records (1 active, 1 former)
○A37.59.140.1812015-07-13 → 2015-11-14 · 4 obs
● 2015-07-13 15:30:00
● 2015-11-14 22:12:28
○ 2016-03-02 21:39:34
○ 2026-07-25 12:29:02
● 2015-11-14 22:12:28
○ 2016-03-02 21:39:34
○ 2026-07-25 12:29:02
●A81.95.118.1332026-03-16 → 2026-07-25 · 3 obs
○ 2016-03-02 21:39:34
● 2026-03-16 01:59:18
● 2026-07-25 12:29:02
● 2026-03-16 01:59:18
● 2026-07-25 12:29:02
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | k.gtld-servers.net, i.gtld-servers.net, f.gtld-servers.net, m.gtld-servers.net... | - |
| vdscloud.com | ns1.edpnet.be, ns2.edpnet.be | - |
✅ Authoritative Response
Server:212.71.8.11
NS records: ns1.edpnet.be, ns2.edpnet.be
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for vdscloud.com (unsigned zone)
⏱️ Timing
Total: 609ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 81.95.118.133 |
Analysis
IP Addresses
vsync.vdscloud.com points to a single IP number: 81.95.118.133.
nakivo.vdscloud.com and freenas.vdscloud.com, along with other host names, share IP addresses with vsync.vdscloud.com.