Skip to content

Hostname

flourish.studio

Last fetched

flourish.studio resolves to 13.227.192.25, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. flourish.studio is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · flourish.studioRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/flourish.studio

Resolution chain

IPv6 resolution

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:81
Registrant organisation
canva uk operations
Contact emails
8e7ce0867e9c6d0edac25abc58269334-4775354@contact.gandi.net, bc5988700f882d9b934855812db9cae8-4775354@contact.gandi.net, bea6fea20c2b260a687d4842f09da565-56590735@contact.gandi.net

Subdomains

Subdomain
app.flourish.studio
demos.flourish.studio
dev.flourish.studio
developers.flourish.studio
help.flourish.studio
helpcenter.flourish.studio
icons.flourish.studio
public.flourish.studio
resources.flourish.studio
tempfiles201706.flourish.studio
tiles.flourish.studio
training.flourish.studio

Showing 12 of 15. View all subdomains →

Web-graph footprint

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

Sample inbound links

Mail and authentication

Nameservers

  • ns-351.awsdns-43.com
  • ns-882.awsdns-46.net
  • ns-1257.awsdns-29.org
  • ns-1905.awsdns-46.co.uk

MX records

  • mxa.mailgun.org
  • mxb.mailgun.org

SPF policy

  • include: helpscoutemail.com
  • include: mail.zendesk.com
  • include: servers.mcsv.net
  • include: mailgun.org

Threat-feed evidence

History

Related pages

Pivot from flourish.studio 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: "flourish.studio"})-[: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.