Hostname

flowminer.com

Last fetched Sat, 26 Sep 2026 22:22:29 GMT

flowminer.com resolves to 104.21.45.229, announced in 104.21.32.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. flowminer.com is listed by 1 threat feed; reconciled level HIGH.

Threat posture

40threat score (procedure-native scale)

HIGH

Listed by 1 threat feed. At least one source recommends blocking.

Threat feeds listing this: 1
Verdict coverage: malicious-evidenced
First seen on a feed: Wed, 26 Aug 2026 14:49:47 GMT
Last seen on a feed: Fri, 25 Sep 2026 23:07:15 GMT

Nutrition Label

Resolution chain

104.21.45.229
104.21.32.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
172.233.221.214
172.233.208.0/20 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
172.234.199.15
172.234.192.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
172.237.145.27
172.237.128.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
172.67.219.176
172.67.208.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
52.20.84.62
52.20.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US

IPv6 resolution

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar: iana:1479
Registrant organisation: brian riley
Contact emails: rileybb@safe-mail.net, pw-17bb3bc3cf1e5ed02754537c26d4fbd9@privacyguardian.org, pw-977b6812dcfa20fd0be7bb120d1d6e4d@privacyguardian.org, pw-9df00b84ece38b84c7b4680793ea9a36@privacyguardian.org, pw-d2501394440d6b43db5c02531a9ec943@privacyguardian.org

Subdomains

Subdomain
server.flowminer.com

Showing 1 of 1 subdomain (1 per page).

Mail and authentication

Nameservers

ns1.atom.com
ns2.atom.com
camilo.ns.cloudflare.com
sreeni.ns.cloudflare.com
ns1.dnsowl.com
ns2.dnsowl.com
ns3.dnsowl.com
ns1.ns306.parklogic.com
ns2.ns306.parklogic.com

MX records

mx156.hostedmxserver.com
mail.wabblywabble.com
mail.wallywatts.com

SPF policy

ip: fd36:7c64:44d0::/48

Threat-feed evidence

History

Pivot from flowminer.com into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "flowminer.com"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.