🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`flovver.com`

DNSSEC	⚠️ Not signed
A	50.16.35.210^{🇺🇸 Amazon50.16.0.0/16 EC2 IAD prefix}
		PTR	`ec2-50-16-35-210.compute-1.amazonaws.com`
NS	`ns51.domaincontrol.com` ⭐
		A	2603:5:2192::1a^{🇺🇸 GODADDY-DNS2603:5:2190::/44}
			PTR	`ns51.domaincontrol.com`
		A	97.74.105.26^{🇺🇸 GODADDY-DNS97.74.104.0/23}
			PTR	`ns51.domaincontrol.com`
NS	`ns52.domaincontrol.com`
		A	2603:5:2292::1a^{🇺🇸 GODADDY-DNS2603:5:2290::/44}
			PTR	`ns52.domaincontrol.com`
		A	173.201.73.26^{🇺🇸 GODADDY-DNS173.201.72.0/23}
			PTR	`ns52.domaincontrol.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c06::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bg-in-f26.1e100.net`
		A	64.233.180.26^{🇺🇸 Google64.233.180.0/24}
			PTR	`on-in-f26.1e100.net`
			PTR	`pe-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c14::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.27^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-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.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
TXT	`v=spf1 include:_spf.google.com include:mail.zendesk.com include:amazonses.com...`
SOA	`ns51.domaincontrol.com`dns@jomax.net 2025-11-21 #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=1786951974

WOT: SAFE (70/100)

Same first word

flovver.com

Similar names

vervolf.blogspot.ru

DNS History

24 records (6 active, 18 former)

○NSns1.dsredirection.com2015-12-06 → 2016-04-04 · 5 obs

○ 2015-08-17 20:51:08
● 2015-12-06 13:07:14
● 2016-04-04 06:16:40
○ 2016-11-25 08:08:24
○ 2026-08-17 08:00:34

○NSns1.fastpark.net2008-03-17 → 2008-03-17 · 3 obs

● 2008-03-17 07:31:48
○ 2015-08-17 20:51:08
○ 2026-08-17 08:00:34

○NSns1.namebrightdns.com2017-07-09 → 2017-07-09 · 4 obs

○ 2016-11-25 08:08:24
● 2017-07-09 17:28:34
○ 2026-06-04 20:44:24
○ 2026-08-17 08:00:34

○NSns2.dsredirection.com2015-12-06 → 2016-04-04 · 5 obs

○ 2015-08-17 20:51:08
● 2015-12-06 13:07:14
● 2016-04-04 06:16:40
○ 2016-11-25 08:08:24
○ 2026-08-17 08:00:34

○NSns2.fastpark.net2008-03-17 → 2008-03-17 · 3 obs

● 2008-03-17 07:31:48
○ 2015-08-17 20:51:08
○ 2026-08-17 08:00:34

○NSns2.namebrightdns.com2017-07-09 → 2017-07-09 · 4 obs

○ 2016-11-25 08:08:24
● 2017-07-09 17:28:34
○ 2026-06-04 20:44:24
○ 2026-08-17 08:00:34

●NSns51.domaincontrol.com2026-06-04 → 2026-08-17 · 3 obs

○ 2017-07-09 17:28:34
● 2026-06-04 20:44:24
● 2026-08-17 08:00:34

●NSns52.domaincontrol.com2026-06-04 → 2026-08-17 · 3 obs

○ 2017-07-09 17:28:34
● 2026-06-04 20:44:24
● 2026-08-17 08:00:34

●MXalt1.aspmx.l.google.com2026-06-04 → 2026-08-17 · 3 obs

○ 2017-07-09 17:28:34
● 2026-06-04 20:44:24
● 2026-08-17 08:00:34

●MXalt2.aspmx.l.google.com2026-06-04 → 2026-08-17 · 3 obs

○ 2017-07-09 17:28:34
● 2026-06-04 20:44:24
● 2026-08-17 08:00:34

●MXaspmx.l.google.com2026-06-04 → 2026-08-17 · 3 obs

○ 2017-07-09 17:28:34
● 2026-06-04 20:44:24
● 2026-08-17 08:00:34

○MXmxs1.domainrecover.com2015-08-17 → 2016-04-04 · 6 obs

○ 2008-03-17 07:31:48
● 2015-08-17 20:51:08
○ 2015-12-06 13:07:14
● 2016-04-04 06:16:40
○ 2016-11-25 08:08:24
○ 2026-08-17 08:00:34

○MXmxs1.serverhome.com2015-12-06 → 2016-11-25 · 6 obs

○ 2015-08-17 20:51:08
● 2015-12-06 13:07:14
○ 2016-04-04 06:16:40
● 2016-11-25 08:08:24
○ 2017-07-09 17:28:34
○ 2026-08-17 08:00:34

○MXmxs2.domainrecover.com2015-08-17 → 2016-04-04 · 6 obs

○ 2008-03-17 07:31:48
● 2015-08-17 20:51:08
○ 2015-12-06 13:07:14
● 2016-04-04 06:16:40
○ 2016-11-25 08:08:24
○ 2026-08-17 08:00:34

○MXmxs2.serverhome.com2015-12-06 → 2016-11-25 · 6 obs

○ 2015-08-17 20:51:08
● 2015-12-06 13:07:14
○ 2016-04-04 06:16:40
● 2016-11-25 08:08:24
○ 2017-07-09 17:28:34
○ 2026-08-17 08:00:34

○A141.8.230.202015-08-17 → 2016-04-04 · 5 obs

○ 2008-03-17 07:31:48
● 2015-08-17 20:51:08
● 2016-04-04 06:16:40
○ 2016-11-25 08:08:24
○ 2026-08-17 08:00:34

○A216.8.177.232008-03-17 → 2008-03-17 · 3 obs

● 2008-03-17 07:31:48
○ 2015-08-17 20:51:08
○ 2026-08-17 08:00:34

●A50.16.35.2102026-06-04 → 2026-08-17 · 3 obs

○ 2017-07-09 17:28:34
● 2026-06-04 20:44:24
● 2026-08-17 08:00:34

○A66.45.246.1412016-11-25 → 2016-11-25 · 4 obs

○ 2016-04-04 06:16:40
● 2016-11-25 08:08:24
○ 2017-07-09 17:28:34
○ 2026-08-17 08:00:34

○CNAMEhdredirect-lb3-890977680.us-east-1.elb.amazonaws.com2017-07-09 → 2017-07-09 · 4 obs

○ 2016-11-25 08:08:24
● 2017-07-09 17:28:34
○ 2026-06-04 20:44:24
○ 2026-08-17 08:00:34

○CNAMEnews.serverhome.com2015-08-17 → 2016-04-04 · 5 obs

○ 2008-03-17 07:31:48
● 2015-08-17 20:51:08
● 2016-04-04 06:16:40
○ 2016-11-25 08:08:24
○ 2026-08-17 08:00:34

○CNAMEpres.serverhome.com2015-08-17 → 2016-04-04 · 5 obs

○ 2008-03-17 07:31:48
● 2015-08-17 20:51:08
● 2016-04-04 06:16:40
○ 2016-11-25 08:08:24
○ 2026-08-17 08:00:34

○CNAMEsnews.serverhome.com2016-11-25 → 2016-11-25 · 4 obs

○ 2016-04-04 06:16:40
● 2016-11-25 08:08:24
○ 2017-07-09 17:28:34
○ 2026-08-17 08:00:34

○CNAMEthie5ku9.dsgeneration.com2015-12-06 → 2016-04-04 · 5 obs

○ 2015-08-17 20:51:08
● 2015-12-06 13:07:14
● 2016-04-04 06:16:40
○ 2016-11-25 08:08:24
○ 2026-08-17 08:00:34

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
flovver.com	ns51.domaincontrol.com, ns52.domaincontrol.com	4 records

✅ Authoritative Response

Server:173.201.73.26

NS records: ns51.domaincontrol.com, ns52.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for flovver.com (unsigned zone)

⏱️ Timing

Total: 201ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`50.16.35.210`
NS	2	`ns51.domaincontrol.com, ns52.domaincontrol.com`
MX	3	`aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)...`
TXT	1	`v=spf1 include:_spf.google.com include:m`
SOA	1	`ns51.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns51.domaincontrol.com, ns51.domaincontrol.com, ns52.domaincontrol.com...)

