Skip to content

Hostname

leadsgate.com

Last fetched

leadsgate.com resolves to 34.102.166.80, announced in 34.100.0.0/14 by GOOGLE-CLOUD-PLATFORM - Google LLC in US. leadsgate.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 · leadsgate.comRouting diversity1.5/10Peering density1.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/leadsgate.com

Resolution chain

Attribution

Google

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
privacy service provided by withheld for privacy ehf
Contact emails
16828d537ca74640b66d58f131264ee6.protect@whoisguard.com, 171caeb7dd164f04acdf0b4f995aa469.protect@whoisguard.com, 1b64e6016ba34cbb8b9157ac65ec45a5.protect@whoisguard.com, a31a51e2aa094487b594ad3b10144c8c.protect@whoisguard.com, 283e98e50ae0432c81eead7230c1b997.protect@withheldforprivacy.com

Subdomains

Subdomain
canary.leadsgate.com
nas.leadsgate.com
offers.leadsgate.com
www.leadsgate.com

Showing 4 of 6. 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

  • dns1.registrar-servers.com
  • dns2.registrar-servers.com

MX records

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

SPF policy

  • include: _spf.google.com
  • include: spf.mandrillapp.com
  • include: mailgun.org
  • ip: 174.37.203.130
  • ip: 198.61.254.186

Threat-feed evidence

History

Related pages

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