`didconference.com`

DNSSEC	⚠️ Not signed
NS	`ns1-38.azure-dns.com` ⭐
		A	2603:1061:0:10::26^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-38.azure-dns.com`
		A	150.171.10.38^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns1-38.azure-dns.com`
NS	`ns2-38.azure-dns.net`
		A	2620:1ec:8ec:10::26^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-38.azure-dns.net`
		A	150.171.16.38^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-38.azure-dns.net`
NS	`ns3-38.azure-dns.org`
		A	2a01:111:4000:10::26^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-38.azure-dns.org`
		A	13.107.222.38^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns3-38.azure-dns.org`
NS	`ns4-38.azure-dns.info`
		A	2620:1ec:bda:10::26^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-38.azure-dns.info`
		A	13.107.206.38^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns4-38.azure-dns.info`
TXT	`v=spf1 -all`
SOA	`ns1-38.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=1774965997

Same first word

didconference.com

DNS History

8 records (4 active, 4 former)

●NSns1-38.azure-dns.com2026-02-28 → 2026-03-31 · 3 obs

○ 2020-01-17 21:17:18
● 2026-02-28 11:47:14
● 2026-03-31 14:10:04

●NSns2-38.azure-dns.net2026-02-28 → 2026-03-31 · 3 obs

○ 2020-01-17 21:17:18
● 2026-02-28 11:47:14
● 2026-03-31 14:10:04

○NSns25.worldnic.com2015-07-09 → 2020-01-17 · 4 obs

● 2015-07-09 04:12:02
● 2020-01-17 21:17:18
○ 2026-02-28 11:47:14
○ 2026-03-31 14:10:04

○NSns26.worldnic.com2015-07-09 → 2020-01-17 · 4 obs

● 2015-07-09 04:12:02
● 2020-01-17 21:17:18
○ 2026-02-28 11:47:14
○ 2026-03-31 14:10:04

●NSns3-38.azure-dns.org2026-02-28 → 2026-03-31 · 3 obs

○ 2020-01-17 21:17:18
● 2026-02-28 11:47:14
● 2026-03-31 14:10:04

●NSns4-38.azure-dns.info2026-02-28 → 2026-03-31 · 3 obs

○ 2020-01-17 21:17:18
● 2026-02-28 11:47:14
● 2026-03-31 14:10:04

○MXp.webcom.ctmail.com2015-11-28 → 2017-03-23 · 4 obs

● 2015-11-28 03:34:42
● 2017-03-23 09:54:44
○ 2020-01-17 21:17:18
○ 2026-03-31 14:10:04

○A205.178.189.1312015-07-09 → 2020-01-17 · 4 obs

● 2015-07-09 04:12:02
● 2020-01-17 21:17:18
○ 2026-02-28 11:47:14
○ 2026-03-31 14:10:04

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
didconference.com	ns4-38.azure-dns.info, ns3-38.azure-dns.org, ns2-38.azure-dns.net, ns1-38.azure-dns.com	2 records

✅ Authoritative Response

Server:150.171.10.38

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for didconference.com (unsigned zone)

⏱️ Timing

Total: 269ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns1-38.azure-dns.com, ns2-38.azure-dns.net...`
TXT	1	`v=spf1 -all`
SOA	1	`ns1-38.azure-dns.com azuredns-hostmaster`

📌 Glue Records Collected

Total: 2

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

Analysis

Name Servers

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

didconference.com at least partially shares name servers with other domains, including valuevillagelistens.com, brooksrunning.ie, ewc.jp, astrotravel.org and 52.217.48.in-addr.arpa.

Hosts with two IP numbers:

Host ns1-38.azure-dns.com points to 2603:1061:0:10::26 and 150.171.10.38

Host ns4-38.azure-dns.info points to 2620:1ec:bda:10::26 and 13.107.206.38

Host ns2-38.azure-dns.net points to 2620:1ec:8ec:10::26 and 150.171.16.38

Host ns3-38.azure-dns.org points to 2a01:111:4000:10::26 and 13.107.222.38

didconference.com - robtex.com