Analysis

IP Addresses

flovver.com has exactly one IP address — 50.16.35.210.

adhesionwealth.com, brooksteinservices.com, groupedion.ca plus two other host names have IP numbers in common with flovver.com.

Name Servers

flovver.com is served by two delegated name servers, ns51.domaincontrol.com and ns52.domaincontrol.com.

The name server configuration of flovver.com is shared with other domains, for instance kraftfahrzeugversicherungen.de, frivls.com, qhamilton.com and two others.

Each of the two host names carries two IP addresses: ns51.domaincontrol.com points to 97.74.105.26 and 2603:5:2192::1a, and ns52.domaincontrol.com points to 173.201.73.26 and 2603:5:2292::1a.

Mail Servers

flovver.com uses three mail servers — aspmx.l.google.com, alt1.aspmx.l.google.com and alt2.aspmx.l.google.com.

At least some of the mail servers used by flovver.com are shared with other domains: niamavreme.bg, teamtuning.info, ns500671.ns500731.ns500671.ns500704.ns500671.ns500688.ns500671.ns500704.ns500153.tenderladiesbz.com and two others among them.

These mail servers are often deployed together with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 other mail servers.

aspmx.l.google.com resolves to 64.233.180.26 and 2607:f8b0:4004:c06::1a. alt1.aspmx.l.google.com resolves to 192.178.234.27 and 2800:3f0:4003:c14::1b. alt2.aspmx.l.google.com resolves to 172.253.116.27 and 2a00:1450:400b:c02::1a. All three hostnames point to two IP numbers each.

flovver.com - robtex.com

flovver.com

com

Same first word

Similar names

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

📌 Glue Records Collected

Analysis

IP Addresses

Name Servers

Mail Servers

`flovver.com`

`com`