Skip to content

Hostname

halifax.co.uk

Last fetched

halifax.co.uk resolves to 34.149.7.15, announced in 34.150.16.0/20 by GOOGLE-CLOUD-PLATFORM - Google LLC in US. halifax.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 · halifax.co.ukRouting diversity1.5/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint8.5/10canon.whisper.security/host/halifax.co.uk

Resolution chain

IPv6 resolution

No AAAA record for halifax.co.uk is recorded in WhisperGraph.

Attribution

Google

cloud · ORIGIN_AS

WHOIS identity

Registrar
registrar:csc corporate domains, inc [tag = csc-corp-domains]
Registrant organisation
bank of scotland

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

  • ns7.lloydsbanking.com
  • ns5.lloydstsb.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
  • ns8.lloydsbanking.co.uk
  • ns2.lloydstsb.co.uk
  • nsgrid3.lloydstsb.co.uk

MX records

  • cluster5.eu.messagelabs.com
  • cluster5a.eu.messagelabs.com

SPF policy

  • ip: 5.57.231.162/32
  • include: spf.messagelabs.com
  • mx: halifax.co.uk
  • ip: 141.92.150.62
  • ip: 141.92.69.62
  • ip: 193.130.13.248
  • ip: 193.130.13.249
  • ip: 8.20.112.130
  • ip: 8.20.112.131
  • ip: 8.20.172.130
  • ip: 8.20.172.131
  • ip: 89.187.121.131
  • ip: 89.187.121.157
  • ip: 89.187.121.158
  • ip: 89.187.121.161
  • ip: 89.187.121.172

Threat-feed evidence

History

Related pages

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