`myclaimtoday.com`

DNSSEC	⚠️ Not signed
NS	`ns1-09.azure-dns.com` ⭐
		A	2603:1061:0:700::9^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-09.azure-dns.com`
		A	13.107.236.9^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-09.azure-dns.com`
NS	`ns2-09.azure-dns.net`
		A	2620:1ec:8ec:700::9^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-09.azure-dns.net`
		A	150.171.21.9^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-09.azure-dns.net`
NS	`ns3-09.azure-dns.org`
		A	2a01:111:4000:700::9^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-09.azure-dns.org`
		A	204.14.183.9^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-09.azure-dns.org`
NS	`ns4-09.azure-dns.info`
		A	2620:1ec:bda:700::9^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-09.azure-dns.info`
		A	208.84.5.9^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-09.azure-dns.info`
TXT	`godaddyverification=dNa/e9/W3CPk/ZDqBk9RmQ==`
SOA	`ns1-09.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=1776167022

Same first word

myclaimtoday.com

DNS History

4 records (4 active, 0 former)

●NSns1-09.azure-dns.com2020-03-17 → 2026-04-14 · 2 obs

● 2020-03-17 14:56:10
● 2026-04-14 12:03:46

●NSns2-09.azure-dns.net2020-03-17 → 2026-04-14 · 2 obs

● 2020-03-17 14:56:10
● 2026-04-14 12:03:46

●NSns3-09.azure-dns.org2020-03-17 → 2026-04-14 · 2 obs

● 2020-03-17 14:56:10
● 2026-04-14 12:03:46

●NSns4-09.azure-dns.info2020-03-17 → 2026-04-14 · 2 obs

● 2020-03-17 14:56:10
● 2026-04-14 12:03:46

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	h.gtld-servers.net, e.gtld-servers.net, k.gtld-servers.net, g.gtld-servers.net...	-
myclaimtoday.com	ns1-09.azure-dns.com, ns2-09.azure-dns.net, ns3-09.azure-dns.org, ns4-09.azure-dns.info	2 records

✅ Authoritative Response

Server:13.107.236.9

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for myclaimtoday.com (unsigned zone)

⏱️ Timing

Total: 257ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns1-09.azure-dns.com, ns2-09.azure-dns.net...`
TXT	1	`godaddyverification=dNa/e9/W3CPk/ZDqBk9R`
SOA	1	`ns1-09.azure-dns.com azuredns-hostmaster`

📌 Glue Records Collected

Total: 2

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

Analysis

Name Servers

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

myclaimtoday.com at least partially shares name servers with other domains, for instance bingnetworks.jp, nordicequities.se, mercantilsi.com.pa, radiora.com and atb.net.au.

Host names with two IP numbers:

ns1-09.azure-dns.com points to 2603:1061:0:700::9 and 13.107.236.9; ns4-09.azure-dns.info points to 2620:1ec:bda:700::9 and 208.84.5.9; ns2-09.azure-dns.net points to 2620:1ec:8ec:700::9 and 150.171.21.9; ns3-09.azure-dns.org points to 2a01:111:4000:700::9 and 204.14.183.9.

myclaimtoday.com - robtex.com