Skip to content

Hostname

leads.global

Last fetched

leads.global resolves to 15.197.225.128, announced in 15.197.224.0/20 by AMAZON-02 - Amazon.com, Inc. in CA. leads.global 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 · leads.globalRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/leads.global

Resolution chain

IPv6 resolution

No AAAA record for leads.global is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:146
Registrant organisation
domains by proxy,
Contact emails
sys@adsalsa.com

Subdomains

Subdomain
ads.leads.global
app.leads.global
br.leads.global
cl.leads.global
downloads.leads.global
es.leads.global
extranet.leads.global
it.leads.global
mail.leads.global
mx.leads.global
ne.leads.global
ns1.leads.global

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

  • ns55.domaincontrol.com
  • ns56.domaincontrol.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

SPF policy

  • ip: 217.61.72.0/21
  • ip: 185.221.16.0/23
  • ip: 109.167.13.0/24
  • ip: 94.177.152.0/24
  • ip: 130.193.108.213/32
  • mx: leads.global
  • include: pl.leads.global

Threat-feed evidence

History

Related pages

Pivot from leads.global 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: "leads.global"})-[: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.