Skip to content

Hostname

secureanalytic.com

Last fetched

secureanalytic.com resolves to 104.21.77.48, announced in 104.21.64.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. secureanalytic.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:51:25 GMT
Last seen on a feed
Sun, 13 Sep 2026 00:52:18 GMT

Nutrition Label

WHISPER CANON · secureanalytic.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings8.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/secureanalytic.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:468
Contact emails
ks53a774925@networksolutionsprivateregistration.com, ndansimau@hotmail.com, 38dd58ac-c5f2-4e4e-ace9-3398762c40d9@identity-protect.org, c833f5b0-f6be-463d-8921-1da887041765@identity-protect.org, f37f68b2-3338-41e4-b3b8-dda09e1b8872@identity-protect.org, owner-10592316@secureanalytic.com.whoisprivacyservice.org

Subdomains

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • coby.ns.cloudflare.com
  • erin.ns.cloudflare.com
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net

Threat-feed evidence

History

Related pages

Pivot from secureanalytic.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: "secureanalytic.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.