Skip to content

Hostname

boc.lk

Last fetched

boc.lk resolves to 13.227.192.57, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. boc.lk 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 · boc.lkRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint8.6/10canon.whisper.security/host/boc.lk

Resolution chain

IPv6 resolution

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrant organisation
bank of ceylon

Subdomains

Subdomain
acs.boc.lk
boccustomeronboarding.boc.lk
careers.boc.lk
cbweb.boc.lk
cfb.boc.lk
chat.boc.lk
demo.boc.lk
ecash.boc.lk
email.boc.lk
expe.boc.lk
expedge.boc.lk
flexinstantloan-admin.boc.lk

Showing 12 of 34. 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

Mail and authentication

Nameservers

  • ns-107.awsdns-13.com
  • ns1.boc.lk
  • ns2.boc.lk
  • ns-809.awsdns-37.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-1199.awsdns-21.org
  • ns-1560.awsdns-03.co.uk

MX records

  • d292518a.ess.barracudanetworks.com
  • d292518b.ess.barracudanetworks.com
  • smtp.google.com

SPF policy

  • include: spf.ess.barracudanetworks.com
  • include: _spf.fortimailcloud.com
  • include: _spf.google.com
  • include: spf.messagelabs.com
  • include: ocmail.in
  • ip: 103.99.100.153
  • ip: 103.99.100.34
  • ip: 103.99.100.9
  • ip: 203.115.11.109

Threat-feed evidence

History

Related pages

Pivot from boc.lk 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: "boc.lk"})-[: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.