Skip to content

Hostname

leibsolutions.com

Last fetched

leibsolutions.com resolves to 35.192.139.89, announced in 35.192.128.0/20 by GOOGLE-CLOUD-PLATFORM - Google LLC in US. leibsolutions.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 · leibsolutions.comRouting diversity1.5/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/leibsolutions.com

Resolution chain

IPv6 resolution

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

Attribution

Google

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:895
Contact emails
4cc48fa20a28fd0a1681d479d7e5db66@domaindiscreet.com, 70d17c890a28fd0a732e4376a23f5b55@domaindiscreet.com, adf86c970a28fd0a2216764d7e5ef86d@domaindiscreet.com, b57a940a0a28fd0a663328d8f66b3c59@domaindiscreet.com, ctorban@leibsolutions.com, grjpykwvqh52@contactprivacy.email

Subdomains

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • ns-cloud-d1.googledomains.com
  • ns-cloud-d2.googledomains.com
  • ns-cloud-d3.googledomains.com
  • ns-cloud-d4.googledomains.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
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • include: _spf.google.com

Threat-feed evidence

History

Related pages

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