`roboticsurgeryexperts.com`

DNSSEC	⚠️ Not signed
A	216.68.236.89^{🇺🇸 RoadRunner216.68.236.0/24 ARIN Route Object for FUSE customer TriHealth}
		PTR	`trihealth-bethesda-hospital-216-68-236-89.static.fuse.net`
NS	`ns1-02.azure-dns.com` ⭐
		A	2603:1061:0:700::2^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-02.azure-dns.com`
		A	13.107.236.2^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-02.azure-dns.com`
NS	`ns2-02.azure-dns.net`
		A	2620:1ec:8ec:700::2^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-02.azure-dns.net`
		A	150.171.21.2^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-02.azure-dns.net`
NS	`ns3-02.azure-dns.org`
		A	2a01:111:4000:700::2^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-02.azure-dns.org`
		A	204.14.183.2^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-02.azure-dns.org`
NS	`ns4-02.azure-dns.info`
		A	2620:1ec:bda:700::2^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-02.azure-dns.info`
		A	208.84.5.2^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-02.azure-dns.info`
SOA	`ns1-02.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=1771291435

Same first word

roboticsurgeryexperts.com

DNS History

7 records (5 active, 2 former)

●NSns1-02.azure-dns.com2026-02-18 → 2026-03-24 · 3 obs

○ 2016-03-26 18:04:24
● 2026-02-18 00:06:38
● 2026-03-24 03:44:26

●NSns2-02.azure-dns.net2026-02-18 → 2026-03-24 · 3 obs

○ 2016-03-26 18:04:24
● 2026-02-18 00:06:38
● 2026-03-24 03:44:26

●NSns3-02.azure-dns.org2026-02-18 → 2026-03-24 · 3 obs

○ 2016-03-26 18:04:24
● 2026-02-18 00:06:38
● 2026-03-24 03:44:26

○NSns3.fuse.net2015-07-21 → 2016-03-26 · 4 obs

● 2015-07-21 22:46:26
● 2016-03-26 18:04:24
○ 2026-02-18 00:06:38
○ 2026-03-24 03:44:26

●NSns4-02.azure-dns.info2026-02-18 → 2026-03-24 · 3 obs

○ 2016-03-26 18:04:24
● 2026-02-18 00:06:38
● 2026-03-24 03:44:26

○NSns4.fuse.net2015-07-21 → 2016-03-26 · 4 obs

● 2015-07-21 22:46:26
● 2016-03-26 18:04:24
○ 2026-02-18 00:06:38
○ 2026-03-24 03:44:26

●A216.68.236.892015-07-21 → 2026-03-24 · 2 obs

● 2015-07-21 22:46:26
● 2026-03-24 03:44:26

🔍 DNS Trace

📋 Delegation Chain

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

✅ Authoritative Response

Server:208.84.5.2

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for roboticsurgeryexperts.com (unsigned zone)

⏱️ Timing

Total: 122ms | Queries: -

📄 Records

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

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

roboticsurgeryexperts.com resolves to one IP number: 216.68.236.89.

Name Servers

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

roboticsurgeryexperts.com at least partially shares name servers with other domains, for instance yrsel.nu, eschools.co.uk, dotnetmag.nl, jotel.com and americansafetycouncil.com.

Host names with two IP numbers:

ns1-02.azure-dns.com points to 2603:1061:0:700::2 and 13.107.236.2; ns4-02.azure-dns.info points to 2620:1ec:bda:700::2 and 208.84.5.2; ns2-02.azure-dns.net points to 2620:1ec:8ec:700::2 and 150.171.21.2; ns3-02.azure-dns.org points to 2a01:111:4000:700::2 and 204.14.183.2.

roboticsurgeryexperts.com - robtex.com