Skip to content

Hostname

lendrock.com

Last fetched

lendrock.com resolves to 45.60.197.62, announced in 45.60.197.0/24 by INCAPSULA - Incapsula Inc in GB. lendrock.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 · lendrock.comRouting diversity1.5/10Peering density9.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/lendrock.com

Resolution chain

IPv6 resolution

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

Attribution

incapsula

ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of lendrock.com owner
Contact emails
lendrock.com@domainsbyproxy.com, 02e38397-59dc-4538-826f-a2d7ee2668e3@identity-protect.org, 545e1fc4-d53e-4a8e-a12f-58d97cc9218a@identity-protect.org, 78d3a9e9-738c-4593-a880-df352f8bc8c3@identity-protect.org, b35e6118-0e8a-43b5-a937-92dd5309aba1@identity-protect.org, d2ae96d5-9ca4-4e5d-b9d1-6d4b78dda2bc@identity-protect.org

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-169.awsdns-21.com
  • ns-873.awsdns-45.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
  • ns-1514.awsdns-61.org
  • ns-2003.awsdns-58.co.uk

MX records

  • lendrock-com.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com
  • include: 144692406.spf08.hubspotemail.net

Threat-feed evidence

History

Related pages

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