`vdicommunications.com`

DNSSEC	⚠️ Not signed
A	107.180.40.14^{🇺🇸 AS400754107.180.0.0/18 IAD2 Allocation}
		PTR	`14.40.180.107.host.secureserver.net`
NS	`ns1-01.azure-dns.com` ⭐
		A	2603:1061:0:700::1^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-01.azure-dns.com`
		A	13.107.236.1^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-01.azure-dns.com`
NS	`ns2-01.azure-dns.net`
		A	2620:1ec:8ec:700::1^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-01.azure-dns.net`
		A	150.171.21.1^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-01.azure-dns.net`
NS	`ns3-01.azure-dns.org`
		A	2a01:111:4000:700::1^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-01.azure-dns.org`
		A	204.14.183.1^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-01.azure-dns.org`
NS	`ns4-01.azure-dns.info`
		A	2620:1ec:bda:700::1^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-01.azure-dns.info`
		A	208.84.5.1^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-01.azure-dns.info`
MX	`vdicommunications-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c902::7^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sj0pr02cu00107.inbound.protection.outlook.com`
		A	2a01:111:f403:f802::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-byapr05cu00400.inbound.protection.outlook.com`
		A	2a01:111:f403:f902::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bl2pr02cu00101.inbound.protection.outlook.com`
		A	2a01:111:f403:f903::^{🇺🇸 Microsoft2a01:111:f000::/36}
		A	52.101.9.20^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bl0pr02cu00604.inbound.protection.outlook.com`
		A	52.101.11.2^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sn1pr03cu00102.inbound.protection.outlook.com`
		A	52.101.50.4^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-co1pr03cu00404.inbound.protection.outlook.com`
		A	52.101.50.10^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-mw2pr02cu00502.inbound.protection.outlook.com`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
TXT	`qvfc24i7oak637ijvm3ciel6i3`
SOA	`ns1-01.azure-dns.com`azuredns-hostmaster@microsoft.com serial=1

`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.net`nstld@verisign-grs.com serial=1778388046

Same first word

vdicommunications.com

DNS History

9 records (6 active, 3 former)

●NSns1-01.azure-dns.com2026-03-25 → 2026-05-10 · 3 obs

○ 2017-03-19 20:51:08
● 2026-03-25 01:03:32
● 2026-05-10 04:46:18

●NSns2-01.azure-dns.net2026-03-25 → 2026-05-10 · 3 obs

○ 2017-03-19 20:51:08
● 2026-03-25 01:03:32
● 2026-05-10 04:46:18

○NSns23.domaincontrol.com2015-05-31 → 2017-03-19 · 4 obs

● 2015-05-31 17:31:56
● 2017-03-19 20:51:08
○ 2026-03-25 01:03:32
○ 2026-05-10 04:46:18

○NSns24.domaincontrol.com2015-05-31 → 2017-03-19 · 4 obs

● 2015-05-31 17:31:56
● 2017-03-19 20:51:08
○ 2026-03-25 01:03:32
○ 2026-05-10 04:46:18

●NSns3-01.azure-dns.org2026-03-25 → 2026-05-10 · 3 obs

○ 2017-03-19 20:51:08
● 2026-03-25 01:03:32
● 2026-05-10 04:46:18

●NSns4-01.azure-dns.info2026-03-25 → 2026-05-10 · 3 obs

○ 2017-03-19 20:51:08
● 2026-03-25 01:03:32
● 2026-05-10 04:46:18

●MXvdicommunications-com.mail.protection.outlook.com2015-05-31 → 2026-05-10 · 2 obs

● 2015-05-31 17:31:56
● 2026-05-10 04:46:18

●A107.180.40.142026-03-25 → 2026-05-10 · 3 obs

○ 2017-03-19 20:51:08
● 2026-03-25 01:03:32
● 2026-05-10 04:46:18

○A23.229.140.2282015-05-31 → 2017-03-19 · 4 obs

● 2015-05-31 17:31:56
● 2017-03-19 20:51:08
○ 2026-03-25 01:03:32
○ 2026-05-10 04:46:18

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
vdicommunications.com	ns1-01.azure-dns.com, ns2-01.azure-dns.net, ns3-01.azure-dns.org, ns4-01.azure-dns.info	2 records

✅ Authoritative Response

Server:150.171.21.1

NS records: ns1-01.azure-dns.com, ns2-01.azure-dns.net, ns3-01.azure-dns.org, ns4-01.azure-dns.info

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for vdicommunications.com (unsigned zone)

⏱️ Timing

Total: 132ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`107.180.40.14`
NS	4	`ns1-01.azure-dns.com, ns2-01.azure-dns.net...`
MX	1	`vdicommunications-com.mail.protection.ou`
TXT	2	`v=spf1 include:spf.protection.outlook.co, qvfc24i7oak637ijvm3ciel6i3`
SOA	1	`ns1-01.azure-dns.com azuredns-hostmaster`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1-01.azure-dns.com, ns1-01.azure-dns.com)

Analysis

IP Addresses

vdicommunications.com points to a single IP number: 107.180.40.14.

Other host names, for instance conexusmx.com, tingledesign.com, mail.musclecarsoftexas.com, syprosolutions.com.au and jasonsfriends.org share IP numbers with vdicommunications.com.

Name Servers

vdicommunications.com is delegated to four name servers: ns1-01.azure-dns.com, ns4-01.azure-dns.info, ns2-01.azure-dns.net and ns3-01.azure-dns.org.

vdicommunications.com at least partially shares name servers with other domains, for instance abam.net, brage.no, getrumble.com, d3draftworks.com and benesse-socius.co.jp.