Skip to content

Hostname

slicethepie.com

Last fetched

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

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of slicethepie.com owner
Contact emails
slicethepie.com@domainsbyproxy.com, domains@soundout.com, steve@slicethepie.com, 18117b45-b984-4625-9708-8ec3d75ddcf5@identity-protect.org, 54004622-80cc-4356-b395-22415b1f7b18@identity-protect.org, 5e861307-ccf4-4e90-924c-e560b9fdde31@identity-protect.org, 97ffcf64-a9a6-426e-be8b-0afe935deb4d@identity-protect.org, ac8ecf71-5e9d-4e87-8c56-372aa66e105a@identity-protect.org, da887770-e519-41b6-a0f9-adc79dffc785@identity-protect.org, ddd2b050-4961-4e36-aa94-d767eecff02f@identity-protect.org, owner-2705124@slicethepie.com.whoisprivacyservice.org, owner-7192466@slicethepie.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

  • braelyn.ns.cloudflare.com
  • frank.ns.cloudflare.com
  • harvey.ns.cloudflare.com
  • violet.ns.cloudflare.com

MX records

  • smtp.google.com
  • slicethepie-com.mail.protection.outlook.com

SPF policy

  • include: amazonses.com
  • include: _spf.google.com
  • include: spf.protection.outlook.com

Threat-feed evidence

History

Related pages

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