`rmz-me.com`

DNSSEC	⚠️ Not signed
A	68.183.237.201^{🇸🇬 DIGITALOCEAN68.183.224.0/20 DigitalOcean}
		PTR	`rmz-me.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`
SOA	`ns1.digitalocean.com`hostmaster@rmz-me.com serial=1612259117

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

PTR for

201.237.183.68.in-addr.arpa

Same first word

rmz-me.com

DNS History

18 records (4 active, 14 former)

○NSconnie.ns.cloudflare.com2018-09-13 → 2018-09-13 · 3 obs

○ 2017-01-15 17:53:44
● 2018-09-13 15:15:48
○ 2026-03-28 10:34:16

○NSjoel.ns.cloudflare.com2018-09-13 → 2018-09-13 · 3 obs

○ 2017-01-15 17:53:44
● 2018-09-13 15:15:48
○ 2026-03-28 10:34:16

○NSlocalhost2016-11-27 → 2017-01-15 · 5 obs

○ 2016-08-22 08:06:20
● 2016-11-27 16:04:50
● 2017-01-15 17:53:44
○ 2018-09-13 15:15:48
○ 2026-03-28 10:34:16

●NSns1.digitalocean.com2026-03-28 → 2026-03-28 · 2 obs

○ 2018-09-13 15:15:48
● 2026-03-28 10:34:16

○NSns1.easycgi.com2015-09-02 → 2016-06-08 · 4 obs

● 2015-09-02 15:47:30
● 2016-06-08 08:42:32
○ 2016-08-22 08:06:20
○ 2026-03-28 10:34:16

○NSns1.mytrafficmanagement.com2016-11-27 → 2017-01-15 · 5 obs

○ 2016-08-22 08:06:20
● 2016-11-27 16:04:50
● 2017-01-15 17:53:44
○ 2018-09-13 15:15:48
○ 2026-03-28 10:34:16

●NSns2.digitalocean.com2026-03-28 → 2026-03-28 · 2 obs

○ 2018-09-13 15:15:48
● 2026-03-28 10:34:16

○NSns2.easycgi.com2015-09-02 → 2016-06-08 · 4 obs

● 2015-09-02 15:47:30
● 2016-06-08 08:42:32
○ 2016-08-22 08:06:20
○ 2026-03-28 10:34:16

○NSns2.mytrafficmanagement.com2016-11-27 → 2017-01-15 · 5 obs

○ 2016-08-22 08:06:20
● 2016-11-27 16:04:50
● 2017-01-15 17:53:44
○ 2018-09-13 15:15:48
○ 2026-03-28 10:34:16

●NSns3.digitalocean.com2026-03-28 → 2026-03-28 · 2 obs

○ 2018-09-13 15:15:48
● 2026-03-28 10:34:16

○MXmx.rmz-me.com2015-09-02 → 2016-06-08 · 4 obs

● 2015-09-02 15:47:30
● 2016-06-08 08:42:32
○ 2016-08-22 08:06:20
○ 2026-03-28 10:34:16

○A104.130.124.962016-11-27 → 2017-01-15 · 5 obs

○ 2016-08-22 08:06:20
● 2016-11-27 16:04:50
● 2017-01-15 17:53:44
○ 2018-09-13 15:15:48
○ 2026-03-28 10:34:16

○A104.24.102.932018-09-13 → 2018-09-13 · 3 obs

○ 2017-01-15 17:53:44
● 2018-09-13 15:15:48
○ 2026-03-28 10:34:16

○A104.24.103.932018-09-13 → 2018-09-13 · 3 obs

○ 2017-01-15 17:53:44
● 2018-09-13 15:15:48
○ 2026-03-28 10:34:16

○A2400:cb00:2048:1::6818:665d2018-09-13 → 2018-09-13 · 3 obs

○ 2017-01-15 17:53:44
● 2018-09-13 15:15:48
○ 2026-03-28 10:34:16

○A2400:cb00:2048:1::6818:675d2018-09-13 → 2018-09-13 · 3 obs

○ 2017-01-15 17:53:44
● 2018-09-13 15:15:48
○ 2026-03-28 10:34:16

○A66.96.143.1662015-09-02 → 2016-06-08 · 4 obs

● 2015-09-02 15:47:30
● 2016-06-08 08:42:32
○ 2016-08-22 08:06:20
○ 2026-03-28 10:34:16

●A68.183.237.2012026-03-28 → 2026-03-28 · 2 obs

○ 2018-09-13 15:15:48
● 2026-03-28 10:34:16

🔍 DNS Trace

📋 Delegation Chain

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

⏱️ Timing

Total: 319ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`68.183.237.201`
NS	3	`ns1.digitalocean.com, ns2.digitalocean.com...`
SOA	1	`ns1.digitalocean.com hostmaster.rmz-me.c`

📌 Glue Records Collected

Total: 3

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

Analysis

IP Addresses

rmz-me.com points to IP number 68.183.237.201.

Name Servers

The delegation for rmz-me.com is handled by three name servers: ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com.

rmz-me.com shares name servers with other domains at least partially, for example 6.68.138.in-addr.arpa, ejpreciado.com, aerocare.es, metroidhq.com and solomonmok.com.

Host names with two IPs:

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

rmz-me.com - robtex.com

rmz-me.com

com

PTR for

Same first word

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

📌 Glue Records Collected

Analysis

IP Addresses

Name Servers

`rmz-me.com`

`com`