Skip to content

Hostname

lapazbcs.com

Last fetched

lapazbcs.com resolves to 65.99.252.200, announced in 65.99.192.0/18 by AS17378 - TierPoint, LLC in US. lapazbcs.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 · lapazbcs.comRouting diversity1.5/10Peering density8.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.2/10canon.whisper.security/host/lapazbcs.com

Resolution chain

IPv6 resolution

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

Attribution

tierpoint

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:1483
Registrant organisation
grupo elipse de gdl
Contact emails
alfredo.trujillo.gomez@gmail.com, sierrachesvick@hotmail.com, oscaralfaro@grupoelipse.com.mx

Subdomains

Subdomain
autodiscover.lapazbcs.com
cpanel.lapazbcs.com
cpcalendars.lapazbcs.com
cpcontacts.lapazbcs.com
mail.lapazbcs.com
webdisk.lapazbcs.com
webmail.lapazbcs.com
www.lapazbcs.com

Showing 8 of 8 subdomains (8 per page).

Mail and authentication

Nameservers

  • ns143.neubox.net
  • ns144.neubox.net
  • ns245.neubox.net
  • 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

  • lapazbcs.com

SPF policy

  • a: lapazbcs.com
  • mx: lapazbcs.com
  • include: smtp.relay.serverneubox.com.mx
  • include: relay.mailchannels.net
  • ip: 65.99.225.210
  • ip: 65.99.252.200
  • ip: 65.99.252.201
  • ip: 72.249.55.8

Threat-feed evidence

History

Related pages

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