Skip to content

Hostname

myflowertree.com

Last fetched

myflowertree.com resolves to 13.126.229.28, announced in 13.126.0.0/15 by AMAZON-02 - Amazon.com, Inc. in IN. myflowertree.com 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 · myflowertree.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/myflowertree.com

Resolution chain

IPv6 resolution

No AAAA record for myflowertree.com is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Contact emails
myflowertree.com@protecteddomainservices.com, 0d29a160-74f7-4602-ab6c-495aab4486fc@identity-protect.org, 2b410e4f-5b66-489b-9e43-8da4bf5c6652@identity-protect.org, 42f3ccf1-92f8-41c8-9b3f-8627e3f8a948@identity-protect.org, 58599357-46d1-4b8a-b733-8dc5fd8cc3f7@identity-protect.org, a34184cc-260c-4fc4-97b2-886002329e87@identity-protect.org, b56c71ef-de2f-40e3-a1b0-1245b7a589a0@identity-protect.org, owner-10652635@myflowertree.com.whoisprivacyservice.org, owner-10881925@myflowertree.com.whoisprivacyservice.org, owner-11119966@myflowertree.com.whoisprivacyservice.org, owner-11285419@myflowertree.com.whoisprivacyservice.org, owner-11656913@myflowertree.com.whoisprivacyservice.org, owner-11854295@myflowertree.com.whoisprivacyservice.org, owner-12103925@myflowertree.com.whoisprivacyservice.org, owner-2752658@myflowertree.com.whoisprivacyservice.org, owner-2784566@myflowertree.com.whoisprivacyservice.org, owner-304757@myflowertree.com.whoisprivacyservice.org, owner-3095174@myflowertree.com.whoisprivacyservice.org, owner-3365123@myflowertree.com.whoisprivacyservice.org, owner-3466668@myflowertree.com.whoisprivacyservice.org and 19 more

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

  • ns-4.awsdns-00.com
  • ns-590.awsdns-09.net
  • 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
  • ns-1260.awsdns-29.org
  • ns-1809.awsdns-34.co.uk

MX records

  • inbound-smtp.us-east-1.amazonaws.com
  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • include: spf.mandrillapp.com
  • include: ncapp02.com
  • include: servers.mcsv.net
  • include: mailgun.org

Threat-feed evidence

History

Related pages

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