Skip to content

Hostname

soyummy.com

Last fetched

soyummy.com resolves to 104.18.8.52, announced in 104.18.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. soyummy.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 · soyummy.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/soyummy.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of soyummy.com owner
Contact emails
admin@promofirstmediamurah.com, dnescrow@afternic.com, info@firstmedia24.de, yuval@1st.media, 1a434956-8786-48ef-8c72-ad26462f8f37@identity-protect.org, 6811b190-ce93-43e7-918b-637b68023e4a@identity-protect.org, 694e04ef-3cc2-4b37-b537-40f1f2a98555@identity-protect.org, b60cc151-431a-464b-aeaa-939007708a1e@identity-protect.org, b7da11a3-5afa-4bc1-9ea5-55851acfb995@identity-protect.org, fe7487cb-ff2b-4460-89a0-565b8af7ff93@identity-protect.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

  • hattie.ns.cloudflare.com
  • wilson.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

MX records

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

Threat-feed evidence

History

Related pages

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