`managedmeeting.com`

DNSSEC	⚠️ Not signed
A	176.122.23.42^{🇷🇺 ITGRAD176.122.23.0/24}
		PTR	`strat-wallet.com`
NS	`ns1.digitalocean.com` ⭐
		A	2606:4700:52::ac40:34d2^{🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.digitalocean.com`
		A	172.64.52.210^{🇺🇸 Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.digitalocean.com`
NS	`ns2.digitalocean.com`
		A	2606:4700:5a::ac40:3515^{🇺🇸 Cloudflare2606:4700:5a::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.digitalocean.com`
		A	172.64.53.21^{🇺🇸 Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.digitalocean.com`
NS	`ns3.digitalocean.com`
		A	2606:4700:52::ac40:31d1^{🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns3.digitalocean.com`
		A	172.64.49.209^{🇺🇸 Cloudflare172.64.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns3.digitalocean.com`
TXT	`v=spf1 a mx ip4:37.228.117.111 ~all`
SOA	`ns1.digitalocean.com`hostmaster@managedmeeting.com serial=1635064730

`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

managedmeeting.com

DNS History

5 records (4 active, 1 former)

●NSns1.digitalocean.com2026-03-21 → 2026-03-21 · 1 obs

● 2026-03-21 09:39:04

●NSns2.digitalocean.com2026-03-21 → 2026-03-21 · 1 obs

● 2026-03-21 09:39:04

●NSns3.digitalocean.com2026-03-21 → 2026-03-21 · 1 obs

● 2026-03-21 09:39:04

●A176.122.23.422026-03-21 → 2026-03-21 · 2 obs

○ 2016-01-19 00:44:28
● 2026-03-21 09:39:04

○A74.220.199.82015-05-12 → 2016-01-19 · 3 obs

● 2015-05-12 16:08:40
● 2016-01-19 00:44:28
○ 2026-03-21 09:39: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...	-
managedmeeting.com	ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com	3 records

✅ Authoritative Response

Server: 172.64.52.210

NS records: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for managedmeeting.com (unsigned zone)

⏱️ Timing

Total: 185ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`176.122.23.42`
NS	3	`ns3.digitalocean.com, ns1.digitalocean.com...`
TXT	1	`v=spf1 a mx ip4:37.228.117.111 ~all`
SOA	1	`ns1.digitalocean.com hostmaster.managedm`

📌 Glue Records Collected

Total: 3

Out-of-bailiwick: 3 (ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com)

Analysis

IP Addresses

managedmeeting.com points to a single IP number: 176.122.23.42.

Other host names, for instance accuracyprone.com, share IP numbers with managedmeeting.com.

Name Servers

The domain managedmeeting.com is delegated to three name servers: ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com.

managedmeeting.com shares name servers with other domains at least partially, for instance infokotapalu.id, zeaara.com, 189.232.165.in-addr.arpa, www.arcrebel.com and zemlan.in.

Host names with two IP numbers:

ns1.digitalocean.com points to 2606:4700:52::ac40:34d2 and 172.64.52.210

ns2.digitalocean.com points to 2606:4700:5a::ac40:3515 and 172.64.53.21

ns3.digitalocean.com points to 2606:4700:52::ac40:31d1 and 172.64.49.209

managedmeeting.com - robtex.com