Skip to content

Hostname

snowleader.com

Last fetched

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

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:81
Registrant organisation
snowleader
Contact emails
thomas@snowleader.com, 12ffb52147783af17ec3faedf970c727-929066@contact.gandi.net, 1c50a6e9d987a9754a8494f0d0c12f21-929066@contact.gandi.net, caea7926c7d6dac792432525d51ad659-929066@contact.gandi.net, e5915818fcb7855c64ea96514fd7d9c7-929066@contact.gandi.net

Subdomains

Subdomain
api.snowleader.com
assets.snowleader.com
blog.snowleader.com
cdn.snowleader.com
event.snowleader.com
hvteqk.snowleader.com
images.snowleader.com
infos.snowleader.com
m.snowleader.com
mx1.snowleader.com
preprod.snowleader.com
prod-aws.snowleader.com

Showing 12 of 24. 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-125-c.gandi.net
  • ns-185-b.gandi.net
  • ns-20-a.gandi.net
  • ns1.gandi.net

MX records

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

SPF policy

  • include: _spf.google.com
  • include: _spf.salesforce.com
  • include: trustpilotservice.com

Threat-feed evidence

History

Related pages

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