🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`availabilityoptimizer.com`

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

Same first word

availabilityoptimizer.com

Previous names

Next names

DNS History

17 records (4 active, 13 former)

●NSns1-35.azure-dns.com2026-02-28 → 2026-08-25 · 3 obs

○ 2018-06-02 19:32:02
● 2026-02-28 14:09:02
● 2026-08-25 08:48:42

○NSns1.markmonitor.com2018-06-02 → 2018-06-02 · 4 obs

○ 2016-12-30 16:14:36
● 2018-06-02 19:32:02
○ 2026-02-28 14:09:02
○ 2026-08-25 08:48:42

●NSns2-35.azure-dns.net2026-02-28 → 2026-08-25 · 3 obs

○ 2018-06-02 19:32:02
● 2026-02-28 14:09:02
● 2026-08-25 08:48:42

○NSns2.markmonitor.com2018-06-02 → 2018-06-02 · 4 obs

○ 2016-12-30 16:14:36
● 2018-06-02 19:32:02
○ 2026-02-28 14:09:02
○ 2026-08-25 08:48:42

●NSns3-35.azure-dns.org2026-02-28 → 2026-08-25 · 3 obs

○ 2018-06-02 19:32:02
● 2026-02-28 14:09:02
● 2026-08-25 08:48:42

○NSns3.markmonitor.com2018-06-02 → 2018-06-02 · 4 obs

○ 2016-12-30 16:14:36
● 2018-06-02 19:32:02
○ 2026-02-28 14:09:02
○ 2026-08-25 08:48:42

●NSns4-35.azure-dns.info2026-02-28 → 2026-08-25 · 3 obs

○ 2018-06-02 19:32:02
● 2026-02-28 14:09:02
● 2026-08-25 08:48:42

○NSns4.markmonitor.com2018-06-02 → 2018-06-02 · 4 obs

○ 2016-12-30 16:14:36
● 2018-06-02 19:32:02
○ 2026-02-28 14:09:02
○ 2026-08-25 08:48:42

○NSns5.markmonitor.com2018-06-02 → 2018-06-02 · 4 obs

○ 2016-12-30 16:14:36
● 2018-06-02 19:32:02
○ 2026-02-28 14:09:02
○ 2026-08-25 08:48:42

○NSns57.1and1.com2015-06-12 → 2016-12-30 · 4 obs

● 2015-06-12 04:28:14
● 2016-12-30 16:14:36
○ 2018-06-02 19:32:02
○ 2026-08-25 08:48:42

○NSns58.1and1.com2015-06-12 → 2016-12-30 · 4 obs

● 2015-06-12 04:28:14
● 2016-12-30 16:14:36
○ 2018-06-02 19:32:02
○ 2026-08-25 08:48:42

○NSns6.markmonitor.com2018-06-02 → 2018-06-02 · 4 obs

○ 2016-12-30 16:14:36
● 2018-06-02 19:32:02
○ 2026-02-28 14:09:02
○ 2026-08-25 08:48:42

○NSns7.markmonitor.com2018-06-02 → 2018-06-02 · 4 obs

○ 2016-12-30 16:14:36
● 2018-06-02 19:32:02
○ 2026-02-28 14:09:02
○ 2026-08-25 08:48:42

○MXmx00.1and1.com2015-06-12 → 2016-12-30 · 4 obs

● 2015-06-12 04:28:14
● 2016-12-30 16:14:36
○ 2018-06-02 19:32:02
○ 2026-08-25 08:48:42

○MXmx01.1and1.com2015-06-12 → 2016-12-30 · 4 obs

● 2015-06-12 04:28:14
● 2016-12-30 16:14:36
○ 2018-06-02 19:32:02
○ 2026-08-25 08:48:42

○A72.52.10.142018-06-02 → 2018-06-02 · 4 obs

○ 2016-12-30 16:14:36
● 2018-06-02 19:32:02
○ 2026-02-28 14:09:02
○ 2026-08-25 08:48:42

○A74.208.19.1372015-06-12 → 2016-12-30 · 4 obs

● 2015-06-12 04:28:14
● 2016-12-30 16:14:36
○ 2018-06-02 19:32:02
○ 2026-08-25 08:48:42

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	c.gtld-servers.net, b.gtld-servers.net, g.gtld-servers.net, m.gtld-servers.net...	-
availabilityoptimizer.com	ns1-35.azure-dns.com, ns2-35.azure-dns.net, ns3-35.azure-dns.org, ns4-35.azure-dns.info	2 records

✅ Authoritative Response

Server:13.107.206.35

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for availabilityoptimizer.com (unsigned zone)

⏱️ Timing

Total: 341ms | Queries: -

📄 Records

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

📌 Glue Records Collected

Total: 2

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

Analysis

Name Servers

The NS records for availabilityoptimizer.com point to four name servers: ns1-35.azure-dns.com, ns4-35.azure-dns.info, ns2-35.azure-dns.net and ns3-35.azure-dns.org.

At least some of availabilityoptimizer.com's name servers are shared with other domains, for example perfininvestimentos.com.br, stmarysamarillo.com, 125.237.135.in-addr.arpa and two more.

Four hostnames, each resolving to a pair of IP addresses: ns1-35.azure-dns.com directs to 150.171.10.35 and 2603:1061:0:10::23; ns4-35.azure-dns.info directs to 13.107.206.35 and 2620:1ec:bda:10::23; ns2-35.azure-dns.net directs to 150.171.16.35 and 2620:1ec:8ec:10::23; ns3-35.azure-dns.org directs to 13.107.222.35 and 2a01:111:4000:10::23.

availabilityoptimizer.com - robtex.com