Skip to content

Hostname

slbfe.lk

Last fetched

slbfe.lk resolves to 220.247.217.187, announced in 220.247.192.0/18 by SLTINT-AS-AP - Sri Lanka Telecom Internet in LK. slbfe.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 · slbfe.lkRouting diversity1.5/10Peering density4.6/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.3/10canon.whisper.security/host/slbfe.lk

Resolution chain

IPv6 resolution

No AAAA record for slbfe.lk is recorded in WhisperGraph.

Attribution

sri lanka

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for slbfe.lk. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Subdomain
applications.slbfe.lk
finapp.slbfe.lk
mail.slbfe.lk
newapplications.slbfe.lk
services.slbfe.lk
www.slbfe.lk

Showing 6 of 6 subdomains (6 per page).

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

  • p1.ns.slt.lk
  • s1.ns.slt.lk
  • s2.ns.slt.lk
  • ns1.slt.lk
  • 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

  • slbfe.in.tmes-sg.trendmicro.com

SPF policy

  • include: _spf.prod.hydra.sophos.com
  • include: spf.tmes.trendmicro.com

Threat-feed evidence

History

Related pages

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