Hostname
nlb.lk
Last fetched
nlb.lk resolves to 69.16.249.143, announced in 69.16.192.0/18 by LIQUIDWEB - Liquid Web, L.L.C in US. nlb.lk is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 69.16.249.143
69.16.192.0/18 · LIQUIDWEB - Liquid Web, L.L.C · Lansing, US
IPv6 resolution
IPv6 resolution is temporarily unavailable.
The graph did not answer within the page budget. Refresh in a moment to retry — fresh data is fetched on the next visit.
Attribution is temporarily unavailable.
The graph did not answer within the page budget. Refresh in a moment to retry — fresh data is fetched on the next visit.
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for nlb.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
Subdomains is temporarily unavailable.
The graph did not answer within the page budget. Refresh in a moment to retry — fresh data is fetched on the next visit.
Mail and authentication
Nameservers
- freedns1.registrar-servers.com
- freedns2.registrar-servers.com
- freedns3.registrar-servers.com
- freedns4.registrar-servers.com
- freedns5.registrar-servers.com
- 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
- mx-01-eu-west-1.prod.hydra.sophos.com
- mx-02-eu-west-1.prod.hydra.sophos.com
- mx.zoho.com
- mx2.zoho.com
- mx3.zoho.com
SPF policy
- include: _spf_euwest1.prod.hydra.sophos.com
- include: spf.titan.email
- ip: 69.16.249.143
Threat-feed evidence
History
Related pages
Pivot from nlb.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: "nlb.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.