Skip to content

Hostname

marleyspoon.com

Last fetched

marleyspoon.com resolves to 13.225.196.35, announced in 13.225.192.0/21 by AMAZON-02 - Amazon.com, Inc. in CA. marleyspoon.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 · marleyspoon.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/marleyspoon.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:1647
Registrant organisation
fabian siegel
Contact emails
contact@marleyspoon.com

Subdomains

Subdomain
api-legacy.marleyspoon.com
api.marleyspoon.com
beef.marleyspoon.com
beta.marleyspoon.com
catflap.marleyspoon.com
data.marleyspoon.com
db03.marleyspoon.com
erp.marleyspoon.com
incidents.marleyspoon.com
ir.marleyspoon.com
logistics.marleyspoon.com
logs.marleyspoon.com

Showing 12 of 57. 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

Sample outbound links

Mail and authentication

Nameservers

  • ns-94.awsdns-11.com
  • ns-796.awsdns-35.net
  • ns-1157.awsdns-16.org
  • ns-2002.awsdns-58.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com

SPF policy

  • ip: 203.41.57.144/32
  • ip: 203.41.57.145/32
  • ip: 203.41.57.147/32
  • ip: 203.38.232.46/32
  • include: _spf.google.com
  • mx: marleyspoon.com
  • include: mail.zendesk.com
  • include: _spf.abiliware.de
  • ip: 35.160.147.225
  • ip: 35.164.81.5
  • ip: 35.166.11.1

Threat-feed evidence

History

Related pages

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