Skip to content

Hostname

grupoleoca.com

Last fetched

grupoleoca.com resolves to 104.21.37.187, announced in 104.21.32.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. grupoleoca.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 · grupoleoca.comRouting diversity2.4/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.6/10canon.whisper.security/host/grupoleoca.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · MAIL_RECEIVER, ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:1068
Registrant organisation
privacy service provided by withheld for privacy ehf
Contact emails
c0c9a513781444018dcfe5a4086d92be.protect@withheldforprivacy.com

Subdomains

Subdomain
a4fb52050a9a.grupoleoca.com
cpanel.grupoleoca.com
cpcalendars.grupoleoca.com
cpcontacts.grupoleoca.com
mail.grupoleoca.com
webdisk.grupoleoca.com
webmail.grupoleoca.com
www.grupoleoca.com

Showing 8 of 9. View all subdomains →

Mail and authentication

Nameservers

  • ns7104.banahosting.com
  • ns7105.banahosting.com
  • cruz.ns.cloudflare.com
  • howard.ns.cloudflare.com
  • khalid.ns.cloudflare.com
  • stella.ns.cloudflare.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

  • grupoleoca.com
  • _dc-mx.a4fb52050a9a.grupoleoca.com
  • mail.grupoleoca.com

SPF policy

  • a: grupoleoca.com
  • mx: grupoleoca.com
  • include: relay.mailchannels.net
  • ip: 107.6.142.170
  • ip: 204.93.189.146
  • ip: 75.102.22.130

Threat-feed evidence

History

Related pages

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