Skip to content

Hostname

slushy.com

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
name administration inc. (bvi)
Contact emails
admin@nameadmininc.com, support@slushy.com

Subdomains

Subdomain
admin.slushy.com
affiliate.slushy.com
agent.slushy.com
analytics.slushy.com
api.slushy.com
blog.slushy.com
cdn.slushy.com
cognito.slushy.com
compliance.slushy.com
creator.slushy.com
demo.slushy.com
emaillink.slushy.com

Showing 12 of 27. 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-488.awsdns-61.com
  • ns-607.awsdns-11.net
  • ns-1354.awsdns-41.org
  • ns-1896.awsdns-45.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com
  • ba4q3db6rghmyt4ajlby5mvkedzk2lvyjeqylibfu42f5twlf3ta.mx-verification.google.com

SPF policy

  • include: amazonses.com
  • include: _spf.google.com
  • include: spf.maropost.com
  • include: sendgrid.net

Threat-feed evidence

History

Related pages

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