`ansysmissions.ml`

DNSSEC	⚠️ Not signed
A	192.104.24.52^{🇺🇸 AS53465192.104.24.0/24 ANSYS, Inc}
NS	`ns1-36.azure-dns.com` ⭐
		A	2603:1061:0:10::24^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-36.azure-dns.com`
		A	150.171.10.36^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns1-36.azure-dns.com`
NS	`ns2-36.azure-dns.net`
		A	2620:1ec:8ec:10::24^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-36.azure-dns.net`
		A	150.171.16.36^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-36.azure-dns.net`
NS	`ns3-36.azure-dns.org`
		A	2a01:111:4000:10::24^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-36.azure-dns.org`
		A	13.107.222.36^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns3-36.azure-dns.org`
NS	`ns4-36.azure-dns.info`
		A	2620:1ec:bda:10::24^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-36.azure-dns.info`
		A	13.107.206.36^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns4-36.azure-dns.info`
TXT	`v=spf1 -all`
SOA	`ns1-36.azure-dns.com`azuredns-hostmaster@microsoft.com serial=1

`ml`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns1.nic.ml` ⭐
	NS	`a.nic.ml`
	NS	`b.nic.ml`
	NS	`c.nic.ml`
	NS	`d.nic.ml`
	SOA	`ns1.nic.ml`supports@gouv.ml 2026-06-16 #12

Same first word

ansysmissions.ml

DNS History

5 records (5 active, 0 former)

●NSns1-36.azure-dns.com2026-05-19 → 2026-06-16 · 2 obs

● 2026-05-19 20:49:50
● 2026-06-16 12:59:14

●NSns2-36.azure-dns.net2026-05-19 → 2026-06-16 · 2 obs

● 2026-05-19 20:49:50
● 2026-06-16 12:59:14

●NSns3-36.azure-dns.org2026-05-19 → 2026-06-16 · 2 obs

● 2026-05-19 20:49:50
● 2026-06-16 12:59:14

●NSns4-36.azure-dns.info2026-05-19 → 2026-06-16 · 2 obs

● 2026-05-19 20:49:50
● 2026-06-16 12:59:14

●A192.104.24.522026-05-19 → 2026-06-16 · 2 obs

● 2026-05-19 20:49:50
● 2026-06-16 12:59:14

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
ml	a.nic.ml, b.nic.ml, c.nic.ml, d.nic.ml	7 records
ansysmissions.ml	ns1-36.azure-dns.com, ns2-36.azure-dns.net, ns3-36.azure-dns.org, ns4-36.azure-dns.info	-

✅ Authoritative Response

Server:13.107.222.36

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for ansysmissions.ml (unsigned zone)

⏱️ Timing

Total: 1041ms | Queries: -

📄 Records

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

📌 Glue Records Collected

Total: 7

In-bailiwick: 7 (a.nic.ml, b.nic.ml, b.nic.ml...)

Analysis

IP Addresses

ansysmissions.ml resolves to one IP address: 192.104.24.52.

livermoresoftware.com, www.ansoft.com, dynamore.se and two other host names share IP numbers with ansysmissions.ml.

Name Servers

The authoritative name servers for ansysmissions.ml are ns1-36.azure-dns.com, ns4-36.azure-dns.info, ns2-36.azure-dns.net and ns3-36.azure-dns.org.

At least some of ansysmissions.ml's name servers are shared with other domains, for example openai-staging.com, cisrussia.com, bluewaterhealth.com and two more.

Four hostnames, each resolving to a pair of IP addresses: ns1-36.azure-dns.com directs to 150.171.10.36 and 2603:1061:0:10::24; ns4-36.azure-dns.info directs to 13.107.206.36 and 2620:1ec:bda:10::24; ns2-36.azure-dns.net directs to 150.171.16.36 and 2620:1ec:8ec:10::24; ns3-36.azure-dns.org directs to 13.107.222.36 and 2a01:111:4000:10::24.

ansysmissions.ml - robtex.com