`rose-security.com`

DNSSEC	⚠️ Not signed
A	108.61.172.189^{🇬🇧 AS-VULTR108.61.172.0/22 Vultr Assigned Prefix}
		PTR	`rose-security.com`
NS	`ns1.hover.com` ⭐
		A	2604:4000:0:d:216:40:47:26^{🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000}
			PTR	`ns1.hover.com`
		A	216.40.47.26^{🇨🇦 TUCOWS216.40.47.0/24 -BRA-BLK1.4/NET-216-40-47-0}
			PTR	`ns1.hover.com`
NS	`ns2.hover.com`
		A	2604:4000:2800:d:64:99:148:13^{🇨🇦 TUCOWS-32604:4000:2800::/37 Tucows.com Co.}
			PTR	`ns2.hover.com`
		A	64.98.148.13^{🇨🇦 TUCOWS-364.98.144.0/20 Tucows.com Co.}
			PTR	`ns2.hover.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c08::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bi-in-f26.1e100.net`
		A	142.251.16.26^{🇺🇸 Google142.251.16.0/24}
			PTR	`bl-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽²⁰⁾
		A	2800:3f0:4003:c0f::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽²⁰⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
MX	`aspmx2.googlemail.com`⁽³⁰⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.26^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f26.1e100.net`
MX	`aspmx3.googlemail.com`⁽³⁰⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
SOA	`ns1.hover.com`dnsmaster@hover.com serial=1720467934

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

PTR for

189.172.61.108.in-addr.arpa

Same first word

rose-security.com

DNS History

8 records (8 active, 0 former)

●NSns1.hover.com2015-07-08 → 2026-07-23 · 3 obs

○ 2008-03-18 22:13:26
● 2015-07-08 23:37:08
● 2026-07-23 22:54:02

●NSns2.hover.com2015-07-08 → 2026-07-23 · 3 obs

○ 2008-03-18 22:13:26
● 2015-07-08 23:37:08
● 2026-07-23 22:54:02

●MXalt1.aspmx.l.google.com2015-07-08 → 2026-07-23 · 3 obs

○ 2008-03-18 22:13:26
● 2015-07-08 23:37:08
● 2026-07-23 22:54:02

●MXalt2.aspmx.l.google.com2015-07-08 → 2026-07-23 · 3 obs

○ 2008-03-18 22:13:26
● 2015-07-08 23:37:08
● 2026-07-23 22:54:02

●MXaspmx.l.google.com2015-07-08 → 2026-07-23 · 3 obs

○ 2008-03-18 22:13:26
● 2015-07-08 23:37:08
● 2026-07-23 22:54:02

●MXaspmx2.googlemail.com2015-07-08 → 2026-07-23 · 3 obs

○ 2008-03-18 22:13:26
● 2015-07-08 23:37:08
● 2026-07-23 22:54:02

●MXaspmx3.googlemail.com2015-07-08 → 2026-07-23 · 3 obs

○ 2008-03-18 22:13:26
● 2015-07-08 23:37:08
● 2026-07-23 22:54:02

●A108.61.172.1892015-07-08 → 2026-07-23 · 3 obs

○ 2008-03-18 22:13:26
● 2015-07-08 23:37:08
● 2026-07-23 22:54:02

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
rose-security.com	ns1.hover.com, ns2.hover.com	4 records

✅ Authoritative Response

Server:216.40.47.26

NS records: ns1.hover.com, ns2.hover.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for rose-security.com (unsigned zone)

⏱️ Timing

Total: 274ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`108.61.172.189`
NS	2	`ns1.hover.com, ns2.hover.com`
MX	5	`alt2.aspmx.l.google.com (pri: 20), alt1.aspmx.l.google.com (pri: 20)...`
SOA	1	`ns1.hover.com dnsmaster.hover.com`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns1.hover.com, ns1.hover.com, ns2.hover.com...)

Analysis

IP Addresses

rose-security.com resolves to just one IP address, 108.61.172.189.

Host names like decentgravy.com are further examples that share IP numbers with rose-security.com.

Name Servers

Two name servers handle the delegation for rose-security.com: ns1.hover.com and ns2.hover.com.

rose-security.com shares its NS records with other domains, for example wellink.ca, parklandhomevalues.info, israelacademicpress.com and two others.

The name servers of rose-security.com overlap at least partially with those of other domains — among them rotlo.com, beavis2000.com, nompute.com and two more.

These name servers commonly co-occur with the name servers ns3.hover.com, ns1.domaindirect.com, ns2.domaindirect.com and ns3.domaindirect.com.

ns1.hover.com and ns2.hover.com both carry two IP addresses. The A records for ns1.hover.com are 216.40.47.26 and 2604:4000:0:d:216:40:47:26; the A records for ns2.hover.com are 64.98.148.13 and 2604:4000:2800:d:64:99:148:13.

Mail Servers

Five mail servers handle rose-security.com: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.

There is at least a partial MX overlap between rose-security.com and other domains, including the-haymaker.com, garmin.com.pe, amzpro.io and two others.

These mail servers tend to appear in combination with mail servers alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.

Host names that have two IP addresses:

aspmx2.googlemail.com resolves to two addresses: 108.177.123.26 and 2800:3f0:4003:c0f::1a.

aspmx3.googlemail.com resolves to two addresses: 172.253.116.27 and 2a00:1450:400b:c02::1b.

aspmx.l.google.com resolves to two addresses: 142.251.16.26 and 2607:f8b0:4004:c08::1a.

alt1.aspmx.l.google.com resolves to two addresses: 108.177.123.27 and 2800:3f0:4003:c0f::1b.

alt2.aspmx.l.google.com resolves to two addresses: 172.253.116.26 and 2a00:1450:400b:c02::1a.