`registrybot.com`

DNSSEC	⚠️ Not signed
A	3.33.139.32^{🇺🇸 Amazon3.33.128.0/20}
		PTR	`aeedc42b70c898c66.awsglobalaccelerator.com`
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`
SOA	`ns1.markmonitor.com`hostmaster@markmonitor.com 2022-10-11 #3

`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=1776058567

WOT: SAFE (29/100)

Subdomains

download.registrybot.com

Same first word

registrybot.com

Similar names

tegrybistro.com

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net...	-
registrybot.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 registrybot.com (unsigned zone)

⏱️ Timing

Total: 543ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`3.33.139.32`
NS	4	`ns1.markmonitor.com, ns2.markmonitor.com...`
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

Hierarchy

The parent of download.registrybot.com is registrybot.com.

IP Addresses

registrybot.com points to a single IP number: 3.33.139.32.

Other host names, for instance amazonn.info, amazon-payment-center.com, neimanbarcusonline.us, www.reebok.ch and cpmpetitivecyclist.com share IP numbers with registrybot.com.

Name Servers

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

registrybot.com shares name servers with other domains at least partially, for instance fortinet.ml, rentalcard.mx, creditkarmaisruiningmydealio.com, bestbuyyellowcard.info and pypl.co.

these name servers are often used with ns5.markmonitor.com, ns6.markmonitor.com and ns7.markmonitor.com.

Host names with two IP numbers:

ns1.markmonitor.com resolves to 2620:10a:80a8::1 and 149.112.160.1.

ns2.markmonitor.com resolves to 2001:67c:10b8::1 and 176.97.158.1.

ns3.markmonitor.com resolves to 2620:10a:80a9::1 and 149.112.161.1.

ns4.markmonitor.com resolves to 2001:67c:1bc::1 and 192.174.68.1.

registrybot.com - robtex.com

registrybot.com

com