`dragonvoice2textmessenger.com`

DNSSEC	⚠️ Not signed
NS	`ns1-34.azure-dns.com` ⭐
		A	2603:1061:0:10::22^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-34.azure-dns.com`
		A	150.171.10.34^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns1-34.azure-dns.com`
NS	`ns2-34.azure-dns.net`
		A	2620:1ec:8ec:10::22^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-34.azure-dns.net`
		A	150.171.16.34^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-34.azure-dns.net`
NS	`ns3-34.azure-dns.org`
		A	2a01:111:4000:10::22^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-34.azure-dns.org`
		A	13.107.222.34^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns3-34.azure-dns.org`
NS	`ns4-34.azure-dns.info`
		A	2620:1ec:bda:10::22^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-34.azure-dns.info`
		A	13.107.206.34^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns4-34.azure-dns.info`
SOA	`ns1-34.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=1777243041

Same first word

dragonvoice2textmessenger.com

DNS History

8 records (4 active, 4 former)

●NSns1-34.azure-dns.com2026-02-28 → 2026-04-26 · 3 obs

○ 2019-01-15 02:12:38
● 2026-02-28 16:18:50
● 2026-04-26 22:46:38

●NSns2-34.azure-dns.net2026-02-28 → 2026-04-26 · 3 obs

○ 2019-01-15 02:12:38
● 2026-02-28 16:18:50
● 2026-04-26 22:46:38

○NSns25.worldnic.com2015-06-13 → 2019-01-15 · 4 obs

● 2015-06-13 16:35:40
● 2019-01-15 02:12:38
○ 2026-02-28 16:18:50
○ 2026-04-26 22:46:38

○NSns26.worldnic.com2015-06-13 → 2019-01-15 · 4 obs

● 2015-06-13 16:35:40
● 2019-01-15 02:12:38
○ 2026-02-28 16:18:50
○ 2026-04-26 22:46:38

●NSns3-34.azure-dns.org2026-02-28 → 2026-04-26 · 3 obs

○ 2019-01-15 02:12:38
● 2026-02-28 16:18:50
● 2026-04-26 22:46:38

●NSns4-34.azure-dns.info2026-02-28 → 2026-04-26 · 3 obs

○ 2019-01-15 02:12:38
● 2026-02-28 16:18:50
● 2026-04-26 22:46:38

○MXp.webcom.ctmail.com2016-01-23 → 2019-01-15 · 4 obs

● 2016-01-23 02:33:46
● 2019-01-15 02:12:38
○ 2026-02-28 16:18:50
○ 2026-04-26 22:46:38

○A205.178.189.1292015-06-13 → 2019-01-15 · 4 obs

● 2015-06-13 16:35:40
● 2019-01-15 02:12:38
○ 2026-02-28 16:18:50
○ 2026-04-26 22:46:38

🔍 DNS Trace

📋 Delegation Chain

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

✅ Authoritative Response

Server:13.107.222.34

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for dragonvoice2textmessenger.com (unsigned zone)

⏱️ Timing

Total: 1009ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns1-34.azure-dns.com, ns2-34.azure-dns.net...`
SOA	1	`ns1-34.azure-dns.com azuredns-hostmaster`

📌 Glue Records Collected

Total: 2

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

Analysis

Name Servers

dragonvoice2textmessenger.com delegates to four name servers: ns1-34.azure-dns.com, ns4-34.azure-dns.info, ns2-34.azure-dns.net and ns3-34.azure-dns.org.

dragonvoice2textmessenger.com at least partially shares name servers with other domains, for instance steweag.at, coding-for-tomorrow.de, globalpartnersincare.org, swedencentral-prod.cosmic.office.net and hownowhq.com.

Host names with two IP numbers: ns1-34.azure-dns.com points to 2603:1061:0:10::22 and 150.171.10.34; ns4-34.azure-dns.info points to 2620:1ec:bda:10::22 and 13.107.206.34; ns2-34.azure-dns.net points to 2620:1ec:8ec:10::22 and 150.171.16.34; ns3-34.azure-dns.org points to 2a01:111:4000:10::22 and 13.107.222.34.

dragonvoice2textmessenger.com - robtex.com