Skip to content

Hostname

leaguepals.com

Last fetched

leaguepals.com resolves to 192.64.119.140, announced in 192.64.119.0/24 by NAMECHEAP-NET - Namecheap, Inc. in US. leaguepals.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 · leaguepals.comRouting diversity1.5/10Peering density4.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/leaguepals.com

Resolution chain

IPv6 resolution

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

Attribution

namecheap

ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
privacy service provided by withheld for privacy ehf
Contact emails
leaguepals@gmail.com, 0387bfcf773f4f3b96c5ec6c83d50847.protect@whoisguard.com, 0f16ceb060214ab89fa6f1e6ee82ecee.protect@withheldforprivacy.com

Subdomains

Subdomain
api-testing.leaguepals.com
api.leaguepals.com
cloud-testing.leaguepals.com
cloud.leaguepals.com
help.leaguepals.com
prod.leaguepals.com
test.leaguepals.com
www.leaguepals.com

Showing 8 of 8 subdomains (8 per page).

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
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • include: _spf.google.com
  • a: leaguepals.com
  • mx: leaguepals.com
  • include: spf.protection.outlook.com
  • include: spf.mtasv.net
  • include: zcsend.net

Threat-feed evidence

History

Related pages

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