Skip to content

Hostname

lendable.co.uk

Last fetched

lendable.co.uk resolves to 108.132.125.183, announced in 108.128.0.0/13 by AMAZON-02 - Amazon.com, Inc. in IE. lendable.co.uk 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 · lendable.co.ukRouting diversity1.5/10Peering density9.6/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint4.6/10canon.whisper.security/host/lendable.co.uk

Resolution chain

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
registrar:namecheap, inc. [tag = namecheap-inc]
Registrant organisation
feather media

Subdomains

Subdomain
1pass-scim-gcp.lendable.co.uk
api.lendable.co.uk
asda.lendable.co.uk
assets-dev.lendable.co.uk
assets.lendable.co.uk
blog.lendable.co.uk
careers.lendable.co.uk
dev.lendable.co.uk
dmp-reporting.lendable.co.uk
em1751.lendable.co.uk
fundtracker.lendable.co.uk
help.lendable.co.uk

Showing 12 of 46. View all subdomains →

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

  • ns-382.awsdns-47.com
  • ns-723.awsdns-26.net
  • ns-1452.awsdns-53.org
  • ns-1590.awsdns-06.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com

SPF policy

  • include: amazonses.com
  • include: _spf.google.com
  • include: fdspfeuc.freshemail.io
  • include: servers.mcsv.net
  • include: sendgrid.net
  • include: em1751.lendable.co.uk
  • ip: 149.72.49.193
  • ip: 149.72.76.26
  • ip: 168.245.123.207

Threat-feed evidence

History

Related pages

Pivot from lendable.co.uk 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: "lendable.co.uk"})-[: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.