`managed500index.com`

DNSSEC	⚠️ Not signed
A	127.0.0.1
NS	`ns1.markmonitor.com` ⭐
		A	2620:10a:80a8::1^{🇨🇦 CIRA-22620:10a:80a8::/48 markmonitor v6 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
		A	149.112.160.1^{🇨🇦 CIRA-2149.112.160.0/24 markmonitor v4 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
NS	`ns2.markmonitor.com`
		A	2001:67c:10b8::1^{🇨🇭 RCODEZERO-ANYCAST-SEC22001:67c:10b8::/48 IPCOM-anycast-net}
			PTR	`ns2.markmonitor.com`
		A	176.97.158.1^{🇦🇹 RCODEZERO-ANYCAST-SEC2176.97.158.0/24 NICat-anycast-net}
			PTR	`ns2.markmonitor.com`
NS	`ns3.markmonitor.com`
		A	2620:10a:80a9::1^{🇨🇦 CIRA-32620:10a:80a9::/48 markmonitor v6 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
		A	149.112.161.1^{🇨🇦 CIRA-3149.112.161.0/24 markmonitor v4 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
NS	`ns4.markmonitor.com`
		A	2001:67c:1bc::1^{🇦🇹 RCODEZERO-ANYCAST-SEC1-TLD2001:67c:1bc::/48 IPCom-NET Anycast}
			PTR	`ns1.markmonitor.com`
		A	192.174.68.1^{🇦🇹 RCODEZERO-ANYCAST-SEC1-TLD192.174.68.0/24 NICat-anycast-net}
			PTR	`ns1.markmonitor.com`
TXT	`v=spf1 -all`
SOA	`ns1.markmonitor.com`hostmaster@markmonitor.com 2025-12-15 #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=1774562372

Same first word

managed500index.com

DNS History

15 records (5 active, 10 former)

●NSns1.markmonitor.com2026-02-27 → 2026-03-26 · 3 obs

○ 2017-11-29 12:59:08
● 2026-02-27 03:59:38
● 2026-03-26 22:15:10

○NSns1.p50.dynect.net2016-01-19 → 2017-11-29 · 5 obs

○ 2015-07-19 01:05:00
● 2016-01-19 04:51:44
● 2017-11-29 12:59:08
○ 2026-02-27 03:59:38
○ 2026-03-26 22:15:10

○NSns1.tdameritrade.com2016-12-23 → 2017-11-29 · 5 obs

○ 2016-04-28 11:10:32
● 2016-12-23 04:06:00
● 2017-11-29 12:59:08
○ 2026-02-27 03:59:38
○ 2026-03-26 22:15:10

●NSns2.markmonitor.com2026-02-27 → 2026-03-26 · 3 obs

○ 2017-11-29 12:59:08
● 2026-02-27 03:59:38
● 2026-03-26 22:15:10

○NSns2.p50.dynect.net2016-01-19 → 2017-11-29 · 5 obs

○ 2015-07-19 01:05:00
● 2016-01-19 04:51:44
● 2017-11-29 12:59:08
○ 2026-02-27 03:59:38
○ 2026-03-26 22:15:10

●NSns3.markmonitor.com2026-02-27 → 2026-03-26 · 3 obs

○ 2017-11-29 12:59:08
● 2026-02-27 03:59:38
● 2026-03-26 22:15:10

○NSns3.p50.dynect.net2016-01-19 → 2017-11-29 · 5 obs

○ 2015-07-19 01:05:00
● 2016-01-19 04:51:44
● 2017-11-29 12:59:08
○ 2026-02-27 03:59:38
○ 2026-03-26 22:15:10

●NSns4.markmonitor.com2026-02-27 → 2026-03-26 · 3 obs

○ 2017-11-29 12:59:08
● 2026-02-27 03:59:38
● 2026-03-26 22:15:10

○NSns4.p50.dynect.net2016-01-19 → 2017-11-29 · 5 obs

○ 2015-07-19 01:05:00
● 2016-01-19 04:51:44
● 2017-11-29 12:59:08
○ 2026-02-27 03:59:38
○ 2026-03-26 22:15:10

○NSpdns151.ultradns.biz2015-07-19 → 2017-11-29 · 4 obs

● 2015-07-19 01:05:00
● 2017-11-29 12:59:08
○ 2026-02-27 03:59:38
○ 2026-03-26 22:15:10

○NSpdns151.ultradns.com2015-07-19 → 2017-11-29 · 6 obs

● 2015-07-19 01:05:00
● 2016-04-28 11:10:32
○ 2016-12-23 04:06:00
● 2017-11-29 12:59:08
○ 2026-02-27 03:59:38
○ 2026-03-26 22:15:10

○NSpdns151.ultradns.net2015-07-19 → 2017-11-29 · 4 obs

● 2015-07-19 01:05:00
● 2017-11-29 12:59:08
○ 2026-02-27 03:59:38
○ 2026-03-26 22:15:10

○NSpdns151.ultradns.org2015-07-19 → 2017-11-29 · 4 obs

● 2015-07-19 01:05:00
● 2017-11-29 12:59:08
○ 2026-02-27 03:59:38
○ 2026-03-26 22:15:10

●A127.0.0.12026-02-27 → 2026-03-26 · 3 obs

○ 2017-11-29 12:59:08
● 2026-02-27 03:59:38
● 2026-03-26 22:15:10

○A216.105.251.2032015-07-19 → 2017-11-29 · 4 obs

● 2015-07-19 01:05:00
● 2017-11-29 12:59:08
○ 2026-02-27 03:59:38
○ 2026-03-26 22:15:10

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
managed500index.com	ns1.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com, ns2.markmonitor.com	8 records

✅ Authoritative Response

Server:149.112.160.1

NS records: ns1.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com, ns2.markmonitor.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for managed500index.com (unsigned zone)

⏱️ Timing

Total: 311ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`127.0.0.1`
NS	4	`ns1.markmonitor.com, ns2.markmonitor.com...`
TXT	1	`v=spf1 -all`
SOA	1	`ns1.markmonitor.com hostmaster.markmonit`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns1.markmonitor.com, ns1.markmonitor.com, ns3.markmonitor.com...)

Analysis

IP Addresses

managed500index.com points to a single IP number: 127.0.0.1.

other host names for instance 0.0.0.0.0.0.0.0.0.0.0.0.8.0.0.0.0.b.8.0.0.b.8.0.1.0.0.2.ip6.arpa, 181.0.85.dynamic.wline.res.cust.swisscom.ch, mail.microsysteme.de, 182.163.static.quadranet.com and www.w-2pp2p6.www.kusiqitoys.com share IP numbers with managed500index.com.

Name Servers

managed500index.com is delegated to four name servers: ns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com and ns4.markmonitor.com.

managed500index.com at least partially shares name servers with other domains, for instance wellsfargochampionship.com, ihg.ma, btgpactual.biz, swedishmatch.co.at and ihgrewards.com.cn.

These name servers are commonly used with ns5.markmonitor.com, ns6.markmonitor.com and ns7.markmonitor.com.

Host names with two IP numbers:

Host name ns1.markmonitor.com points to: 2620:10a:80a8::1 and 149.112.160.1.

Host name ns2.markmonitor.com points to: 2001:67c:10b8::1 and 176.97.158.1.

Host name ns3.markmonitor.com points to: 2620:10a:80a9::1 and 149.112.161.1.

Host name ns4.markmonitor.com points to: 2001:67c:1bc::1 and 192.174.68.1.

managed500index.com - robtex.com